yy20111011659 / route-me

Automatically exported from code.google.com/p/route-me
0 stars 0 forks source link

libtool (libMapView.a error) on Simulator 3.1 build #114

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Embed MapView in an XCode project made with Xcode v.3.0 [Checked that 
project builds and 
runs successfully on Simulator 2.2.1 and 3.0]
3. Upgrade SDK to XCode 3.1
4. Set up code signing required by v.3.1
5. Build with Simulator 3.1

What is the expected output? What do you see instead?
The expected output was a successful build, as in previous builds. 

Error received: Libtool "/Users/iphonedevel/Desktop/SpeedcamProject 
07.08/MapView/buid/Debug-iphonesimulator/libMapView.a" normal i386 (1 error)
/Developer/Platforms/iphoneSimulator.platform/Developer/usr/bin/libtool: 
-dynamic not 
specified the following flags are invalid: -ObjC
/Developer/Platforms/iphoneSimulator.platform/Developer/usr/bin/libtool: object 
/Developer/Platforms/iphoneSimulator.platform/Developer/SDKs/iPhoneSimulator3.1.
sdk/usr/li
b/libsqlite3.dylib malformed object (unknown load command 5)

Command /Developer/Platforms/iphoneSimulator.platform/Developer/usr/bin/libtool 
failed with 
exit code 1

What subversion release are you using? Does the behavior occur on the
simulator, a real iPhone/iPod Touch, or both?
iphone SDK 3.1 beta 3. The behavior occurred on the simulator build.

If you can reproduce your bug, please provide the source code for a
reproducing case. The best place to start is with the SampleMap project.

I have reproduced the bug on the SampleMap project, but the code signing 
identity won't work
on another computer.
The only changes to the original SampleMap project were setting the code 
signing identity and 
the Info.plist bundle identifier to the info of the working certificate. The 
same error was 
encountered.

Please provide any additional information below.

This project has been tested extensively with the simulator on 2.2.1 and 3.0 
but no actual 
device. Upgrade and compatibility to the 3.1 version was requested only 
recently but during the 
course of working with the route-me MapView project no embedding problems were 
encountered.

Original issue reported on code.google.com by Morar....@gmail.com on 7 Aug 2009 at 6:50

GoogleCodeExporter commented 8 years ago
As (...further) additional information: The SampleMap application with the 
aforementioned changes applied to it 
runs on the device (Device 3.1 build) while not building on the simulator 
(Simulator 3.1 build) with the error 
mentioned in the original issue post.

Original comment by Morar....@gmail.com on 7 Aug 2009 at 7:21

GoogleCodeExporter commented 8 years ago
Appears to be a developer error in codesigning, not a route-me bug. Make sure 
all of your SDK versions match 
in all of your .xcodeproj files, Clean All, empty cache, try again.

Original comment by halmuel...@gmail.com on 7 Aug 2009 at 7:30

GoogleCodeExporter commented 8 years ago
I got the same. Recreated the project from scratch following the EmbeddingGuide 
thoroughly. The issue still 
exists. Changed the SDK version in the MapView.xcodeproj file as well but I 
idn't solved the problem.

I' will try to uninstall the whole developer tools and reinstall it again. 
Maybe the xcode update from 3.1.3 to 3.1.4 
caused the problem. I'll get back with the results.

Original comment by zgobo...@gmail.com on 12 Sep 2009 at 9:25

GoogleCodeExporter commented 8 years ago
Ok. The result is that the route-me project doesn't compile on 3.1 
out-of-the-box.

I tried the following simplest case: Fresh Xcode 3.1.4 install, latest route-me 
downloaded from the svn 
repository, MapView.xcodeproj opened and the compilation failed with the 
message mentioned in the 
description. Fortunately Xcode 3.1.4 comes with iPhone OS support from 2.0-3.1, 
so switching back to 3.0 
solves the issue, but it doesn't enough.

Original comment by zgobo...@gmail.com on 12 Sep 2009 at 1:12

GoogleCodeExporter commented 8 years ago
I have this same problem.

is there any update about this issue? is there any solution?
has this issue been resolved yet?

thanks

Original comment by sdisn...@gmail.com on 16 Sep 2009 at 5:16

GoogleCodeExporter commented 8 years ago
I too am having this same problem; and like sdisneys, wondering
if there has been any update/workaround/resolution to this?

please advise - thanks much!

Original comment by m...@winternet.com on 6 Oct 2009 at 3:24

GoogleCodeExporter commented 8 years ago
I can confirm this issue of not compiling for the "simulator" using SDK 3.1. 
Compiling for "device" on SDK 3.1 
does work however. It does not seem to be a code signing error as libMapView.a 
does not get generated.

Original comment by anthony....@gmail.com on 22 Oct 2009 at 10:02

GoogleCodeExporter commented 8 years ago
Any updates on this one? I developed an app on my laptop and got it working 
fine, running in the simulator or 
on my device. I zipped it up and sent it to a friend and it won't compile for 
him, giving the above error.

The messages showing above the error are:

"..../libtool: -dynamic not specified the following flags are invalid: -ObjC"

followed by something about libsqlite3 which I can't see properly on the 
screengrab I have :-/

Original comment by mck...@gmail.com on 20 Nov 2009 at 12:14

GoogleCodeExporter commented 8 years ago
I got rid of this error by removing libsqlite3.dylib from the MapView.xcodeproj.

Original comment by ChlorosA...@gmail.com on 15 Jan 2010 at 3:01

GoogleCodeExporter commented 8 years ago
how to avoid libtool failed toexit code 1

Original comment by mkm.srav...@gmail.com on 2 Jul 2010 at 9:28

GoogleCodeExporter commented 8 years ago
Hi guys i have some problem ! may be some one can help me! At first when i am 
trying to build mapView in the end of the process i received a message:

"No launchable executable present at path.
/Users/user/projects/route-me-truck/MapView/build/Debug-iphonesimulator/RM Unit 
Tests.app"
what i must to do? i am using xcode 3.2.3
Thank you!

Original comment by ant.o...@gmail.com on 17 Feb 2011 at 10:48

GoogleCodeExporter commented 8 years ago
I second the previous poster. The exactly the same thing happened to my app 
after I upgraded xcode. Would appreciate if someone out there knows the 
solution and let us know.

Original comment by xinema...@gmail.com on 19 Feb 2011 at 8:51