Am 24.09.2010 02:04, schrieb Danny Price:
I didn't provide a link. I said I could provide a sample project if you need it.
Your post said that the library was created as a project in a subdir therefore
it is not an 'external' library. And the path is not correct - if it was
correct you would not be having these problems.
It is a library that I create, but that is not the point. it could as
well be the a normal application.
While my library is compiled and linked the external lib is not linked
to my library.
If my App can link to my lib is something I do not see since this can
not happen
if my lib was not created. (this is what you are talking about)
The whole point is that for an external lib I do not need to provide an
build path.
What I provide (still it has nothing to do with the external lib)
in the src.pro
PROJECT_ROOT = ..
BIN_DIR = $${PROJECT_ROOT}/lib
CONFIG(debug, debug|release):DESTDIR = $${BIN_DIR}/$${COMPILER}/debug/
CONFIG(release, debug|release):DESTDIR = $${BIN_DIR}/$${COMPILER}/release/
BUILD_DIR = $${PROJECT_ROOT}/build
CONFIG(debug, debug|release):OBJECTS_DIR = $${BUILD_DIR}/debug/
CONFIG(release, debug|release):OBJECTS_DIR = $${BUILD_DIR}/release/
EXAMPLE_DIR = $${PROJECT_ROOT}/example/bin
CONFIG(debug, debug|release):DLLDESTDIR = $${EXAMPLE_DIR}/$${COMPILER}/debug/
CONFIG(release, debug|release):DLLDESTDIR =
$${EXAMPLE_DIR}/$${COMPILER}/release/
Thus my own lib is created in
/project/lib/mingw/debug/mylib.dll
the example in
/project/example/bin/mingw/debug/myapp.exe
where the dll is copied to.
In example.pro I link against this with:
CONFIG(debug, debug|release):LIBS += -L../lib/$${COMPILER}/debug/
-l$${LIBRARY_NAME}
CONFIG(release, debug|release):LIBS += -L../lib/$${COMPILER}/release/
-l$${LIBRARY_NAME}
The examplesOBJECTS_DIRis currenty not the same as the one for the lib.
Why is that necessary for shadow builds?
_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-creator
