What steps will reproduce the problem?
Rather than link to the GData framework, you can compile the GData library
sources directly into your own project. To do this, drag the GData Sources
source group from the GData Xcode project into your project's window (add by
reference, not by copying the files.)
You can delete the references to the client services (Calendar, Contacts,
Spreadsheet, and so on) that are not needed by your application, though they
will not be compiled if you set the compiler flags described below in "Removing
Unneeded Code."
If you compile the project's source files directly into your own project file,
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
What is the expected output? What do you see instead?
A successful build should be seen but instead there are a number
of errors pertaining to the GTMHTTPUploadFetcher
What version of the product are you using? On what operating system?
Gdata version 2.0 with iOS SDK XCode 4
Please provide any additional information below.
Original issue reported on code.google.com by thedi...@gmail.com on 22 Aug 2011 at 12:29
Original issue reported on code.google.com by
thedi...@gmail.com
on 22 Aug 2011 at 12:29