Frank Hilliger wrote:
I want to remove the /GZ flag which is set for Windows Visual C++ compilers
in CMAKE_CXX_FLAGS_DEBUG_INIT. Furthermore I want to remove some .lib files
defined in CMAKE_C_STANDARD_LIBRARIES_INIT.
How I can achieve this without touching
This is the second try, since gmane seems to swallowed the first one...
Hello,
I have trouble when trying to run the Visual Studio 7 generator on a Fortran
project, while NMake Makefiles works fine. The installed fortran compiler
is intels ifort.
A minimal test case:
CMakeLists.txt
I wrote:
when I use the Visual Studio 7 .NET 2003 generator, CMake generates
one .vcproj file for each library/application,
and one .sln file that contains all the .vcproj files, with
appropriate dependencies. So far so good.
What I would like in addition is a .sln file for each
On 8/10/07, Eric Noulard [EMAIL PROTECTED] wrote:
I think I perfectly understand your point but I would
say that adding pre-parsing phase where
The main CMakeLists.txt pre-parsed in order to list
the OPTION and their desc statement would indeed be feasible
cmake -p would show INCONDITIONAL
Brandon Van Every wrote:
It might be reasonable, however, to show OPTIONS resolved at the
current scope. And to note whether conditional options exist, i.e.
Warning: conditional options detected. You are advised to run
(CMakeSetup|CCMake) and resolve them iteravely. Or the opposite:
All
Brandon Van Every wrote:
On 8/10/07, James Bigler [EMAIL PROTECTED] wrote:
both supported, I build both. On the Mac, where static libraries are
officially depreciated, I don't. There's an OPTION to build them if
you really really want to scrounge around with that. And if you want
On 8/10/07, Bill Hoffman [EMAIL PROTECTED] wrote:
Brandon Van Every wrote:
It might be reasonable, however, to show OPTIONS resolved at the
current scope. And to note whether conditional options exist, i.e.
Warning: conditional options detected. You are advised to run
I am having the following issue. I want to create both a libFOO.a and a
libFOO.so. Note that the libFOO.so is composed of more sources than the
libFOO.a.
I use OUTPUT_NAME in order so they have the same name. I can make the
FOOSTATIC, libFOO.a, target, just fine. However, making the
Quoting Brandon Van Every [EMAIL PROTECTED]:
On 8/10/07, Christian Convey [EMAIL PROTECTED] wrote:
What I'm trying to avoid is having to go into all 70 of those
subdirectories and modifying each of those 70 CMakeLists.txt files,
adding an INSTALL command to each file.
Why avoid that? You
Yes it does... It's a copy if different operation.
On 8/10/07, Christian Convey [EMAIL PROTECTED] wrote:
It looks to me like CONFIGURE_FILE is a no-op when the target file
already exists *and* has the exact same content that it would have if
CONFIGURE_FILE ran.
I'm basing me belief by
Christian Convey schrieb:
It looks to me like CONFIGURE_FILE is a no-op when the target file
already exists *and* has the exact same content that it would have if
CONFIGURE_FILE ran.
I'm basing me belief by looking running some experiments and looking
at timestamps.
But this isn't mentioned in
Juan Sanchez wrote:
I am having the following issue. I want to create both a libFOO.a and a
libFOO.so. Note that the libFOO.so is composed of more sources than the
libFOO.a.
I use OUTPUT_NAME in order so they have the same name. I can make the
FOOSTATIC, libFOO.a, target, just fine.
Pau Garcia i Quiles wrote:
I took a quick look a few weeks ago and replacing the current regex
library with PCRE seems easy (most of the work would be replacing
the regexp's in current .cmake files with their POSIX equivalents). Is
Kitware or anyone else already working on that?
Sounds like
Hi Bill,
Thanks, it works when I do this in SET_TARGET_PROPERTIES.
Juan
Juan Sanchez wrote:
Hi Bill,
What's the proper syntax? Setting the variable in CMakeLists.txt doesn't
work. Neither does setting it in my initial Cache file (loaded with
cmake -C).
SET (CLEAN_DIRECT_OUTPUT 1 CACHE
Quoting Bill Hoffman [EMAIL PROTECTED]:
Pau Garcia i Quiles wrote:
I took a quick look a few weeks ago and replacing the current regex
library with PCRE seems easy (most of the work would be
replacing the regexp's in current .cmake files with their POSIX
equivalents). Is Kitware or
On 8/10/07, James Bigler [EMAIL PROTECTED] wrote:
both supported, I build both. On the Mac, where static libraries are
officially depreciated, I don't. There's an OPTION to build them if
you really really want to scrounge around with that. And if you want
I haven't heard this, albeit I
It looks to me like CONFIGURE_FILE is a no-op when the target file
already exists *and* has the exact same content that it would have if
CONFIGURE_FILE ran.
I'm basing me belief by looking running some experiments and looking
at timestamps.
But this isn't mentioned in the online docs for
Pau Garcia i Quiles wrote:
Another option would be to have something like STRING(
POSIX_REGEX_MATCH ...), etc but I like the ~ better.
I think this would be my choice...
-Bill
___
CMake mailing list
CMake@cmake.org
Brandon Van Every wrote:
On 8/10/07, Bill Hoffman [EMAIL PROTECTED] wrote:
Brandon Van Every wrote:
http://developer.apple.com/qa/qa2001/qa1118.html
I am not sure this means static libraries are deprecated. It just
means that completely static
executables are not
On 8/10/07, dave [EMAIL PROTECTED] wrote:
On Fri, Aug 10, 2007 at 12:38:08PM -0400, Brandon Van Every wrote:
The command line is the retraining tool.
How about a CMake utility that accepts autotools files as input
and creates CMake output files for all the autotools features which
can be
Eric Noulard wrote:
2007/8/10, Bill Hoffman [EMAIL PROTECTED]:
The process for configuring a cmake project has to be iterative because
options can
be nested inside if statements. ccmake, cmake -i and CMakeSetup all do
the following:
1. Configure
2. Write CMakeCache.txt
3. Did the
Hello,
I want to read the current state (build type debug/release) out of Visual
Studio 2005 using CMake. I tried a lot of things. Please can anyone help me?
Thanks,
Markus
___
CMake mailing list
CMake@cmake.org
Hello,
I want to read the current state (build type debug/release) out of Visual
Studio 2005 using CMake. I tried a lot of things. Please can anyone help me?
Thanks,
Markus
___
CMake mailing list
CMake@cmake.org
On 8/10/07, Bill Hoffman [EMAIL PROTECTED] wrote:
Brandon Van Every wrote:
http://developer.apple.com/qa/qa2001/qa1118.html
I am not sure this means static libraries are deprecated. It just
means that completely static
executables are not recommended. They want you to use the dynamic
On 8/10/07, Bill Hoffman [EMAIL PROTECTED] wrote:
Basically this requires a paradigm shift for autotools users.
This discussion makes me think we need to see the fundamental problem
differently. These are not CMake is ugly, CMake lacks something
problems. Rather, CMake has a lot of things that
I appears that -Wmost is hard coded in the CFLAGS for XCode
projects. Is there anyway to disable this without change the cmamke
code and re-compiling it?
Rick M
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
On 8/10/07, dave [EMAIL PROTECTED] wrote:
I understand your desire to be compensated for projects that have the
potential for being very large sinks of time and energy. I don't have
any real experience with gnu autotools. I have noticed that there are
*many* versions closely following each
2007/8/10, gga [EMAIL PROTECTED]:
Brandon Van Every wrote:
On 8/8/07, gga [EMAIL PROTECTED] wrote:
I know I can pass -D symbols to cmake to modify its behavior and that
windows also has its ugly CmakeSetup gui.
Ugly? Geez, what are you, a candidate for Windows Aero or something?
On Friday 10 August 2007 15:55, Brandon Van Every wrote:
...
Totally horrible brain dead idea. If it weren't for your other
suggestions, I'd say you should be shot.
...
You are a sick, depraved individual.
Brandon, I think this went to far, maybe even if there would have been
smileys.
Please
Brandon Van Every wrote:
I don't trust smileys, people may not notice them. The above was
clearly a joke, except for the shooting part.
Let me state the matter seriously. Anyone who thinks that more
control characters should be inserted into a regex stream, that has no
wide based standard
Hi Bill,
What's the proper syntax? Setting the variable in CMakeLists.txt doesn't
work. Neither does setting it in my initial Cache file (loaded with
cmake -C).
SET (CLEAN_DIRECT_OUTPUT 1 CACHE STRING 1)
Thanks,
Juan
Bill Hoffman wrote:
Juan Sanchez wrote:
I am having the following issue.
On 8/10/07, Christian Convey [EMAIL PROTECTED] wrote:
What I'm trying to avoid is having to go into all 70 of those
subdirectories and modifying each of those 70 CMakeLists.txt files,
adding an INSTALL command to each file.
Why avoid that? You could just write some regex replaces in CMake
On 8/10/07, Eric Noulard [EMAIL PROTECTED] wrote:
I think there is a confusion here.
./configure does not give you full help unless the writer
of the configure scripts did it using --enable-xx or --with-xxx.
I may well write ugly configure.ac (in
Hello!
I have try to build CMake for Win23/MinGW
When I run the bootstrap i get an Error!
---
C:\svn_tools\branches\bin\win32\mingw-3.4.5\bin\make: *** No rule to make
target `/c/temp/cmake-2.4.7/cmake-2.4.7/Source/cmake.cxx', needed by
`cmake.o'. Stop.
---
??
Have try different
On 8/10/07, Alexander Neundorf [EMAIL PROTECTED] wrote:
On Friday 10 August 2007 15:55, Brandon Van Every wrote:
...
Totally horrible brain dead idea. If it weren't for your other
suggestions, I'd say you should be shot.
...
You are a sick, depraved individual.
Brandon, I think this
. (lots of stuff).
Since CMake is a language that is parsed when cmake is run, there is no
way to present the user
with all possible options until you run cmake. Options can be included
inside an if statement.
This is actually a good thing. For example, if the user enables
2007/8/10, Bill Hoffman [EMAIL PROTECTED]:
The process for configuring a cmake project has to be iterative because
options can
be nested inside if statements. ccmake, cmake -i and CMakeSetup all do
the following:
1. Configure
2. Write CMakeCache.txt
3. Did the CMakeCache.txt change ?
On 8/10/07 1:16 PM, Bill Hoffman said:
both supported, I build both. On the Mac, where static libraries are
officially depreciated, I don't. There's an OPTION to build them if
you really really want to scrounge around with that. And if you want
I haven't heard this, albeit I don't do much
I've got a top-level directory with *70* subdirectories. Each
subdirectory defines a sub-PROJECT (I'm not sure this was necessary),
and typically one build target (either a library or program).
I want to define two INSTALL components, which collectively will
install all 70 targets. At my
Juan Sanchez wrote:
I am having the following issue. I want to create both a libFOO.a and a
libFOO.so. Note that the libFOO.so is composed of more sources than the
libFOO.a.
I use OUTPUT_NAME in order so they have the same name. I can make the
FOOSTATIC, libFOO.a, target, just fine.
I would like to use cmake to build a set of single target projects
(each project generates either one library or one executable). I
understand how to handle dependencies on external packages with the
fooFind.cmake scripts, but I don't know how to deal with internal
CMake built packages. There is
On 8/10/07, Bill Hoffman [EMAIL PROTECTED] wrote:
Brandon Van Every wrote:
I don't trust smileys, people may not notice them. The above was
clearly a joke, except for the shooting part.
Let me state the matter seriously.
Sure, it is a bad idea, and technically I agree with you. I
On 8/10/07, Kyle Heath [EMAIL PROTECTED] wrote:
I would like to use cmake to build a set of single target projects
(each project generates either one library or one executable). I
understand how to handle dependencies on external packages with the
fooFind.cmake scripts, but I don't know how
43 matches
Mail list logo
