I just stumbled upon 2 warnings in my project that are really confusing..
1.
warning: ignoring debug info with an invalid version (0)
2.
WARNING: Linking two modules of different target triples: 'x86_64-apple-ios7.0.0' and 'x86_64-apple-ios6.0.0'
the first one was resolved by this answer's help. But after restarting my Xcode I got the warning again…
The second one just appeared and i can't find anything on google for this…
THanks in advance.
Items:
You should for sure clean your Xcode project (⇧⌘K). Personally, I like to clean the entire derived data directory (⌥⇧⌘K), AKA "nuke the entire site from orbit...".
I had some problems after upgrading too. FWIW, Xcode 5.1 defaults Simulator builds to "active architecture", which for most folks is x86_64 now. Previously, I think the default architecture for sim builds was i386. This might be part of your problem with #2.
Re: #2, one of those modules is compiled against the iOS6 SDK, and one is iOS7. Clean might help, or you might need to reset the Base SDK in Build Settings to Latest iOS on all your submodules.
Related
I have a slight issue when build my Xcode project, get tones of warning after update pod. It looks like this
Already search the whole site here but still no luck. it doesn't affect the project but it is quite annoying. Anyone could help?
It probably means their binary file has non-aligned pointer when they compile their code. In those cases the alignment basically defaults to 1 byte and hypothetically might impact performance.
After updating to Xcode 8.3 public release I am still seeing this error, so Google might need to compile their static library with different settings to make it go away.
Got this response from firebase support:
This is a known issue with Xcode 8.3 beta, so it might be a beta thing
and Xcode being extra verbose. It works well though with 8.2.1 so I
recommend temporarily use it to avoid the warnings or ignore the
warnings on 8.3 beta if it does not affect your app.
This has been fixed in Firebase 3.16.0 (Firebase Core 3.6 + Firebase Analytics 3.8.0)
guys, it is all fixed now. Tested it all myself on two projects. You got to go to the correct directory of your project so that your pod spec file is visible to your command line commands, run
pod update
and see it all fixed and working properly!
These problems are addressed, and likely fixed, with release 3.16.0.
I have a slight issue when build my Xcode project, get tones of warning after update pod. It looks like this
Already search the whole site here but still no luck. it doesn't affect the project but it is quite annoying. Anyone could help?
It probably means their binary file has non-aligned pointer when they compile their code. In those cases the alignment basically defaults to 1 byte and hypothetically might impact performance.
After updating to Xcode 8.3 public release I am still seeing this error, so Google might need to compile their static library with different settings to make it go away.
Got this response from firebase support:
This is a known issue with Xcode 8.3 beta, so it might be a beta thing
and Xcode being extra verbose. It works well though with 8.2.1 so I
recommend temporarily use it to avoid the warnings or ignore the
warnings on 8.3 beta if it does not affect your app.
This has been fixed in Firebase 3.16.0 (Firebase Core 3.6 + Firebase Analytics 3.8.0)
guys, it is all fixed now. Tested it all myself on two projects. You got to go to the correct directory of your project so that your pod spec file is visible to your command line commands, run
pod update
and see it all fixed and working properly!
These problems are addressed, and likely fixed, with release 3.16.0.
I have a slight issue when build my Xcode project, get tones of warning after update pod. It looks like this
Already search the whole site here but still no luck. it doesn't affect the project but it is quite annoying. Anyone could help?
It probably means their binary file has non-aligned pointer when they compile their code. In those cases the alignment basically defaults to 1 byte and hypothetically might impact performance.
After updating to Xcode 8.3 public release I am still seeing this error, so Google might need to compile their static library with different settings to make it go away.
Got this response from firebase support:
This is a known issue with Xcode 8.3 beta, so it might be a beta thing
and Xcode being extra verbose. It works well though with 8.2.1 so I
recommend temporarily use it to avoid the warnings or ignore the
warnings on 8.3 beta if it does not affect your app.
This has been fixed in Firebase 3.16.0 (Firebase Core 3.6 + Firebase Analytics 3.8.0)
guys, it is all fixed now. Tested it all myself on two projects. You got to go to the correct directory of your project so that your pod spec file is visible to your command line commands, run
pod update
and see it all fixed and working properly!
These problems are addressed, and likely fixed, with release 3.16.0.
I have recently updated version to xCode6.2 and previous one I was using xCode6.2 beta.
It works fine with all previous versions and xCode6.2 beta as well.
When I am update it's version, I have removed xCode beta completely and install new one. But it is getting this issue, and I have added UIKit, Foundation to libraries. No luck yet.
The thing what I have tried and suspicious additionally;
Check framework search path at build settings(nothing mentioning that)
Other LD Flags in build settings.
This is suspicious, because it's have keys -frameworks Foundation, -frameworks UIKit
Have not enough understandings about other LD flags this values, so tried to remove them, but nothing new.
When I open other project with new version of xCode, they are all working fine but just that project.
Can anybody help this?
It's probably better to simply uninstall xcode completely with appCleaner or such. And reinstall it.
I suspect it will work and you will save time otherwise spent searching for a solution.
After struggling a few hrs, I found the solution.
The error was because of the some path specified in OTHER_LD_FLAGS and OTHER_C_FLAGS have not changed.
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS8.1.sdk
It was like this but it should be iPhoneOS8.2.sdk according to the changes of xCode version
I am new to IOS and am writing an ios 7.0 app that uses coreplot (latest version 1.3). I had the "Build active architecture" set to YES - so during the development, I did not run into any linking problem (I used static linking method as described at https://code.google.com/p/core-plot/wiki/UsingCorePlotInApplications
Then I built and deployed on my device (iphone 4, ios 7). It worked fine - I dont remember if it asked to change build settings or not. Today morning, when I tried to run the same code on simulator it started giving me linker error. After doing some research, I realized I need to set the build for active architecture to No and rebuild the core plot using "dependent project install" strategy.
I am stuck at the point where I need to set the header files search path. The compilation fails to detect the header file. The coreplot is in a directory CorePlot_1.3.
The main linking error reads as
"ignoring file /Users/rmenon/Documents/Developer/MoneyTrail/MoneyTrail/libCorePlot-CocoaTouch.a, missing required architecture x86_64 in file /Users/rmenon/Documents/Developer/MoneyTrail/MoneyTrail/libCorePlot-CocoaTouch.a (3 slices)"
As part of my attempt to solve this, I tried to load the coreplot project separately, change the architecure to Stndard (armv7 nd armv7s) and tried to build it. I get two deprecation errors below. Any help in getting me compile this library for ios 7 so I can use the same setting in debug and device would be really appreciated! Thank you!
You'll need to update to a newer version of Core Plot. It has been updated to work with Xcode 5 and iOS 7, but we haven't done a release with those changes yet. You can pull the latest code with Mercurial or wait for the next release, which should be soon (within the next week or so).