Linking with OpenCV in XCode

Debug and Release build settings are independent. For example in Debug, projects usually want to link with libraries that include symbols; otherwise not. So it's common for Debug to use a set of lib paths that are different from Release. Adding a framework to a project may add several paths for xCode to choose from based on config., SDK version, and target platform.

I'm not clear on exactly where or how you added your libs to the project (there are other ways besides dragging, btw), but since you knew how to do that for the Debug config., just do it again for Release. Xcode won't care that the paths are the same, they just need to be set separately.

If you'd rather use gcc from the Terminal command line, that will work just fine too. I do lots of my work that way. In fact you can still use the Xcode editor by typing "open file_name.C" at the command line.

Hey

I too am facing same issues with linking opencv. My debug config seems to be workign just fine but Release has linking errors. I have added Lib search paths, Header search path and all the libs in -l<style> in other library flags.

I am currently suing Eclipse which is able to link fairly well. I am new to Mac and would like to experience Xcode, in case someone figure out solution please let me know.

mine's not resolved. Xcode 3.2, using the OpenCV framework 1.2. compiles fine. Won't link against framework. Standard cant find referenced symbol messages from the linker. Build config, file locations, etc all seem to be identical to demo app (FaceTracker). Build config doesn't matter. I do NOT have 10.4 SDK installed ...

Any help?

I tried to build this library myself, but it fails because I don't have QT. I even tried turning off QT support without success.

As I have definitively problem this package isn't put together very well, there are no guarantees.

Are you able to get FaceTracker to build correctly in both debug and release? If so, you may want to compare settings from the target panes. That might be where the difference is. You can also check the raw output from FaceTracker.

FaceTracker builds (and works) fine - both debug and release versions, using the prebuilt 1.2 framework, with no problems of any kind. I gave up (for now) trying to build the 2.0 framework myself as there were just too many issues, so am using the framework.

I have spent hours comparing build settings on my project(s) and have had no love. Here is the history, after making FaceTracker work.

I built a project to put this into a Quartz plug-in. First problem was getting it to simply compile - with the same includes, paths, etc as FaceTracker there were many unfound includes. Resolved the framework stuff eventually by NOT using System/Library/Private Frameworks/ - just put it in user space at /Library/Frameworks/. Never resolved finding <cassert> and <stdio> - but not actually needed, so punted on those.

Got it to compile with minimal warnings, but BAM, won't link! Cannot find any of the functions in OpenCV. Spent more hours looking at framework paths, compiler settings, link setting, build configs ... nothing changed for the better.

Finally built a little project to simply evaluate the include and link stuff. Got it to compile, and slowly added more references found only in the OpenCV headers, at multiple layers in the header structure. All good. Added one function call, that compiles and links in FaceTracker, and same result - cannot find the link symbol for "_cvLoad", a helper function contained in the framework.

I am sure this is a build problem - the wrong symbol stripping or a funny sequence of linkage paths and flags. I am just hoping someone out there has had to deal with this with open source ports, or this library ...

I am new to XCode, and have not worked the Unix/linux world in a looong time. BTW, using 10.6 sdk - the framework uses 10.4. I haven't installed 10.4 yet, and that is my next approach.

Any ideas?

Fixed, at least for this little project. Apparently, the 1.2 framework is valid only for i386. I am sure if I look, it will tell me that in the documentation.