http://www.cmake.org/Wiki/CMake_Useful_Variables has variables for
putting executable and library files in a common directory, but I don't
see anything for object files. Do you actually need object files in a
common directory? Why?
Cheers,
Brandon Van Every
d.1234567890 wrote:
In our
Trevor Kellaway wrote:
Hi,
I'm try to get my link to depend on a pre-existing file that contains
linker segment information link.prm.
I thought that by just adding this to the executable dependency list
this should work:
ADD_EXECUTABLE (${THIS_APP} ${THIS_SRC}
[EMAIL PROTECTED] wrote:
On Thursday 12 April 2007 19:33, Brandon J. Van Every wrote:
Trevor Kellaway wrote:
Hi,
I'm try to get my link to depend on a pre-existing file that contains
linker segment information link.prm.
I thought that by just adding this to the executable dependency
Bill Hoffman wrote:
Actually from the wiki:
http://www.cmake.org/Wiki/CMake_FAQ
Your custom commands should look like this:
ADD_CUSTOM_COMMAND(
OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/foo0.qaz
COMMAND ${DOIT_EXE} ${CMAKE_CURRENT_SOURCE_DIR}/someinput0.txt
${CMAKE_CURRENT_BINARY_DIR}/foo0.qaz
CMake (unfortuantely) distinguishes between target level dependencies
and file level dependencies. An ADD_CUSTOM_COMMAND only creates file
level dependencies, and these fail in various circumstances. To create
target level dependencies, you create an ADD_CUSTOM_TARGET that depends
on the
Alan W. Irwin wrote:
t f
library = target = command
\
\ t
=== executable
This new arrangement bypasses the whole issue of having a custom command
file depend on an executable
Are you using
Alan W. Irwin wrote:
What do you think of the possibility of using the above forked
arrangement
of dependencies instead? I will go to that (and not worry about
GET_TARGET_PROPERTY),
You must use GET_TARGET_PROPERTY to support MSVC. YMMV with other
generators.
if anybody can assure me
Manfred Rebentisch wrote:
Hello,
I am new to this list, so I beg your pardon, if the question is a recurrence.
I use cmake version 2.4-patch 3 on Suse 10.1 .
I want to generate a library with the name libstd3000c.so. So I define:
CMakeLists.txt BEGIN
project(Std3000C)
set(USEAPR 1)
Jong-young Park wrote:
How can I know what compiler is (in project using CMake)?
http://www.cmake.org/Wiki/CMake_Useful_Variables
Cheers,
Brandon Van Every
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Salvatore Iovene wrote:
Am I doing something obviously wrong?
Using an older version of CMake when making a bug report? :-)
My cmake version is 2.4-patch 5.
See if it's a problem with 2.4.6.
Cheers,
Brandon Van Every
___
CMake mailing
Pascal Fleury wrote:
So it will in effect automatically add the current source dir and current
binary dir to the include directories in every directory as the doc says.
However, the *current* directory has a different value when cmake is
processing project/src/CMakeLists.txt than when
Kishore, Jonnalagadda (IE10) wrote:
I just checked again and confirm that the information was already there under the section
Various Options
http://www.cmake.org/Wiki/CMake_Useful_Variables#Various_Options
Now it is also added under Environment Variables
Kishore, Jonnalagadda (IE10) wrote:
-Original Message-
CMAKE_INCLUDE_CURRENT_DIR is the same as
INCLUDE_DIRECTORIES(${CMAKE_CURRENT_BINARY_DIR}
${CMAKE_CURRENT_SOURCE_DIR}) for all targets.
If you have a project that constantly needs to add the current source
directory and the
kitts wrote:
But then, despite setting the value I had to put in
INCLUDE_DIRECTORIES(.)
And I was brief because I don't know if there any caveats on how it can
be used. Maybe you found a bug. Maybe the behavior isn't consistent
across generators. Maybe the value isn't propagated
Could you please put this in the bug tracker so it doesn't get lost?
http://www.cmake.org/Bug That's the best way to report a fairly
cut-and-dried problem / wart / better feature or behavior you'd like to
have. Generally I post on the mailing list if I don't know whether or
not something is
James Bigler wrote:
Is is possible to add include directories for a particular source file?
Right now I do:
INCLUDE_DIRECTORIES(${Extra_Include_Dir})
But this puts the extra includes on all the files for the libraries in
the CMakeLists.txt file.
Where is the harm in doing so? Are you
Filipe Sousa wrote:
CMAKE_INCLUDE_CURRENT_DIR is the same as
INCLUDE_DIRECTORIES(${CMAKE_CURRENT_BINARY_DIR}
${CMAKE_CURRENT_SOURCE_DIR}) for all targets.
When explaining a variable, it's good to put it on the wiki. I did it
this time.
stuff before I bother looking at things deeply.
On Thu, 15 Mar 2007 00:00:50 -0700
Brandon J. Van Every [EMAIL PROTECTED] wrote:
Asmodehn Shade wrote:
Using CMake 2.4.2 on NetBSD 4.0, my command line looks like :
Why don't you try updating to CMake 2.4.6?
Cheers,
Brandon
Cristian Adam wrote:
I hope you will include it in the next build, so that others will benefit
from it. And, maybe scintilla and SciTE will be build using CMake ;-)
Thanks for that. I have been using SciTE lately. My experience has
been that I don't need pretty printing and so forth to
Bill Hoffman wrote:
Orion Poplawski wrote:
What are the issues that arise? In general with RPM packaging you
are starting with a clean freshly unpacked source tree.
It really depends on the project. There are no cmake imposed
limitations on this.
What happens in practice, is if
Asmodehn Shade wrote:
Using CMake 2.4.2 on NetBSD 4.0, my command line looks like :
Why don't you try updating to CMake 2.4.6?
Cheers,
Brandon Van Every
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Asmodehn Shade wrote:
Hi everyone,
I am currently in the process of starting to profile my software.
It builds with cmake on unix, linux, and windows, more or less nicely ;)
Assuming that I only want to use g++ with gprof right now, I wonder if there
was a way to do that smartly in CMake,
Jong-young Park wrote:
...
LINK_DIRECTORIES(../lib)
LINK_LIBRARIES(crypt pthread my)
These are old commands. Install CMake 2.4.6, read the cmake.html docs
again, and don't use them. Look at TARGET_LINK_LIBRARIES.
Cheers,
Brandon Van Every
___
Alexander Neundorf wrote:
Von: Brandon J. Van Every [EMAIL PROTECTED]
Jong-young Park wrote:
I need both lib.a lib.so as project result.
But ADD_LIBRARY command may support Only 1 type, I think.
Not any other method?
Thanks for reading.
]
You will have to do ADD_LIBRARY
I am questioning the relevance or clarity of this FAQ entry:
http://www.cmake.org/Wiki/CMake_FAQ#How_do_I_rename_a_library_that_has_already_been_built.3F
This looks like some kind of historical hack-around. I don't think we
want to be telling people to rename libraries. Rather, we should be
When rewriting a FAQ entry I came upon a conundrum.
http://www.cmake.org/Wiki/CMake_FAQ#How_do_I_rename_a_library_after_it_has_already_been_built.3F
On Windows you may also want to copy the .dll import lib, using the
same approach as above, but with IMPORT_PREFIX and IMPORT_SUFFIX.
Problem:
Alan W. Irwin wrote:
I think that documentation needs to be expanded by roughly a factor of
three
to make it consistent with the size of the documentation of the second
form
of try_compile which is well documented from my perspective. I certainly
did not get the above terse documentation
How do I ensure that INSTALL has already occurred, so that I can proceed
with post-installation testing? When I last tried my hand at this, I
found that install is not a first class dependency target. In fact,
trying to make a dependency on install crashed CMake, but the crash
got fixed at
Thomas Christian Chust wrote:
I consider this seriously buggy behaviour. First of all I don't like it
that the build system magically wipes out one of the library targets I
ordered it to create.
See SET_TARGET_PROPERTIES in the docs.
When a library is built CMake by default generates code to
klaas.holwerda wrote:
Hi,
Cmake 2.4 patch 5
I am getting different behaviour on Linux compared to windows. From
the docs i understand that the next should end up with the message
fine.
Is that true? I get the else answer??
SET( myvar 0 )
IF( myvar EQUAL 0 )
MESSAGE( fine )
ELSE( myvar
Bill Hoffman wrote:
CMake does not directly support [static libraries as part of a static
library].
However, you can put a full path to a .o file as a source for a
library and cmake will do the right thing for with it. The catch is I
have never done this, and it will be difficult to figure
Pavel Volkovitskiy wrote:
Brandon J. Van Every wrote:
There's nothing stopping anyone from writing code like
IF(KDE)
FIND_LIBRARY(ASPELL_PATH ...)
blah
ELSE(KDE)
blah
ENDIF(KDE)
but nobody's going to do that without a motive. It sounds like the
real problem here is that conary
In my toplevel CMakeLists.txt I have:
ADD_SUBDIRECTORY(pcre)
ADD_SUBDIRECTORY(boot)
in pcre/CMakeLists.txt I build
SET_TARGET_PROPERTIES(libpcre-for-shared PROPERTIES
COMPILE_FLAGS ${SHARED_FLAGS} -fPIC
OUTPUT_NAME pcre-for-shared)
in boot/CMakeLists.txt I link:
Radu Serban wrote:
Brandon J. Van Every wrote:
In my toplevel CMakeLists.txt I have:
ADD_SUBDIRECTORY(pcre)
ADD_SUBDIRECTORY(boot)
in pcre/CMakeLists.txt I build
SET_TARGET_PROPERTIES(libpcre-for-shared PROPERTIES
COMPILE_FLAGS ${SHARED_FLAGS} -fPIC
OUTPUT_NAME pcre-for-shared
Wojciech Jarosz wrote:
I've been looking through other projects that use CMake in order to
learn more. I've seen that some (Chicken, Scribus, for example) seem
to have configure.in files in addition to CMakeList.txt files. I was
wondering why one would use both autoconf and CMake in the same
Wojciech Jarosz wrote:
Right. But other than the transitioning reason, is there any benefit
to using autoconf in conjunction with CMake, as opposed to using CMake
alone?
None. Autoconf is a complete royal PITA. Avoid it like the plague. I
didn't want to become an Autoconf expert... it was
Bill Hoffman wrote:
Brandon J. Van Every wrote:
So I am not seeing how Debug is a default value for CMAKE_BUILD_TYPE.
OK, it seems that it is the default for nmake with cl,
That's consistent with Windows build culture, in that a MSVC .sln file
does have Debug as the default. I don't
Bill Hoffman wrote:
Brandon J. Van Every wrote:
Bill Hoffman wrote:
You can not use FIND_* stuff because the files will not be there.
There is a risk that cmake could change where the .o files are put.
To mitigate that risk, I would recommend setting up everything with
variables. You
Eric Noulard wrote:
Is there a way to build both shared AND static
in a single build
Yes. However, you'll probably need to compile them in separate
directories to prevent collisions between object files. The Chicken
CMake build http://www.call-with-current-continuation.org/index.html has
Eric Noulard wrote:
2007/1/25, Andreas Schneider [EMAIL PROTECTED]:
Eric Noulard wrote:
Is there a way to build both shared AND static
Hi Eric,
yes there is. From the cmake documentation:
SET_TARGET_PROPERTIES
When a library is built CMake by default generates code to
remove any
I added the following notation to the Useful Variables page of the wiki:
http://www.cmake.org/Wiki/CMake_Useful_Variables#Compilers_and_Tools
Note that CMAKE_BUILD_TYPE is not initialized with a readable value at
configuration time. This is because the user is free to select a build
type at
David Cole wrote:
Put the -D args *before* the -P -- it'll work like you expect then...
I've added content bug #4372 on this issue. The order dependency should
be documented.
Cheers,
Brandon Van Every
___
CMake mailing list
CMake@cmake.org
Sam Miller wrote:
I am trying to convert an hand-rolled Makefile build system into CMake.
The project itself is a subset of a larger project, which uses a
Make.rules file for various cross compilation rules and install
directories. Is there any way to include this Make.rules file into the
Bill Hoffman wrote:
Basically, there are two types of generators, single build type per
build tree, and multi- build type per tree. The variables that are
useful for that are here:
CMAKE_BUILD_TYPE is used by makefile generators or any future
generator that supports one build type per
Bill Hoffman wrote:
Brandon J. Van Every wrote:
For clarity, let's say I make 2 static libraries:
- pcre_static_pic, for use with our shared libchicken et al
- pcre_static_nopic, for use with our libchicken-static et al
The latter case runs into the static library as part of a static
library
Bill Hoffman wrote:
Brandon J. Van Every wrote:
Bill Hoffman wrote:
Brandon J. Van Every wrote:
We need to compile the same underlying code 7 times for 7 different
libraries. 3 of the resulting libs are dynamic and 4 are static.
I am not following the example here. If PCRE where
We need to compile the same underlying code 7 times for 7 different
libraries. 3 of the resulting libs are dynamic and 4 are static. We
would use convenience libraries to do this, if it were portable and
available in CMake. We understand that ar in particular can't include
static libraries
Bill Hoffman wrote:
Brandon J. Van Every wrote:
We need to compile the same underlying code 7 times for 7 different
libraries. 3 of the resulting libs are dynamic and 4 are static.
I am not following the example here. If PCRE where a convenience
library you would want it
to be used
Ilya Shvetsov wrote:
Hi, cmake team!
I have tried new build (CMake 2.4.6) and found that MSYS generator not
works.
System:
WinXP SP2
Msys with MinGW 3.4.5.
Version 2.4.3 works fine. At the moment I can't send error log.
But I do this later if you need.
You'll need to send more
[EMAIL PROTECTED] wrote:
Hello Chandra,
chandrashekhar jadhav wrote:
-- Build started: Project: ZERO_CHECK, Configuration: Debug Win32
--
Checking Build System
-- Check for working C compiler: c:/Program Files/Microsoft Visual
Studio 8/VC/bin/cl.exe
-- Check for working C
I'm getting into IBM Cell development, the CPU that's in the Sony
Playstation 3. I'm thinking of porting Chicken Scheme to it. I don't
currently have the dough for a PS3. Anyone have a PS3 with Linux set up
on it, or is willing / planning to set it up? I'd like to try some
CMake
Mehdi Rabah wrote:
All I have to say is that you all rocks :-)
Brandon Van Every, excuse my ignorance but what documentation are you
refering to ?
The cmake book ?
No, C:\Program Files\cmake-2.4\cmake.html , or the equivalent on your
OS. This is evidence that there aren't enough
Someone showed up on the Chicken mailing list and wants to do Debian
packaging for Chicken. I'm looking at what I need to do to support
packaging systems in general. I've noticed several problems already:
- packages tend to duplicate the project's manifest. Often these
duplications are
Anders Sundman wrote:
Hi!
Can you configure cmake to perform an install automatically?
Today, when we generate a VC-project we get an INSTALL target which
installs the program when explicitly built. But when we execute a
build solution, the install target is not run. The following message
James Bigler wrote:
If you look at the original code. The PARSER_EXECUTABLE variable
isn't defined until inside the first ELSE branch.
# You need at least version 2.4 for this to work.
IF(${CMAKE_MAJOR_VERSION}.${CMAKE_MINOR_VERSION} LESS 2.6)
MESSAGE(You need at least version 2.4 for
James Bigler wrote:
I want the variable to disappear from the list when running ccmake.
This didn't seem to do anything.
How about SET(myvar CACHE INTERNAL Don't show this)
See the docs for SET.
Cheers,
Brandon Van Every
___
CMake mailing list
James Bigler wrote:
Message: 8
Date: Tue, 05 Dec 2006 00:48:31 -0800
From: Brandon J. Van Every [EMAIL PROTECTED]
Subject: Re: [CMake] Deleting a variable
To: cmake cmake@cmake.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
James Bigler
James Bigler wrote:
FIND_PROGRAM(PARSER_EXECUTABLE
NAMES my_parser
PATHS ${PARSER_DIR} )
IF(EXISTS ${PARSER_EXECUTABLE})
SET(PARSERS_FOUND 1)
ELSE(EXISTS ${PARSER_EXECUTABLE})
SET(PARSERS_FOUND 0)
ENDIF(EXISTS ${PARSER_EXECUTABLE})
CMake Error: Error in cmake code at
Alan W. Irwin wrote:
On 2006-12-05 14:44-0700 James Bigler wrote:
CMake barfs on the first IF(EXISTS ${PARSER_EXECUTABLE}), probably
because it is trying to evaluate if this expression is part of the
ENDIF or something. It does this with 2.2.3, 2.4.3, 2.4.5 on Linux.
Try IF(EXISTS
wedekind wrote:
Hello Brandon,
thanks for your input.
So you are the only person who ever builds your software? If other people
have to build your stuff, you're making it a PITA for them, having to
remember precisely what Qt directory to use. All this knowledge is locked
up in
Tanguy Krotoff wrote:
Brandon J. Van Every wrote:
Sure. But OpenWengo isn't a patch. I'm sure everyone will be very
happy if you submit *small* patches, bug reports, and feature
requests in the bug tracker for *CMake*. Nobody wants the entireity
of CMake to be rewritten in a higher level
Summary: emitting a CMakeLists.txt is never parallel with standard
coding practices in the toplevel CMakeLists.txt. At a minimum, this
causes programmers to do everything 2 different ways. In the likely
case, the emission fails because it is fragile as quotes are consumed.
These kinds of
Martin Lütken wrote:
Thanks a lot!
But the name CONFIGURE_FILE suggest it happens before the build.
Is that so? I need to copy lib files after build!
I didn't really understand the rest of the post; perhaps some context
got snipped. Going by the subject line, I think what you want is an
Eric Noulard wrote:
May be you could use TRY_RUN to detect endianity
with something like:
TRY_RUN(
ENDIANESS_RESULT
ENDIANESS_COMPILE
/tmp/
${CMAKE_CURRENT_SOURCE_DIR}/make/endianess.c
OUTPUT_VARIABLE ENDIANESS_OUT
)
MESSAGE(STATUS ENDIANITY is :${ENDIANESS_OUT})
endianess.c is
)
ECHO_TARGET(darcs-changelog No Darcs repository. ChangeLog is
missing from archive distribution.)
ENDIF(EXISTS ${Chicken_SOURCE_DIR}/ChangeLog)
ENDIF(EXISTS ${Chicken_SOURCE_DIR}/_darcs)
Brandon J. Van Every wrote:
Summary: emitting a CMakeLists.txt is never parallel with standard
coding
Mike Jackson wrote:
Is there a way to generate the list of Cmake keywords/Constants/Commands
that can appear in a Cmake file? I am trying to write a language definition
for TextMate on OS X and a list of these would make life simpler.
I seem to remember a posting about this to the list but I am
Brandon J. Van Every wrote:
Alan W. Irwin wrote:
This example of how CMake has quite casually taken over one autotoolized
project reflects in my opinion the fact that we live in a chaotic world
where small positive actions often have large positive consequences.
So in
such a world careful
Alan W. Irwin wrote:
Our windows platform is
still not completely full-featured, but it has many more features
(plotting
devices, language front-ends, etc.) than it did before on windows
which is
why we are making a development release a week from today.
It sounds like Chicken and PLplot
Alexander Neundorf wrote:
Hi Brandon,
Von: Brandon J. Van Every [EMAIL PROTECTED]
Getting started with CMake is easy. It lulls people into a false sense
of security about the amount of work involved... which from a CMake
promotion standpoint, is a good thing. I'm cynical about what
Length warning! As a preamble, I want to make it clear that I'm not a
proponent of Stop Energy.
http://www.userland.com/whatIsStopEnergy
I throw cold water at people, then tell them to knock themselves out
with whatever they feel needs doing.
Tanguy Krotoff wrote:
Brandon J. Van Every
Alan W. Irwin wrote:
[The Autotools] help was much appreciated, but
still the necessity for that help and the other factors I have mentioned
made me uneasy about continuing to depend on autotools.
Yes, the Autotools have many liabilities. Most notably, they are built
in layers, all with
Bill Hoffman wrote:
The problem with the shell, is that you can run cmake, then run make
from a different shell
For the most part that works on unix. zsh, bash, sh, csh basically
work the same. The trouble shows up
on windows.
Yep, open source on Windows is nothing but TROUBLE. It
Alexander Neundorf wrote:
CMake has some of that.
It has for OS:
UNIX
APPLE
WIN32
CYGWIN
MINGW
Cygwin is not an OS, it's a compiler.
The Bash that comes with Cygwin provides a filesystem environment.
Oftentimes when people compile on Windows in open source land, what they
really want /
Nags Venkat (nags) wrote:
Hi,
Just new to cmake.
We are evaluating cmake for building multiplatform (linux
and MS
windows)
targets using gcc (linux) and MS VS 2005 (ms windows).
Since we have
existing infrastructure in clearmake for windows, just
Peter Soetens wrote:
Quoting Brad King [EMAIL PROTECTED]:
Any time you change the compiler you have to wipe out the build tree and
start from scratch. Try running CMake like this instead:
$ rm -rf build; mkdir build; cd build
$ CC=gcc CXX=g++ cmake ..
I had read this comment before, but I
Christian Ehrlicher wrote:
I still don't understand why msys is needed anyway.
Because it exists and people use it. It is a standard support drill
for various people. That said, I'm not pleased with the official MSYS
distribution as of late. It runs ./configure stuff rather badly, and
Kai Sterker wrote:
A CMake compiled from MSYS (as opposed to cygwin) seems to be
a native Windows App with limited knowledge of stuff like /usr/local.
Data point: I use MinGW / MSYS as my primary build environment. I use a
CMake that was compiled with Visual Studio .NET 2003, i.e. standard
Alexander Neundorf wrote:
Von: "Brandon J. Van Every" [EMAIL PROTECTED]
Alexander Neundorf wrote:
Von: "Brandon J. Van Every" [EMAIL PROTECTED]
I would like more direct access to the CMake version number, and the
Xavier Larrode wrote:
Hello all,
Cmake is using by default /usr/bin/c++ to compile project.
Is it a way to set it ton another compiler like g++, or gcc-color.
You can set CMAKE_CXX_COMPILER to whatever you want.
This is documented at http://www.cmake.org/Wiki/CMake_Useful_Variables
but not in
David Cole wrote:
Brandon J. Van Every wrote:
Alexander Neundorf wrote:
Von: Brandon J. Van Every [EMAIL PROTECTED]
Alexander Neundorf wrote:
Von: Brandon J. Van Every [EMAIL PROTECTED]
I would like more direct access to the CMake version number, and
the ability to make
David Cole wrote:
Brandon J. Van Every wrote:
Anyways, I'll be happy to improve the readability of the Dashboard
Variables description when I'm more awake.
If you do, please don't claim it's comprehensive. It's a more complete
list than what's been manually entered so far on
http
David Cole wrote:
Brandon J. Van Every wrote:
Anyways, I'll be happy to improve the readability of the Dashboard
Variables description when I'm more awake.
If you do, please don't claim it's comprehensive. It's a more complete
list than what's been manually entered so far on
http
Martin Dobias wrote:
Actually CMakeSetup from CVS crashes for me even with so trivial
CMakeLists.txt like:
PROJECT (hello)
MESSAGE (STATUS hello world)
I cannot reproduce this. I just updated my CMake CVS. I used
CMakeSetup 2.4.3 with the Visual Studio .NET 2003 generator. I did an
Brandon J. Van Every wrote:
William A. Hoffman wrote:
At 08:17 AM 7/22/2006, Brad King wrote:
Brandon J. Van Every wrote:
Ok, the CMake 2.4.2 documentation for the projectName version of TRY_COMPILE is only 3 short sentences. IIUYC, you
Brandon J. Van Every wrote:
Brandon J. Van Every wrote:
William A. Hoffman wrote:
At 08:17 AM 7/22/2006, Brad King wrote:
You can create a macro to wrap this all up.
Regardless of the documentation, try-compile and not exec_process is what
Brad King wrote:
Brandon J. Van Every wrote:
I think the result is, quotes and backslashes cannot be reliably escaped
with respect to macro wrappers for ADD_CUSTOM_TARGET. Thus it is not
possible to write a macro that will TRY_COMPILE an arbitrary COMMAND.
So the feature that I
Brandon J. Van Every wrote:
I cannot find any well-defined point of control for escaping
backslashes or quotes in strings and macros. Different levels of CMake
are consuming them differently. This is preventing COMMAND from being
usable in any kind of portable manner.
I have
Filipe Sousa wrote:
Brandon J. Van Every wrote:
It would be nice if the CMake mailing list archives already had a search
button set up.
http://dir.gmane.org/gmane.comp.programming.tools.cmake.user
http://www.mail-archive.com/cmake@cmake.org/
On the archive
Alexander Neundorf wrote:
Maybe it would be possible to add some special cases, so that e.g. for the
FILE() commands and for the second parameter of CONFIGURE_FILE() relative paths
are interpreted relative to CMAKE_CURRENT_BINBARY_DIR, but IMO this would be
inconsistent.
Automagicality
Brandon J. Van Every wrote:
My CMakeLists.txt for the Chicken Scheme project has lots of examples
of ADD_CUSTOM_COMMAND to drive a language (Scheme) that is not C/C++.
That might be useful to you. A development snapshot is available at
http://www.call-with-current-continuation.org
Nathan A. Smith wrote:
On Sun, 2006-09-17 at 04:34 -0700, Brandon J. Van Every wrote:
Brandon J. Van Every wrote:
My CMakeLists.txt for the Chicken Scheme project has lots of
examples of ADD_CUSTOM_COMMAND to drive a language (Scheme) that is
not C/C
Philip Lowman wrote:
Requiring the user to specify else(cond1) and endif(cond1) may
prevent a few mistakes but it also gets kinda annoying as conditionals
get longer or change.
Agreed on being annoying as things get longer. It's a tradeoff between
safety and brevity.
It's *SUPPOSED* to
Alan W. Irwin wrote:
Agreed. I wish I had known about that CMAKE_ALLOW_LOOSE_LOOP_CONSTRUCTS
variable before the CMake build system was completed for PLplot. It
would
have made my life a whole lot easier.
A whole lot easier? Just how many nested IF..ELSE..ENDIF statements
does your
Alan W. Irwin wrote:
On 2006-09-16 12:11-0700 Brandon J. Van Every wrote:
It is the CMake language style to force the user to bracket their
conditional with matching conditions. Personally I think this is a
good design choice, especially as conditionals are nested deeper and
deeper
Alan W. Irwin wrote:
I am pleased with the way that CMake normally defaults to writing
files to
the build tree. This default behaviour encourages users to keep a clean,
unmolested source tree.
Thus, I was surprised recently to discover that
FILE(WRITE filename message to write... )
created
Nathan A. Smith wrote:
On Sat, 2006-09-16 at 16:38 -0700, Brandon J. Van Every wrote:
Nathan A. Smith wrote:
Hi,
I was wondering if it's possible to have cmake assemble assembly code
(*.s) -- and if so how? I tried something like this:
You
I'm making a casual effort to build the G3D library, which has CMake
support under development. It contains:
INCLUDE (FindSDL)
FIND_PACKAGE(SDL REQUIRED)
I have SDL binaries for VS7.1 on my system in E:\devel\vs71\SDL-1.2.11.
CMakeSetup complained that it was missing some SDL variables, so I
Do subdirectories inherit the INCLUDE_DIRECTORIES from their parents?
Do INCLUDE_DIRECTORIES set by children pop off and disappear when
returning to the parent?
Cheers,
Brandon Van Every
___
CMake mailing list
CMake@cmake.org
Benjamin Reed wrote:
On 9/6/06, Brandon J. Van Every [EMAIL PROTECTED] wrote:
Actually it's not invalid to compile it. That's what a cross-compiler
does. It's invalid to run it. CMake already has this distinction
between TRY_COMPILE and TRY_RUN, so if TRY_RUN is used inappropriately,
that's
On MSVC my CMakeLists.txt generates Debug, Release, MinSizeRel, and
RelWithDebInfo build types. I want to keep all 4 of 'em. I want to
select MinSizeRel as the default build, so that if an end user just
fires up BUILD_ALL and does nothing else, he'll get a MinSizeRel build.
The default
1 - 100 of 231 matches
Mail list logo
