azubala / gdata-objectivec-client

Automatically exported from code.google.com/p/gdata-objectivec-client
Apache License 2.0
0 stars 0 forks source link

Linking to the Mac OS X Framework MISSING STEP PLEASE READ #105

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
set this build setting:

    C Language Dialect: C99 [-std=c99] 

Search the build settings for "c99" to find the setting. If it's not present as 
a build option, and if a compile error requires c99, then set the equivalent 
user-defined setting:

    GCC_C_LANGUAGE_STANDARD=c99 

For just the Debug configuration of your target, add this compiler definition 
to ensure that the library's debug-only code is included:

    Other C Flags: -DDEBUG=1 

Or, if the Other C Flags setting is not available in your target's build 
options, set the equivalent user-defined setting:

    OTHER_CFLAGS=-DDEBUG=1 

With the source files compiled directly in your project, refer directly to the 
headers by omitting the framework name, like

#import "GDataCalendar.h"

Notes for iPhone apps compiling the source files directly:

Be sure that the files GDataXMLNode.m and GDataXMLNode.h in the 
Common/Optional/XMLSupport group are included in your project. They are 
required for iPhone builds.

iPhone applications also need these build settings in the project or target:

    Header Search Paths: /usr/include/libxml2 

    Other Linker Flags: -lxml2 

Original issue reported on code.google.com by thedi...@gmail.com on 22 Aug 2011 at 12:39

GoogleCodeExporter commented 9 years ago
What is the missing step mentioned in the issue summary?

Original comment by grobb...@google.com on 23 Aug 2011 at 1:08

GoogleCodeExporter commented 9 years ago
Issue 104 has been merged into this issue.

Original comment by grobb...@google.com on 23 Aug 2011 at 1:09

GoogleCodeExporter commented 9 years ago
Issue 104 is of a different nature and should not be merged with this issue. 
Regarding comment 1:
The summary in this issue should be seen as the remaining step for the 
installation directive titled "Linking to the Mac OS X Framework". If this step 
is not taken there will be build errors related to the files in the XMLSupport 
directory. 

Original comment by thedi...@gmail.com on 23 Aug 2011 at 4:29

GoogleCodeExporter commented 9 years ago
I don't follow.

The issue summary is

"Linking to the Mac OS X Framework MISSING STEP PLEASE READ"

Mac OS X apps using the library do not use the XMLSupport files, so no linking 
step is required.

Original comment by grobb...@google.com on 23 Aug 2011 at 9:00