Hello,
I am trying to convert our current home-brew build system to use
cmake. One issue we have is that some libraries are built using
Visual C++ 7.1 and other libraries and executables are built using
VIsual C++ 6.0. I would like to somehow indicate in each subdirectory
which version of the C+
William A. Hoffman wrote:
At 05:10 PM 6/1/2006, Brandon J. Van Every wrote:
STATIC? Is that some post 2.4.2 thing? It's not in the 2.4.2 docs. What does it do?
Sorry, that is not something you can do from the set command, INTERNAL does pretty
William A. Hoffman wrote:
CMake 2.4.2-1 is now available on Cygwin mirrors.
Got it, installed it, deleted my old home-compile. Thanks! I notice
"cmake -version" says "2.4-patch 2". I guess you don't bother with the -1 ?
Cheers,
Brandon Van Every
___
CMake 2.4.2-1 is now available on Cygwin mirrors.
There has been a new release of the official cmake (2.4.2-1).
This is a major release from 2.2.3 to 2.4.2.
Changes in CMake 2.4.2
* Run symlink command from correct directory for executable versions
* Fix for universal binaries and Xcode depend
At 05:10 PM 6/1/2006, Brandon J. Van Every wrote:
>>
>
>STATIC? Is that some post 2.4.2 thing? It's not in the 2.4.2 docs. What
>does it do?
Sorry, that is not something you can do from the set command, INTERNAL does
pretty much
the same thing.
_
William A. Hoffman wrote:
At 03:55 PM 6/1/2006, Brandon J. Van Every wrote:
=
Maybe SET INTERNAL is what you are looking for.
But IIUC, INTERNAL cache state is meant only for the cache in the current directory. There is a notation in the LOAD_CACHE docum
Brandon J. Van Every wrote:
William A. Hoffman wrote:
Try this:
add a:
message(${EXTRA_LIBS})
Also, make sure you delete the CMakeCache.txt after the change.
I'll be darned, EXTRA_LIBS are dl;ws2_32
ws2_32 is from my code, but where is dl coming from?
Well crappy tun
Brandon J. Van Every wrote:
IIUC, INTERNAL cache state is meant only for the cache in the
current directory. There is a notation in the LOAD_CACHE documentation:
"INCLUDE_INTERNALS can be used to provide a list of internal entries to
be included. Normally, no internal entries are brought in. U
At 03:55 PM 6/1/2006, Brandon J. Van Every wrote:
>>=
>>
>>Maybe SET INTERNAL is what you are looking for.
>>
>>
>But IIUC, INTERNAL cache state is meant only for the cache in the current
>directory. There is a notation in the LOAD_CACHE documentation:
>"INCLUDE_INTERNALS can be used to provid
Filipe Sousa wrote:
Brandon J. Van Every wrote:
So how do you pass read-only global state to subdirectory consumers?
Cheers,
Brandon Van Every
Maybe SET INTERNAL is what you are looking for.
But IIUC, INTERNAL cache state is meant only for the cache in the
current
Brandon J. Van Every wrote:
I need some stylistic advice on handling global state. I'm starting to
break my monolithic CMakeLists.txt up into subdirectories. I'm building
the Chicken compiler and I need to do staged builds. A lot of
essentially the same operations, done on itself multiple ti
Brandon J. Van Every wrote:
> I need some stylistic advice on handling global state. I'm starting to
> break my monolithic CMakeLists.txt up into subdirectories. I'm building
> the Chicken compiler and I need to do staged builds. A lot of
> essentially the same operations, done on itself mult
William A. Hoffman wrote:
At 02:22 PM 6/1/2006, Brandon J. Van Every wrote:
When I run ccmake again, it comes back with exactly the same thing.
To be very sure of the conclusion, I comment out the entire CHECK_INCLUDE_FILE sequence.
Now there is no way for my code to be inserting
I need some stylistic advice on handling global state. I'm starting to
break my monolithic CMakeLists.txt up into subdirectories. I'm building
the Chicken compiler and I need to do staged builds. A lot of
essentially the same operations, done on itself multiple times so that
it's compiled up
At 02:22 PM 6/1/2006, Brandon J. Van Every wrote:
>When I run ccmake again, it comes back with exactly the same thing.
>
>To be very sure of the conclusion, I comment out the entire CHECK_INCLUDE_FILE
>sequence.
>Now there is no way for my code to be inserting a -ldl. It still shows up.
Try this:
Brandon J. Van Every wrote:
Brad King wrote:
Brandon J. Van Every wrote:
I have investigated, and I'm not convinced that the -ldl is coming
from my code. My code is:
CHECK_INCLUDE_FILE(dl.h HAVE_DL_H)
IF(HAVE_DL_H)
ADD_DEFINITIONS(-DHAVE_DL_H)
SET(EXTRA_LIBS ${EXTRA_LIBS} ldl)
ENDIF(HA
Brad King wrote:
Brandon J. Van Every wrote:
I have investigated, and I'm not convinced that the -ldl is coming
from my code. My code is:
CHECK_INCLUDE_FILE(dl.h HAVE_DL_H)
IF(HAVE_DL_H)
ADD_DEFINITIONS(-DHAVE_DL_H)
SET(EXTRA_LIBS ${EXTRA_LIBS} ldl)
ENDIF(HAVE_DL_H)
There is no dl.h on a
Brandon J. Van Every wrote:
I have investigated, and I'm not convinced that the -ldl is coming from
my code. My code is:
CHECK_INCLUDE_FILE(dl.h HAVE_DL_H)
IF(HAVE_DL_H)
ADD_DEFINITIONS(-DHAVE_DL_H)
SET(EXTRA_LIBS ${EXTRA_LIBS} ldl)
ENDIF(HAVE_DL_H)
There is no dl.h on any hard drive of m
William A. Hoffman wrote:
At 01:22 PM 6/1/2006, Brandon J. Van Every wrote:
Brad King wrote:
Brandon J. Van Every wrote:
I built a CMake 2.4.2 for Cygwin from sources. I used the "Unix linefeed" download, cmake-2.4.2.tar.gz. I used an earlier
At 01:22 PM 6/1/2006, Brandon J. Van Every wrote:
>Brad King wrote:
>>Brandon J. Van Every wrote:
>>>I built a CMake 2.4.2 for Cygwin from sources. I used the "Unix linefeed"
>>>download, cmake-2.4.2.tar.gz. I used an earlier Cygwin CMake package to
>>>build it. Now I am using this Cygwin CCMa
Brad King wrote:
Brandon J. Van Every wrote:
I built a CMake 2.4.2 for Cygwin from sources. I used the "Unix
linefeed" download, cmake-2.4.2.tar.gz. I used an earlier Cygwin
CMake package to build it. Now I am using this Cygwin CCMake 2.4.2
to generate my Chicken build. When it comes time
Thomas Zander wrote:
btw; does that include a /fast on install?
Good idea.
-Brad
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
On Friday 26 May 2006 17:27, Brad King wrote:
> > Doesn't seem to work here on my 2.4-p2
>
> Try it in the top level instead of the subdir. It looks like those
> shortcut targets were left out of the subdirs. We'll fix it.
Cool;
btw; does that include a /fast on install?
If I do a 'make kwordp
Filipe Sousa filipe at ipb.pt wrote :
>I've been using a configure perl script that call cmake. I have this
>script compiled to configure.exe on windows. But I always use ccmake or
>cmakesetup because there are options that are enabled depending on other
>options and that can't be done in my script
On Thursday 1 June 2006 17:33, you wrote:
> Thomas Zander zander at kde.org wrote:
> >Correct me if I misunderstood; but AFAICS the current idea was to
> > parse all config files (which in case of KOffice takes several
> > minutes with clean caches) and present the options based on that.
> >If you
On Wednesday 31 May 2006 01:44, William A. Hoffman wrote:
> Yes, that is what I am talking about. I don't think it will be hard to
> implement, and I am sure any hard coded approach will be regretted a few
> months later.
>
> Also,
>
> cmake --help (will print the help for the given project)
I
Thomas Zander zander at kde.org wrote:
>Correct me if I misunderstood; but AFAICS the current idea was to parse
>all config files (which in case of KOffice takes several minutes with
>clean caches) and present the options based on that.
>If you want to do that I suggest to not show in anyway that
> Has anyone had any luck with precompiled
headers on visual studio 2005?> > For Visual Studio 6, i added
additional parameters to each compiled > file. I then told one specific
file to build the precompiled headers. > This worked in vs6, but in 2005
the ide must have the actual projects > s
Has anyone had any luck with precompiled headers on visual studio 2005?
For Visual Studio 6, i added additional parameters to each compiled
file. I then told one specific file to build the precompiled headers.
This worked in vs6, but in 2005 the ide must have the actual projects
setup for prec
Dan White wrote:
Hi all,
Doing an OSX VTK build on intel core duo platform
OSX10.4
Cmake 2.4 patch2
VTK CVS yesterday
trying to use intel compilers for OSX intel
ccmake . configure changes intel compiler selection from icc back to
gcc! Why? Anyone know?
also it changes icpc back to g++
i
At 02:48 AM 6/1/2006, Brandon J. Van Every wrote:
>I built a CMake 2.4.2 for Cygwin from sources. I used the "Unix linefeed"
>download, cmake-2.4.2.tar.gz. I used an earlier Cygwin CMake package to build
>it. Now I am using this Cygwin CCMake 2.4.2 to generate my Chicken build.
>When it come
Brandon J. Van Every wrote:
I built a CMake 2.4.2 for Cygwin from sources. I used the "Unix
linefeed" download, cmake-2.4.2.tar.gz. I used an earlier Cygwin CMake
package to build it. Now I am using this Cygwin CCMake 2.4.2 to
generate my Chicken build. When it comes time to link a .dll, it
Hi all,
Doing an OSX VTK build on intel core duo platform
OSX10.4
Cmake 2.4 patch2
VTK CVS yesterday
trying to use intel compilers for OSX intel
ccmake . configure changes intel compiler selection from icc back to
gcc! Why? Anyone know?
also it changes icpc back to g++
icc and icpc are bo
Jan Woetzel wrote:
is there a way to compile/link only the "libs" (ADD_LIBRARY)
but skip linking the executables (ADD_EXECUTABLE)
using a global option/switch on cmake level?
I want to save compilation time when I need only the libraries for
linking my client project.
But we have about 200 exam
Brandon J. Van Every wrote:
> I would like a MESSAGE(WARNING ...) feature. This would pop up a dialog
> box in CMakeSetup, or readily appear in a display on CCMake, but it
> wouldn't skip the generation. It would get the user's attention that
> there's something not quite right about what's go
Hi,
is there a way to compile/link only the "libs" (ADD_LIBRARY)
but skip linking the executables (ADD_EXECUTABLE)
using a global option/switch on cmake level?
I want to save compilation time when I need only the libraries for linking
my client project.
But we have about 200 examples in subdire
Hi,
is there a way to compile/link only the "libs" (ADD_LIBRARY)
but skip linking the executables (ADD_EXECUTABLE)
using a global option/switch on cmake level?
I want to save compilation time when I need only the libraries for
linking my client project.
But we have about 200 examples in subdire
37 matches
Mail list logo
