If I set -mmacosx-version-min=10.7 or 10.8, the same error message shows up. I download Qt5.2beta, OpenCV 2.4.7, XCode 5.02, and Mac OSX 10.9 less than a week ago. I didn't finish my own test of other libraries. Thanks for the advice of checking the arch of OpenCV, which direct me to check the Makefile. I will make more check after I install all other libraries, and report the result. ( only 10.9 works, others don't work, actually, you can delete all the three flags, Qt can still build and run nicely) Here is few lines in the original = -pipe -g -gdwarf-2 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/atform/Developer/SDKs/MacOSX10.9.sdk -mmacosx-version-min=10.6 -Wall -W -fPIE = -pipe -g -gdwarf-2 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/atform/Developer/SDKs/MacOSX10.9.sdk -mmacosx-version-min=10.6 -Wall -W -fPIE = -headerpad_max_install_names -Wl,-syslibroot,/Applications/Xcode.app/Contents/Developer/Platforms/atform/Developer/SDKs/MacOSX10.9.sdk change -mmacosx-version-min=10.6 to -mmacosx-version-min=10.9īy adding this line to = after a week struggle. I opened the Makefile generated by Qt for the project I checked the arch of OpenCV lib at /usr/local/lib by the of them Mach-O 64-bit dynamically linked shared library I have a good news, I think.I have been working on this more than four days. QMAKE_LFLAGS = -std=c++11 -stdlib=libstdc++ nothing changed QMAKE_CXXFLAGS = -std=c++11 -stdlib=libstdc++ -mmacosx-version-min=10.7 Return try to add this to project += MAC_CONFIG When executing step project file += /usr/local/include Ld: symbol(s) not found for architecture x86_64Ĭlang: error: linker command failed with exit code 1 (use -v to see invocation)ġ0:31:20: The process "/usr/bin/make" exited with code 2.Įrror while building/deploying project untitled (kit: Desktop Qt 5.2.0 clang 64bit) "cv::imread(std::string const&, int)", referenced from: Undefined symbols for architecture x86_64: Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ -headerpad_max_install_names -Wl,-syslibroot,/Applications/Xcode.app/Contents/Developer/Platforms/atform/Developer/SDKs/MacOSX10.9.sdk -mmacosx-version-min=10.6 -o untitled main.o -L/usr/local/lib -lopencv_core -lopencv_highgui o main.o /Users/ObiWang/Desktop/untitled/main.cpp Applications/Xcode.app/Contents/Developer/Platforms/atform/Developer/SDKs/MacOSX10.9.sdk -mmacosx-version-min=10.6 -Wall -W -fPIE -I/Users/ObiWang/Qt5.2.0/5.2.0-beta1/clang_64/mkspecs/macx-clang -I/Users/ObiWang/Desktop/untitled -I/usr/local/include -I. Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ -c -pipe -g -gdwarf-2 -isysroot Here is the complete output in Starting: "/usr/bin/make" I solve this by = there is no error message. So it seems that Qt can't link correctly to see the function I used ?. A simple pure OpenCV or pure Boost program gives the same error. These libraries checked by file command are all 64-bit dynamically linked shared library simple program -of OpenCV- can be compiled and linked to these libraries by running commands under -L/usr/local/lib -lopencv_core -lopencv_highgui -I/usr/local/include when I try to build this program under Qt.Īn error message symbols for architecture shows up.Īs discussions with SGaist and sandy.martel below, this is caused by using libstdc++ or libc++ issue. I have -the OpenCV 2.4.7 and Boost 1.5 installed- libraries compiling from sources on my /usr/local/lib. I installed the Qt 5.2 (Qt5.1 has the same result), and a simple hello world c++ program runs nicely. The computer is a fresh (not upgraded) Mac OS X 10.9 + Xcode (5.0.2) with command line tools I think the problem is the linker, so I post here again. ![]() Symbolic links are available in NTFS starting with Windows Vista.Bq. Programming considerations for working with symbolic links.Ĭreate symbolic links that use either an absolute or relative path by using the CreateSymbolicLink function. How symbolic links affect standard file functions that use path names to specify one or more files. Symbolic Link Effects on File Systems Functions Microsoft has implemented its symbolic links to function just like UNIX links.įor more information, see the following topics. Symbolic links are designed to aid in migration and application compatibility with UNIX operating systems. Symbolic links are transparent to users the links appear as normal files or directories, and can be acted upon by the user or application in exactly the same manner. The object being pointed to is called the target. A symbolic link is a file-system object that points to another file system object.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |