I think it is fixed in the latest version of CMake in the CVS. Certainly for Visual Studio 2005 everything seems Ok in this respect.
Regards
Andrew
-- Forwarded message --From: [EMAIL PROTECTED]
To: Date: Wed, 24 May 2006 08:55:28 +0100Subject: [CMake] Bu
>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 no
James Mansion wrote:
I.e. there are modules for each library, and these modules
(should) define a standard set of variables whioch give you
the required information.
Thanks - but its not what I wanted to hear. :-(
It does load a lot of identical donkey-work onto every dependent
project. In my
>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 o
>I.e. there are modules for each library, and these modules
>(should) define a standard set of variables whioch give you
>the required information.
Thanks - but its not what I wanted to hear. :-(
It does load a lot of identical donkey-work onto every dependent
project. In my case, also, its not
-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
> f
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
indic
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 ex
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 MATCHE
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 libr
10 matches
Mail list logo