Am 04.04.2013 um 17:31 schrieb Brian Milco:
On Thu, Apr 4, 2013 at 6:01 AM, Daniele E. Domenichelli
daniele.domeniche...@gmail.com wrote:
One benefit is that it would allow to easily remove all cmake files when
you wrongly run cmake in the source directory instead of in the build one.
Am 22.03.2013 um 16:59 schrieb Mateusz Loskot mate...@loskot.net:
Hi,
I'm trying to build software which uses libE57 library which has
Xerces as dependency.
I build Xerces too as part of my project and I deploy it in custom locations
and Xerces library has custom name.
libE57
Am 11.03.2013 um 06:14 schrieb hce:
Hi,
I have following statement to install a file from source directory to
destination. It got a conflict error if the destination has already had the
file.
Hello Jupiter,
can you post the error message here? I wasn't aware that install(FILES ...) did
Hello Pierre,
my knowledge concerning the linking process is rather limited, but wouldn't
that mean you don't need to inter-link the libraries at all, when the symbols
are resolved at link-time with the executable?
add_executable(ex1 libB libC1 libC2) should suffice then.
Best regards,
Andreas
Hello Pierre,
self reply as a correction, sorry:
what I meant was that only linking the executables
TARGET_LINK_LIBRARIES(EX1 libB libC1)
TARGET_LINK_LIBRARIES(EX2 libB libC2)
should suffice.
Andreas
Am 25.02.2013 um 14:14 schrieb Andreas Stahl:
Hello Pierre,
my knowledge concerning
Hello Darrell,
you can also set it as a property per target
set_target_properties(MyExecutable
PROPERTIES
XCODE_ATTRIBUTE_LD_RUNPATH_SEARCH_PATHS @loader_path;@loader_path/../lib
)
This should work, but I think CMake could use some facilities to handle the
executables runpath search
messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
--
Andreas Stahl, Dipl. Medien-Inf.
Technische Universität Dresden
Fakultät Informatik
Institut für Software- und