Closed GoogleCodeExporter closed 9 years ago
after splitting up the platformCommon.m into 3 separate files i get the
following error:
Command /Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/gcc-4.2 failed
with exit code 1
ld: ldr 12-bit displacement out of range (4172 max +/-4096) in
_CGContextFillRect$stub in
_CGContextFillRect$stub from
/Users/evermeer/Desktop/NetSuite/build/NetSuite.build/Debug-
iphoneos/NetSuite.build/Objects-normal/armv7/NetSuite
Original comment by vermeer....@gmail.com
on 26 May 2010 at 9:26
Ouch. Can you possibly get rid of all the code you don't need?
Alternatively, try compiling your project with the new LLVM compiler.
Original comment by hasse...@gmail.com
on 26 May 2010 at 9:36
I probably only need a small part of the total generated code. It's only that I
don't want to do too much manual
editing because I would have to do that again when there is a new version of
the service. Splitting up the
platformComon into 3 files already took me half a day because xcode does not
handle big files well. If it is the
only solution, then I will try that later this week.
Original comment by vermeer....@gmail.com
on 26 May 2010 at 10:39
building using LLVM gives me the same error. It's not a build error, its a
linker error. The error occurs during
linking.
Original comment by vermeer....@gmail.com
on 26 May 2010 at 10:47
Looks like LD is puking on the sheer number of needed linkages.
Did you try compiling the non-debug version? it might play nicer with LD.
What I would do is work on the wsdl files themselves: Download them and rip out
all the services you don't
need, and if you can all the types you don't need. Then run the code generator
on those local wsdl/xsd files.
Original comment by hasse...@gmail.com
on 26 May 2010 at 1:33
A release build does work. However I would like to debug because i use some
device specific code (I use the
camera and location)
I think in most cases it would be good enough to do a debug build to the
simulator plus a release build to a
device.
I will try stripping the wsdl.
Original comment by vermeer....@gmail.com
on 1 Jun 2010 at 1:35
Ok I'll consider this closed as a "won't fix" because there's always a way to
overkill a device with massive WSDLs.
Thanks for the report.
Original comment by hasse...@gmail.com
on 1 Jun 2010 at 1:55
Let me just say that I find wsdl2objc a very cool tool :)
removing unused calls from the wsdl and the core.xsd did the job.
It was easy enough to say that this is a workaround that we can use.
I will use this in a production iPhone app (ad hoc distribution)
Thanks for your help... And many thanks for this tool.
Original comment by vermeer....@gmail.com
on 2 Jun 2010 at 8:11
Original issue reported on code.google.com by
vermeer....@gmail.com
on 26 May 2010 at 8:47