Bill Hoffman wrote:
Philip Lowman wrote:
I've reopened this feature request as a bug because
1.) using ctest does not work
2.) the ENVIRONMENT test property is not documented
Discovered both of these issues tonight after looking into Ankit's
request and vaguely recalling this being
Philip Lowman wrote:
For the first cut I think starting out with keeping the CMakified
sources in the project would be fine. Many people are never going to
want anything more complicated than this and we know that this will at
least work for now.
CMake can already untar with -E mode.
Patrick Spendrin wrote:
Does this sound interesting?
Yes.
As I am maintaining patches for some libraries and working for some
others, it would be nice to have such a unified system to keep doubled
work amount low.
This has some more points:
We would not have to maintain our patches in our
Aaron Turner wrote:
Trying to get up to speed on this thread- apologies if I missed this.
Long story short, as an OSS developer and new Cmake user, I'm less
interested in getting libfoo building with Cmake and a lot more
interested in CMake modules for detecting and using libfoo in my own
BRM wrote:
I read through this thread, and I think there may be a better route -
Instead of trying to create all kinds of patches, etc; why not make a
simple tool to convert an autotool project to CMake and vice-versa?
Perhaps call it 'autotool2cmake'?
This way, the process becomes simpler:
Eric Noulard wrote:
2009/2/16 Bill Hoffman bill.hoff...@kitware.com:
Philip Lowman wrote:
A tertiary goal would be convincing the 3rd party dependencies to switch
to CMake for their native build systems.
I don't really like the propaganda idea :-)
Particularly for Open Source projects
Birju Prajapati wrote:
I’ve figured it out. I added the following lines into the root
CMakeLists.txt file:
SET(CMAKE_CXX_FLAGS -m64)
SET(CMAKE_C_FLAGS -m64)
SET(CMAKE_EXE_LINKER_FLAGS -m64)
SET(CMAKE_MODULE_LINKER_FLAGS -m64)
SET(CMAKE_SHARED_LINKER_FLAGS -m64)
That is not the
John Biddiscombe wrote:
Brad
OK. I'm using 2.6.2 I'll let you know if the problem continues with
2.6.3 or later (won't try it right away because I don't want to force a
rebuild of anything just now - but soon)
Changing from 2.6.2 to 2.6.3 should not trigger a full rebuild...
However, if
David Cole wrote:
Just use Build Solution. Rebuild Solution causes *all* build steps
everywhere to re-run, even when nothing has changed, including the ones
that re-run cmake if a CMakeLists.txt file changes.
If you want to start over entirely (effective Rebuild Solution) then
wipe your
David Doria wrote:
If I have many executables in the same project (ie same CMakeLists.txt
file), it seems like I shouldn't have to do this:
set(Sources File1.cpp File1.cpp )
ADD_EXECUTABLE(Test1 Test1.cpp ${Sources})
ADD_EXECUTABLE(Test2 Test2.cpp ${Sources})
because it is compiling File1
Aaron Turner wrote:
That is not the preferable way to do this. As it hard codes flags into the
CMake file. The way I would do it is:
export CXXFLAGS=-m64
export CFLAGS=-m64
export LDFLAGS=-m64
cmake ../myproject
If those environment variables are set BEFORE you run cmake, then cmake will
Steven Van Ingelgem wrote:
Hi all,
How can I (on windows) do the following:
cmake .. -DCMAKE_USE_NEW_CURL=1
It always results in an error (upon compilation)?
Scanning dependencies of target cmcurl
The new curl is currently untested. So, to avoid the error, don't try
to use it.
-Bill
jessepe...@gmail.com wrote:
The real solution is to create a new sub-class of the visual studio
generator for the intel compiler, or maybe it is just a flag on the
existing generator. Calling ICProjConvert seems like a bad idea, and I
would not accept a generator based on that solution into
Bartlett, Roscoe A wrote:
Hello,
I am trying to get memory checking to work in an extended Ctest script
that calls ctest_memcheck(...). However, when I do I get the error message:
SetCTestConfiguration:BuildDirectory:/home/rabartl/PROJECTS/dashboards/Trilinos.base/SERIAL_DEBUG/BUILD
On behalf of myself, Ken, Brad, Dave, Alex and the rest of the
CMake team, we are pleased to announce that CMake 2.6.3 is
available for download at:
http://www.cmake.org/cmake/resources/software.html
The documentation for 2.6.3 can be found here:
Stephan Aiche wrote:
It was an empty directory. Also inspecting the CMakeCache.txt shows
//C++ compiler
CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/g++-4.2
For me it seems, that the generator is ignoring this variable while
generating the Xcode project files
Stephan
That will not work with
Sean McBride wrote:
Hi all,
Back in early April 2008 we debated whether CMake's .app should be named
simply CMake.app or something with the version number, like CMake
2.6-3.app.
I just updated from 2.6.2 to 2.6.3, and went to rebuild my VTK. It now says:
/bin/sh: /Applications/CMake
There is a FindCuda.cmake here, that I have looked at:
http://www.sci.utah.edu/~abe/FindCuda.html
I am thinking of adding it to CMake, he uses custom_commands for Cuda.
-Bill
___
Powered by www.kitware.com
Visit other Kitware open-source projects
scott mc wrote:
I've compiled CMake for Haiku but it's insisting on putting some
things into /usr/local which Haiku does not have and does not even
allow. Haiku uses /boot/common instead, so for most ports I've done
with autotools we simply use ./configure --prefix=/boot/common, how is
this
Reisinger, Thomas Karl wrote:
Hello,
AUX_SOURCE_DIRECTORY by default searches for the following extensions -
.c .C .c++ .cc .cpp .cxx .m .M .mm .h .hh .h++ .hm .hpp .hxx .in .txx
Because CMake works case sensitive I need to ADD another extension
.CPP to the command AUX_SOURCE_DIRECTORY.
Bartlett, Roscoe A wrote:
Does anyone know how to get valgrind to not search for errors in the parent but
only in the children?
No way to do that, but you can create a suppression file. If you add
--gen-suppressions=all to the valgrind command line it will create
entries for the
Steve Huston wrote:
I'm working on a project that involves generating a large chunk of the
sources from separate definitions. The set of generated source files
is not known before it is generated.
The approach I've tried so far (and I'm very new to cmake) is to
define a custom_command that does
Pavel Shevaev wrote:
Folks, any idea why this can be happening?
I have the following lines in my CMakeLists.txt:
...
ENABLE_TESTING()
INCLUDE(CTest)
ADD_TEST(AllTests {$project_SOURCE_DIR}/scripts/runtests)
...
I also have properly configured CTestConfig.cmake in the same
directory with
Pavel Shevaev wrote:
Can you create a complete but small example that shows the problem?
Ok, I tried to extract the minimal non-working example from my CMakeLists.txt.
foo/CMakeLists.txt:
==
cmake_minimum_required(VERSION 2.6 FATAL_ERROR)
in advance.
-Bill
--
Bill Hoffman
Kitware, Inc.
28 Corporate Drive
Clifton Park, NY 12065
bill.hoff...@kitware.com
http://www.kitware.com
518-371-3971 (phone and fax)
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http
I had another idea. About how many generated files are there, and how
big are they? It they are smallish, you could generate a single source
file that includes the generated files.
generated.cxx
#include gen1.cxx
#include gen2.cxx
#include gen3.cxx
...
Then you could have a custom command
Alexander Neundorf wrote:
On Monday 02 March 2009, Nicolas Slythe (Intern) wrote:
SET(TARGET_SOURCE
./utils/utils.cxx
./test/test.cxx
./test/test1.cxx
)
ADD_DEFINITIONS (
-DK_NODLL
-DK_DISABLE_UI
)
ADD_LIBRARY (
test
SHARED
${TARGET_SOURCE}
)
I don't have
Mathieu Malaterre wrote:
Hi there,
Why is the firefox logo redistributed within cmake:
No idea!
That file does not seem to be referenced by the build or any of the
tests, so I have removed it.
$ cvs commit -m ENH: remove unused file CPack.background.png.in
Committer: Bill Hoffman
Mathieu Malaterre wrote:
On Tue, Mar 3, 2009 at 4:20 PM, kent williams nkwmailingli...@gmail.com wrote:
Lather, Rinse, Repeat. After 2 or 3 go-arounds, CCMake is happy and
lets you generate your build files.
And if I recall correctly, earlier versions (2.3? 2.4?) did not act this way.
Yup,
Michael Jackson wrote:
The subtle difference is this line from the macro help section:
Note that the parameters to a macro and values such as ARGN are not
variables in the usual CMake sense. They are string replacements much
like the c preprocessor would do with a macro. If you want true
Robert Dailey wrote:
Hi,
I noticed after switching to version 2.6.3 that header files (with HPP
extension) are marked as Exclude from build in Visual Studio 2008. Is
this behavior by design? If so, why?
You don't want to compile .hpp files do you?
-Bill
Robert Dailey wrote:
But by default visual studio does not compile HPP or H files. I've
*never* had this problem in any version of visual studio starting from
version 6.
So, what is the problem? CMake marks all files that should not be
compiled as do not compile. Is this causing trouble?
Clemens Arth wrote:
Well, it's on you to decide, but I'd still suggest that Bill's
workaround also goes into the cvs for the next release to make
everything more bullet-proof...
I have already done the commit with the fix. For now, I would suggest
just letting it do something for the
Pavel Shevaev wrote:
On Wed, Mar 4, 2009 at 7:22 PM, David Cole david.c...@kitware.com wrote:
Did you call ENABLE_TESTING before any ADD_TEST calls in your
CMakeLists.txt?
Yes :(
Please create a full working test case that shows this problem.
-Bill
Daniele Galdi wrote:
Dear CMake developers,
I'm sending you this email to thank you all for your precious and always
prompt support in using this amazing build system.
We just developed and released a free tool, built using cmake.
We put a link to your site in our technology section:
kent williams wrote:
So the problem with CCMake forgetting valid user input stems from the
entire CMakeCache.txt file getting deleted if there's a compiler
mismatch?
Yes, that is what happens. The use case that this was supposed to
address was this:
ccmake ../source
- oops, I did not
Adolfo Rodríguez wrote:
If none of the developers sees any important issue with this proposal,
I'll submit a feature request based on what has been discussed in the
current thread.
Thanks all,
I am not sure I like the idea. It is too make specific. The makefiles
that cmake generates
Philip Lowman wrote:
The CTest documentation online appears like it wasn't generated from the
2.6.3 source release. Just noticed this by accident tonight and wanted
to mention it.
http://www.cmake.org/cmake/help/ctest2.6docs.html#command:ctest_update
* *|ctest_submit|*: Submits the
Marcel Loose wrote:
After further inspection, I think my observation holds true for all
Check*.cmake files in the Modules directory, not just the
CheckC(XX)SourceCompiles files.
It is a cache variable so that the test is not run over and over each
time CMake is run. unset is in cmake 2.6.3.
Wojciech Migda wrote:
Hi all,
I have a build system with several subtargets residing in respective
subfolders. What is important - I'm using common binary directory for
all targets. The command I use is:
ADD_SUBDIRECTORY( nth_subfolder common_binary_dir )
Each directory must be unique.
Wojciech Migda wrote:
Hi again,
this workaround seems to do a trick:
in cmDependsC::WriteDependencies I've added a local variable to store
path to the source file being scanned for dependencies:
std::string root_dir =
cmSystemTools::GetFilenamePath(this-LocalGenerator-Convert(src,
Silvio Frischknecht wrote:
If I enable_testing() executables or libraries called test don't build
anymore.
here's a simple example:
CMakeLists.txt:
cmake_minimum_required(VERSION 2.6)
project(FooBar)
enable_testing()
add_executable(test test.c)
add_test(baz test)
If this is not going to be
laur...@marzu.org wrote:
Hello all,
I've just began trying to port my project from autoconf to CMake and
I've got a question.
My project use 'vpath' variable in order to locate source file from
different directory according to argument pass to autoconf.
Typically, my C++ source file
Pau Garcia i Quiles wrote:
Yes, I'm using QT4_WRAP_CPP (with plans to move to automoc), but that
right-click, compile to run moc is useful (no need to close the
solution or reload projects) and it's what VC++ developers are used
to.
With CMake, you can still right click and compile, it will
Pau Garcia i Quiles wrote:
On Mon, Mar 9, 2009 at 4:24 PM, Bill Hoffman bill.hoff...@kitware.com wrote:
Pau Garcia i Quiles wrote:
Yes, I'm using QT4_WRAP_CPP (with plans to move to automoc), but that
right-click, compile to run moc is useful (no need to close the
solution or reload projects
Pau Garcia i Quiles wrote:
What does not work is what I am doing: I'm listing the .h files as
source files so that they show in the VC++ project. Now, given that
header files are marked as excluded from build, VC++ disables
right-click-and-compile for those header files.
The .h file is not
Naram Qashat wrote:
I have a CMake project that I have been testing with various verisons of
CMake 2.4.x and 2.6.x to make sure it works as far back as 2.4.0, due to
not knowing what version of CMake our users will be using since a lot of
them use shells. In some instances, I have to read
Naram Qashat wrote:
Bill Hoffman wrote:
Naram Qashat wrote:
I have a CMake project that I have been testing with various verisons
of CMake 2.4.x and 2.6.x to make sure it works as far back as 2.4.0,
due to not knowing what version of CMake our users will be using
since a lot of them use
Marcel Loose wrote:
Hi all,
I feel rather stupid, but I fail to see whether there's any difference
between a CMake option (which is stored in the cache as a variable of
type bool) and a CMake variable of type bool that's being cached.
Both can be modified in a GUI like ccmake.
Is there any
Naram Qashat wrote:
myscript.cmake
file(READ ${FILE} ALL_STRINGS)
...
message(${RESULT})
-Bill
Thanks, that worked very well. The only problems I had, though, were
that the quotes were passed to the new invocation of CMake and that I
had to use ERROR_VARIABLE instead of
Alexander Neundorf wrote:
On Wednesday 11 March 2009, Bill Hoffman wrote:
...
Great, glad it works for you. At some point 2.X will be in the past... :)
Oh, plans for cmake 3.0 ?
oops, 2.4.X.
-Bill
___
Powered by www.kitware.com
Visit other
Alexander Neundorf wrote:
I'm using CMake 2.6.2 and Eclipse CDT5 (not CDT4, could this be an issue?)
I don't think so.
We could add some special variable, like
CMAKE_MAKEFILE_PROJECT_FLAGS or CMAKE_MAKEFILE_PARALLELITY, and use this in
the makefile-based generators to set the -jx parameter
Claus Höfele wrote:
Hi everyone,
I've recently switched to cmake to generate Visual Studio project
files for a project of mine and it's working great so far.
One issue that bugs me is that header files end up being disabled in
Visual Studio (Excluded From Build property is set for the header
Claus Höfele wrote:
Thanks for the quick replies.
I'm using cmake 2.6.3 + Visual Studio 8 2005 SP1
Playing around further with the file properties in Visual Studio, it
looks like VS only checks the syntax of a file if the Tool property is
set to C/C++ Compiler Tool. However, this setting will
Denis Scherbakov wrote:
Dear CMake list subscripers,
I have a project with verious ADD_LIBRARY/ADD_EXECUTABLE targets in
different subdirectories. Some of these targets depend on mico corba,
some don't. As well as some depend on libxml2, some don't.
We have developers working on
Andreas Schneider wrote:
Hi,
what means
- Fix set cache FORCE and -D command line to work together
I've recognized, that -DFOO=something doesn't overwrite cache settings anymore
which are set to FORCE. Is this true?
If yes, then the documentation should be updated. -D states:
Denis Scherbakov wrote:
Eric,
Your solution requires a developer to know too much about the
project,
which is not always true and basically to answer a full-scale
questionnaire before compilation. What if it is a new developer? What if
it is not a developer, but a user who expects everything
Hicham Mouline wrote:
Hello,
cmake 2.6.3.
There has been a number of modifications which have caused all headers in the
generated project files .vcproj to be excluded frm build
(the red minus sign next to the file in Solution explorer)
I have searched from inside VStudio the string
Hicham Mouline wrote:
-Original Message-
From: John Drescher [mailto:dresche...@gmail.com]
Sent: 13 March 2009 21:25
To: Bill Hoffman
Cc: Hicham Mouline; cmake@cmake.org
Subject: Re: [CMake] VS2005 all headers are excluded
Is this causing issues with the building of your project
Joachim Geiger wrote:
Hello,
this is more or less to document a bug in the cmake version 2.6.2 seen
on AIX version 5.3 when using the option to redefine the fortran
compiler. For example:
11:13 ../cmake-2.6.2-AIX-powerpc/bin/cmake ../test_project
-DCMAKE_Fortran_COMPILER=f95
What if you do
Bill Hoffman wrote:
Joachim Geiger wrote:
Hello,
this is more or less to document a bug in the cmake version 2.6.2 seen
on AIX version 5.3 when using the option to redefine the fortran
compiler. For example:
11:13 ../cmake-2.6.2-AIX-powerpc/bin/cmake ../test_project
-DCMAKE_Fortran_COMPILER=f95
Denis Scherbakov wrote:
I see progress jumping even on freshly CMake prepared, but never compiled tree.
So is this a bug or a feature?
The progress is an approximation at best. It should always betting
bigger, and it should not go over 100%. Working with make there really
is not a
Matthew Woehlke wrote:
Makefile : cmake_check_build_system
Shouldn't this rather be:
Makefile: list of CMakeLists.txt, etc
cmake_check_build_system
?
...in which case, the only thing that should get checked is if the
CMakeLists.txt are newer than the Makefile. So in most cases this
Matthew Woehlke wrote:
Bill Hoffman wrote:
Matthew Woehlke wrote:
Makefile : cmake_check_build_system
Shouldn't this rather be:
Makefile: list of CMakeLists.txt, etc
cmake_check_build_system
?
...in which case, the only thing that should get checked is if the
CMakeLists.txt are newer
Steven Wilson wrote:
Following the FAQ
(http://www.cmake.org/Wiki/CMake_FAQ#I_want_a_new_feature_in_CMake._What_should_I_do.3F)
I have submitted a couple feature requests(8725, 8743) to the cmake
bugs database along with source patches implementing the features. I
haven't yet received any
Michael Jackson wrote:
On Mar 20, 2009, at 5:30 AM, Eric Noulard wrote:
2009/3/20 Philip Lowman phi...@yhbt.com:
On Thu, Mar 19, 2009 at 11:18 PM, Michael Jackson
mike.jack...@bluequartz.net wrote:
I am trying to find a nice portable solution for generating version
strings based on the
Michael Jackson wrote:
I don't think you could do this as a set of variables. It would be
better as some sort of command. file(GETDATE result) or something.
-Bill
Well, I could but I am really interested in _why_ I would _not_ want to?
Besides the obvious that the variables would
John Drescher wrote:
Makes sense. So then I should be opening cmake-gui from the compiler's
command prompt instead of the shortcut on the desktop. Not a big deal
I am one to use the command prompt all the time windows or linux..
I'm not very familar with cmake-gui but I don't see another
John Drescher wrote:
On Fri, Mar 20, 2009 at 3:49 PM, John Drescher dresche...@gmail.com wrote:
If you use the IDE generators for CMake, you do not need to modify the
environment at all. It is only when using nmake or make, that you need an
environment that is setup to run the compiler. If
John Drescher wrote:
But then with this setup cmake-2.6.3 is scanning my vc6 headers and
libs to generate vc2005 projects.
This has not caused me any problems but I am unsure if checks like
partial template specification are being used or is this part of cmake
not really used if I use the .sln
John Drescher wrote:
On Fri, Mar 20, 2009 at 5:42 PM, John Drescher dresche...@gmail.com wrote:
If you select Visual Studio 8 2005 as a generator, it should not use VC6.
Please make sure you start with an empty binary directory, with no
CmakeCache.txt file.
I just created a new build tree
Bill Lorensen wrote:
I don't use boost, but a quick google search found this:
https://svn.boost.org/trac/boost/wiki/CMakeConfigAndBuild
Here is another wiki about the Boost CMake work:
https://svn.boost.org/trac/boost/wiki/CMake
Currently, there are cmakelists.txt files in the trunk svn
Vladimir Prus wrote:
On Saturday 21 March 2009 22:28:43 Piotr Dobrogost wrote:
Hi
On the following page
http://www.cmake.org/cmake/help/documentation.html
one can read the following statement
In addition many other popular open source projects use CMake such as
VTK, ITK, ParaView, VXL,
Bill Hoffman wrote:
Vladimir Prus wrote:
Therefore, that page is at very least inaccurate. I would like to request
CMake developers fix that page.
Gotcha, will do.
Done:
http://www.cmake.org/cmake/help/documentation.html
Sorry for any confusion.
-Bill
Marcel Loose wrote:
Hi all,
I was trying to figure out how to generate a preprocessed file. By
browsing the CMake modules and by printing all CMake variables I
discovered CMAKE_LANG_CREATE_PREPROCESSED_SOURCE variables. That
suggests that there is support for generating preprocessed files.
Andreas Pokorny wrote:
Hi,
Any news from the WinCE Support front?
There are four patch tickets in mantis:
http://cmake.org/Bug/view.php?id=7919
http://cmake.org/Bug/view.php?id=8486
http://cmake.org/Bug/view.php?id=8102
http://cmake.org/Bug/view.php?id=7434
Are there any tests included in
Clemens Arth wrote:
Bill Hoffman wrote:
Andreas Pokorny wrote:
Hi,
Any news from the WinCE Support front?
There are four patch tickets in mantis:
http://cmake.org/Bug/view.php?id=7919
http://cmake.org/Bug/view.php?id=8486
http://cmake.org/Bug/view.php?id=8102
http://cmake.org/Bug/view.php?id
Andreas Pokorny wrote:
Hello,
2009/3/23 Bill Hoffman bill.hoff...@kitware.com:
[..]
Basically, something that runs the new code. Compile a WinCE project, and
somehow verify that it compiled it correctly.
So we need a couple of source files that pull in at least some basic
API headers
Adolfo Rodríguez wrote:
Hi,
I have a project that uses CTest. I'm using the auto-generated
BUILD_TESTING variable to enable/disable the test-related parts of my
build tree. What strikes me as unusual is that when I build my project
with BUILD_TESTING set to ON (hence all test executables
Adolfo Rodríguez wrote:
I'm not setting any -D flags that depend on BUILD_TESTING. I only use
the variable to guard entering the subdirectories where tests are generated:
if(BUILD_TESTING)
add_subdirectory(test)
endif(BUILD_TESTING)
I am working in a project that adds a test subfolder to
Alastair Rankine wrote:
Hi,
I must be blind but I can't see a way for CTest to pass a command line
argument to a test executable?
I've tried using
--test-command testExe myargs
... but this causes it to not find the executable.
Any help appreciated, thanks.
Just put --test-command last
Mostly to fix the issue with Visual Studio and header files that was
introduced with CMake 2.6.3, I am working on 2.6.4. I have a release
candidate that can be found here:
http://www.cmake.org/files/v2.6
Specifically, the windows one with the visual studio fix is here:
Bartlett, Roscoe A wrote:
Hello,
Does anyone know if the XCode generator for CMake support Fortran as a
compiler? We have a Trilinos developer that tried to use CMake to
generate an XCode project but it does not know how to handle the Fortran
files.
Xcode itself does not support
Robert Dailey wrote:
What exactly does this mean:
- Enforce unique binary directories
Does this mean instead of all executables going inside bin/debug, that
they go inside of something like bin/project_name/debug (For the debug
configuration, it would be likewise for release)?
No, it
KSpam wrote:
My build system relies heavily on CMAKE_CURRENT_LIST_FILE. For instance, I
typically get a variable for the directory containing the current list file
as follows:
get_filename_component(scriptDir ${CMAKE_CURRENT_LIST_FILE} PATH)
This has worked in prior versions of CMake;
Daniel Nelson wrote:
So it sounds like the only way to fix this would be to write a separate
flags.make file for every object file that has compile/define flags set? I opened
this as issue 8787 in the bug tracker.
We tried that, it was way to slow with all those files. Especially on
Benne, Kyle wrote:
Hello All,
I have been experimenting with CMake to compile a large Fortran
project with the Intel Fortran compiler ifort. I am having trouble
getting the executable to link with the static intel libraries, because
CMake is adding the linker flag i_dynamic and it is
Steven Van Ingelgem wrote:
What I did (and solved the issue) is:
file(READ zconf.in.h ZCONF_H)
STRING(REPLACE HAVE_STD_HEADERS_H ${HAVE_STD_HEADERS_H} ${ZCONF_H})
file(WRITE zconf.test ${ZCONF_H})
Especially the quotes around the variable are important as otherwise
CMake think it's an array
-wrapped paragraphs
delimited by newlines. Indented text is considered pre-formatted.
-Bill
--
Bill Hoffman
Kitware, Inc.
28 Corporate Drive
Clifton Park, NY 12065
bill.hoff...@kitware.com
http://www.kitware.com
518-371-3971 (phone and fax)
___
Powered
Kenneth Boyd wrote:
Apologies for not replying to the list. Forwarding:
Original Message
Subject: Re: [CMake] building within msys/mingw
Date: Fri, 27 Mar 2009 22:07:37 -0500
From: Kenneth Boyd zaim...@zaimoni.com
To: Jason Addison jraddi...@gmail.com
James Bigler wrote:
Ah, yes. I also was getting globbing expressions and regular
expressions mixed up.
From the docs (and experimentation), it looks like CMake only supports
*, ?, and [], but not {} which would be required to do what we want:
file(GLOB_RECURSE sources *.{h,cpp})
CMake
Robert Dailey wrote:
But it does work! I've tested it several times with much success! I'm
not sure what you're saying about *.c, *.cxx, and *.h. Could you
explain? Also, I won't have access to a bash shell on Windows. I'd
rather CMake just work instead of trying to find silly workarounds
Philip Lowman wrote:
I'll put in the feature request for {} and at some point in the
future it can be addressed.
Can someone point me to a definition of what glob is supposed to
have in it? It seems to vary from php glob, perl glob, various
different shell globs,
I have seen several requests for an autoheader type function to be added
to CMake. I have never used autoheader, but I gather it takes a list of
variables and generates a config.h.in file automatically. Does anyone
on the list have experience with autoheader? If so, what would a nice
CMake
Hendrik Sattler wrote:
Zitat von Bill Hoffman bill.hoff...@kitware.com:
I have seen several requests for an autoheader type function to be
added to CMake. I have never used autoheader, but I gather it takes a
list of variables and generates a config.h.in file automatically. Does
anyone
Robert Dailey wrote:
Just like regex, I don't believe there is an official standard for
glob expressions. I think what you should do is implement the common
intersection set of functionality just like everyone else does. You're
trying to find the right way to do it when a right way has not
Alexander Neundorf wrote:
On Monday 30 March 2009, Robert Dailey wrote:
Hi,
What's the proper way to define a list? Suppose I have 3 words: Foo, Bar,
and Baz. I want these 3 strings to be in a list called Stuff. Would I do
this:
set( Stuff Foo;Bar;Baz )
Is this correct?
Yes, this is
Marcel Loose wrote:
Hi Bill,
Wouldn't it be better if CMake kept track of these variables internally.
I mean, usually the HAS_X variables are the result of calls to
check_include_file() and check_function_exists(). The Autotools handle
this under the hood.
CMake might keep a list of these
James Bigler wrote:
If this feature comes to fruition, I would like the ability to specify
which flags make it into what header. In one project I worked on all
our configuration defines were in a single header. This caused
extremely long recompiles if something happened to change the one
BRM wrote:
How about:
# Each variable can have a registered filter name - packages/programs/libraries
would use their name
cmake_autoheader_add_variable(has_some_other_package, filter_name)
# user controls what the output file is
# User can generate a C #define method (default method if
601 - 700 of 2920 matches
Mail list logo
