On 07/27/2011 01:03 PM, Laura Autón García wrote:
Hello glenn,
Thank you for your answer.
I misunderstood the documentation. Thank you for pointing this out!
Documentation:
...For DLL platforms the DLL part of a shared library is treated as a
runtime target and the corresponding import
Have a look at the documentation for CMAKE_RUNTIME_OUTPUT_DIRECTORY. On
Linux the .so shared library files do go in the LIBRARY_OUTPUT_DIRECTORY.
However, on Windows the DLL files are placed in the runtime directory and
only the import libraries (.LIB files) are placed in the
Have a look at the documentation for CMAKE_RUNTIME_OUTPUT_DIRECTORY. On
Linux the .so shared library files do go in the LIBRARY_OUTPUT_DIRECTORY.
However, on Windows the DLL files are placed in the runtime directory and
only the import libraries (.LIB files) are placed in the
Hello glenn,
Thank you for your answer.
I misunderstood the documentation. Thank you for pointing this out!
Documentation:
...For DLL platforms the DLL part of a shared library is treated as a
runtime target and the corresponding import library is treated as an
archive target...
It's a pity,
Hello Alan,
Thank you very much for your answer.
It woks perfectly using deprecated options, which is kind of funny,
isn't it? As Glenn pointed out in his reply afterwards, newer options
(ARCHIVE_OUTPUT_DIRECTORY, LIBRARY_OUTPUT_DIRECTORY and
RUNTIME_OUTPUT_DIRECTORY) work differently from
You could set the target property RUNTIME_OUTPUT_DIRECTORY on your library
targets. That would override the CMAKE_RUNTIME_OUTPUT_DIRECTORY variable
just for those targets.
2011/7/27 Laura Autón García laura.au...@gmail.com
Hello Alan,
Thank you very much for your answer.
It woks perfectly
Just as an alternative approach; instead of relying on having the code
in-place, generate appropriate install directives RUNTIME_, ARCHIVE_
and LIBRARY_ issues similar, needing basically a macro
my_install(target) if( WIN32) install( #what's correct for windows )
else( WIN32 ) install ( what's
Have a look at the documentation for CMAKE_RUNTIME_OUTPUT_DIRECTORY. On
Linux the .so shared library files do go in the LIBRARY_OUTPUT_DIRECTORY.
However, on Windows the DLL files are placed in the runtime directory and
only the import libraries (.LIB files) are placed in the
Hello all,
In the project I am collaborating on, CMake is used in Windows in
order to generate a Visual C++ solution to be compiled afterwards. In
this process, everything seems to work fine as the external
directories and libraries are well included and everything compiles
and so. However, we are
On 2011-07-25 12:19+0100 Laura Autón García wrote:
Hello all,
In the project I am collaborating on, CMake is used in Windows in
order to generate a Visual C++ solution to be compiled afterwards. In
this process, everything seems to work fine as the external
directories and libraries are well
On 2011-07-25 07:59-0700 Alan W. Irwin wrote:
One possibility is you are setting CMAKE_LIBRARY_OUTPUT_DIRECTORY
after your dll's are built.
That was sloppy language. What I meant was after your dll targets
are configured by CMake.
Alan
__
Alan W. Irwin
Astronomical
11 matches
Mail list logo
