ADD_CUSTOM_COMMAND(
OUTPUT {library}.def
COMMAND using ${library}-static
COMMAND ${CMAKE_COMMAND} -E touch ${library}.cpp
DEPENDS ${library}-static
)
This would invalidate ${library}.cpp each time ${library}.def is
regenerated, so the dummy is recompiled and ${library}
AFAICS there are three different issues here:
- Having a .def file as a source in a ADD_LIBRARY() it does the correct thing,
which is using it to build the library, but it does not create a dependency to
it. I would call this a bug.
- The way to generate the .def file that I have figured
On 12/22/2010 07:49 PM, Pere Mato Vila wrote:
AFAICS there are three different issues here:
- Having a .def file as a source in a ADD_LIBRARY() it does the correct
thing, which is using it to build the library, but it does not create a
dependency to it. I would call this a bug.
For the
Dear all,
I am trying to build shared libraries on Windows exporting all symbols. This
is as an alternative of instrumenting the code with dllimport/dllexport
declarations. For this I do build first a static library from which I get all
the defined symbols to write a .DEF file which is then
You will want to read this article:
http://www.cmake.org/Wiki/BuildingWinDLL
___
Mike Jackson www.bluequartz.net
Principal Software Engineer mike.jack...@bluequartz.net
BlueQuartz Software Dayton,
Hi,
I did read the article. The point is that I am trying to port a number of
very large projects to CMake that have been always build without code
instrumentation, which I am convinced is the best and optimal way of doing it.
But in this case the code instrumentation is not practical for a
On 12/21/2010 04:13 PM, Pere Mato Vila wrote:
Dear all,
I am trying to build shared libraries on Windows exporting all symbols.
This is as an alternative of instrumenting the code with dllimport/dllexport
declarations. For this I do build first a static library from which I get all
the
On 12/21/2010 2:17 PM, Michael Hertling wrote:
AFAIK, this is because CMake does not know how to handle a .def file
for incorporation in the target, i.e. ${library}.def has no LANGUAGE
Actually, it should...
Something like this should work:
(assumes you have a perl script to create a .def
On 12/21/2010 08:45 PM, Bill Hoffman wrote:
On 12/21/2010 2:17 PM, Michael Hertling wrote:
AFAIK, this is because CMake does not know how to handle a .def file
for incorporation in the target, i.e. ${library}.def has no LANGUAGE
Actually, it should...
Something like this should work:
