static-libraries

问题 When I run make (after running qmake) I get the following error: /usr/bin/ld: cannot find -lQtGui /usr/bin/ld: cannot find -lQtCore In synaptic it shows that I have installed libqtcore4 and libqtgui4. There is no such directory as /usr/bin/ld. Basically, I've installed the QtSDK, and QtCreator seems to work fine in that it can build the hello world program. But I want to be able to work from the CLI and run make. I suspect that I may need to redirect the make program to look elsewhere for

问题 When I run make (after running qmake) I get the following error: /usr/bin/ld: cannot find -lQtGui /usr/bin/ld: cannot find -lQtCore In synaptic it shows that I have installed libqtcore4 and libqtgui4. There is no such directory as /usr/bin/ld. Basically, I've installed the QtSDK, and QtCreator seems to work fine in that it can build the hello world program. But I want to be able to work from the CLI and run make. I suspect that I may need to redirect the make program to look elsewhere for

问题 e.exe is linked against my custom static library, c.lib , which uses Win32 API defined in w.dll . w.dll is located in C:\Windows\System32 and its import library is w.lib , located in Windows SDK directory. Shell w.lib be listed as Additional Dependency in c.lib or e.exe project? ( e.exe builds successfully in both cases.) What is the best practice and why? I guess e.exe should not know about w.lib . c.lib is intended to be shared among a group of developers only (not to be shipped to

问题 Maybe I'm missing something but I'm not able to build the static libraries of opencv. Setup: Kubuntu 12.04 gcc 4.6.3 make 3.81 cmake 2.8.7 opencv 2.4.6.1 (last available on site) I do all the job manually. I tried with cmake-gui with no more success. I do what it is written. $ cmake -D CMAKE_BUILD_TYPE=RELEASE -D CMAKE_INSTALL_PREFIX=/usr/local -D BUILD_PYTHON_SUPPORT=ON -D WITH_QT=ON -D BUILD_SHARED_LIBRARIES=OFF .. (I also tried with BUILD_SHARED_LIBRARIES=NO) What I get is (for core for

问题 Trying to link against a static assimp library which I built with MinGW. Here are the errors I'm getting: H:\ovgl\ovgl...\dependencies\Assimp\lib\libassimp.a(BlenderLoader.cpp.obj):BlenderLoader.cpp:(.text+0xd91): undefined reference to inflateInit2_' H:\ovgl\ovgl\.\..\dependencies\Assimp\lib\libassimp.a(BlenderLoader.cpp.obj):BlenderLoader.cpp:(.text+0xe06): undefined reference to inflate' H:\ovgl\ovgl...\dependencies\Assimp\lib\libassimp.a(BlenderLoader.cpp.obj):BlenderLoader.cpp:(.text

问题 How can I store a version number in a static library (file.a) and later check for its version in Linux? P.S. I need possibility to check version of file any time without any special executable using only by shell utilities. 回答1: Maybe you could create a string with the version like this: char* library_version = { "Version: 1.3.6" }; and to be able to check it from the shell just use: strings library.a | grep Version | cut -d " " -f 2 回答2: In addition to providing a static string as mentioned

问题 I have used pre-build static libs of OpenSSL 1.0, but it makes my binary too big, (increase its size by about 800Kb in release mode). I do not need most of the feature of OpenSSL such as BIO, I use my own sockets, therefore in the code I am only using a couple of SSL_XXXXXXXXX calls(SSL_accept(3) or SSL_connect(3), SSL_read(3) and SSL_write(3)) My only requirement is support SSLv2/v3 with winsock on windows, and sockets on linux for both client and server side (for C++) Is there anyway to

问题 I have used pre-build static libs of OpenSSL 1.0, but it makes my binary too big, (increase its size by about 800Kb in release mode). I do not need most of the feature of OpenSSL such as BIO, I use my own sockets, therefore in the code I am only using a couple of SSL_XXXXXXXXX calls(SSL_accept(3) or SSL_connect(3), SSL_read(3) and SSL_write(3)) My only requirement is support SSLv2/v3 with winsock on windows, and sockets on linux for both client and server side (for C++) Is there anyway to

问题 What is standard or "most-popular" naming convention for MSVC library builds. For example, for following platforms library foo has these conventions: Linux/gcc: shared: libfoo.so import: --- static: libfoo.a Cygwin/gcc: shared: cygfoo.dll import: libfoo.dll.a static: libfoo.a Windows/MinGW: shared: libfoo.dll import: libfoo.dll.a static: libfoo.a What should be used for MSVC buidls? As far as I know, usually names are foo.dll and foo.lib , but how do you usually distinguish between import

问题 What is standard or "most-popular" naming convention for MSVC library builds. For example, for following platforms library foo has these conventions: Linux/gcc: shared: libfoo.so import: --- static: libfoo.a Cygwin/gcc: shared: cygfoo.dll import: libfoo.dll.a static: libfoo.a Windows/MinGW: shared: libfoo.dll import: libfoo.dll.a static: libfoo.a What should be used for MSVC buidls? As far as I know, usually names are foo.dll and foo.lib , but how do you usually distinguish between import