Original-Nachricht
Datum: Wed, 24 May 2006 00:09:12 +0100
Von: James Mansion [EMAIL PROTECTED]
An: cmake@cmake.org
Betreff: [CMake] Passing requirements to users
(Another stupid noob question, sorry!)
bjam has a handy feature where I can define a build
for a library
Original-Nachricht
Datum: Tue, 23 May 2006 20:00:46 +0100
Von: James Mansion [EMAIL PROTECTED]
An: cmake@cmake.org
Betreff: [CMake] Convenience Libraries and Precompiled Headers
Is it possible to convince CMake to build a set of convenience libraries
and
then a main
James Mansion wrote:
VStudio projects I add in the includes and
the documentation text and web files so I can
select them easily for editing.
You could add arbitray files to a target - as long as VS has no
automatic rule to compile them (e.g. .cc, .cpp etc)
I am adding .html files to
Jan Woetzel wrote:
ADD_EXECUTABLE(dummy dummy.cpp
${CMAKE_CURRENT_BINARY_DIR}/Doc/index.html)
Sidenote:
I think you have to take care that they are added only to VS IDE
generator builds,
in particular NOT to makefiles.
Thus we are using something like this:
IF(CMAKE_BUILD_TOOL MATCHES
I have tried to use CMake 2.4.2 and came across the bug described in
2331 which was assigned to Bill Hoffman more than a year ago:
If we have a source group X/Y and another source group Z/Y then files
which we intend to go into Z/Y will in fact go into X/Y and Z/Y is never
created even though Z
I have added progress reporting to the makefile based builds. It is checked
into CMake CVS and should work with any make and parallel builds. The
percentage done is based on source file counts without knowing if the source
files are up to date or not. Specifically the progress is not a good
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ken Martin wrote:
I have added progress reporting to the makefile based builds. It is checked
into CMake CVS and should work with any make and parallel builds. The
percentage done is based on source file counts without knowing if the source
files
Conv. libs are not (officially) supported by cmake. Just
compile all source files into the resulting library. That's
what we do for KDE.
Oh, tht's a shame. I was hoping to be able to use a single
structure which would build static or dynamic libs as either
multiple small libraries or one big
There will probably be a way to set the *interface*
include file search path separately from the
*implementation* search path. Then when a library is
linked its interface include file search path can be
included during compilation of source files using the
library.
Great - and hopefully not
