ViewController.o File Errors

[jwrichiv]

Forgive me if this has already been addressed, but...

I am developing my first, to-release, app and the final step is a mapping step that will find the users location and map out a route to a predetermined address. All worked fine until I started adding in the Core Location code. After compiling, i get the errors below. Where are the ".o" files? How do I correct their deficiencies?

Undefined symbols:
"_kCLDistanceFilterNone", referenced from:
_kCLDistanceFilterNone$non_lazy_ptr in ContactViewController.o
(maybe you meant: _kCLDistanceFilterNone$non_lazy_ptr)
"_OBJC_CLASS_$_CLLocationManager", referenced from:
objc-class-ref-to-CLLocationManager in ContactViewController.o
"_kCLLocationAccuracyBest", referenced from:
_kCLLocationAccuracyBest$non_lazy_ptr in ContactViewController.o
(maybe you meant: _kCLLocationAccuracyBest$non_lazy_ptr)
ld: symbol(s) not found
collect2: ld returned 1 exit status

Any help, even a gentle nudge in the right direction will be greatly appreciated. Thanks.

[kapps11]

dude i never understand those errors either, cuz it just happens theres nothing really to cause it. i just kinda equate it with xcode just crapped its pants. try clean all targets, and then if that doesnt work, what ive had to resort to in the pst is creating a new project and manually adding all of the old files to that new project. really stupid lol... maybe somebody else out here has a real solution???

[Kalimba]

I suppose "xcode just crapped its pants" could be the reason... but errors like that usually indicate that a framework is missing from your project.

When you say "I started adding in the Core Location code", I'm assuming you're talking about source code. But have you added the framework(s) that this new code links against?

Also, the ".o" files are the intermediate files that the compiler produces as output from compiling a ".m" (or ".c", or ".cpp" I believe) source file. Once all of the source files have been compiled into .o files, the linker is then put in charge to make all of the appropriate connections. If a framework (aka "library") hasn't been added to the project, the linker can't make the connections and spits out error messages -- just like the ones you've posted.

[jwrichiv]

kapps - ive had to resort to in the pst is creating a new project and manually adding all of the old files to that new project

I've done this before as well, but I have gotten tired of that and this has turned into a huge project. Super time consuming, but it is looking like that is where I am heading.

Kalimba - When you say "I started adding in the Core Location code", I'm assuming you're talking about source code. But have you added the framework(s) that this new code links against?

I have added the "#import <CoreLocation/CoreLocation.h>" to my .h file, is there more to the code linking than that?

[kapps11]

yes there is, you need to actually go and add it the framework to your project. its something like Project -> add to project -> add framework to project. or something like that i dont remember. And that probably is the reason im just not smart enough to figure that out lol. but ill remember that in the future!