> Hi,
>
> The goal is to have an out-of-source build by default.
> The target is a programmer who compiles my package just
> to get the libraries needed for another project. He would
> have one less option to worry about, especially, if
> he wasn't familiar with CMake.
It is not exactl
It would be something like:
${CMAKE_SOURCE_DIR)/build
In other words it would be a subdirectory of the top-level
source dir.
Yes, it would be annoying if the default was set to 'c:\'
or '/tmp/'. However, it is safe to assume that if the user can
compile source in '/some/di
Kedzierski, Artur CIV NAVSURFWARCENDIV CORONA wrote:
The goal is to have an out-of-source build by default.
That means you'd have to pick an out-of-source directory for the user.
What do you imagine would be a non-annoying choice? Do you have enough
knowledge of the user's system
Hi,
I am sorry to bomb the mailing list with all my questions.
However, CMake is pretty exciting and my group is very likely to
migrate to it.
I found a link that mentions that CPACK can generate an RPM:
http://wiki.na-mic.org/Wiki/index.php/2006_Annual_Scientific_
On 9/16/06, Filipe Sousa <[EMAIL PROTECTED]> wrote:
Not anymore. You can doSET(CMAKE_ALLOW_LOOSE_LOOP_CONSTRUCTS 1)IF(cond1)ELSE()ENDIF()Wow, I never knew about that option.I think adding adding an ELSEIF extension should not be a high priority, since the same thing can be accomplished with existin
Hi,
The goal is to have an out-of-source build by default.
The target is a programmer who compiles my package just
to get the libraries needed for another project. He would
have one less option to worry about, especially, if
he wasn't familiar with CMake. That programmer
would be a
Kedzierski, Artur CIV NAVSURFWARCENDIV CORONA wrote:
Hi,
I am pretty new to CMake. Is there a way to specify a
default build dir in CMakeLists.txt?
What are you really trying to prevent from happening? Are you just
trying to get all your *.o files to appear in a particular place,
David C Thompson wrote:
What if you named the construct something other than ELSEIF? For
instance:
ONEOF( LABEL )
CONDITION( cond_1 )
statements here if cond_1 is true
OR_CONDITION( cond_2 )
statements here if cond_1 is false and cond_2 is true
... (more OR_CONDITION st
Alan W. Irwin wrote:
On 2006-09-17 20:27-0700 Brandon J. Van Every wrote:
... some rhetorical questions trying to convince me (and I guess
others) that I should not use CMAKE_ALLOW_LOOSE_LOOP_CONSTRUCTS.
I just don't think you value the social build engineering aspects of
this particular lang
Hi,
Some packages provide modules/programs that
provide information where they were installed. For
example, "FooLibrary" may provide
FooLibrary.m4 for auto-tools,
FooLibrary.pc for pkg-confing,
or
Foo-config for anything else.
As an author of a library, should I start
prov
On 2006-09-18 15:33-0700 David C Thompson wrote:
What if you named the construct something other than ELSEIF? For
instance:
ONEOF( LABEL )
CONDITION( cond_1 )
statements here if cond_1 is true
OR_CONDITION( cond_2 )
statements here if cond_1 is false and cond_2 is true
... (
Brad King wrote:
> Alan W. Irwin wrote:
> > So far all but one of those who responded to the discussion are in support
> > of the idea, but it is also fair to say that only a handful of subscribers
> > to this list have responded yet.
> >
> > I am particularly interested in the opinion of Bill Hof
Kedzierski, Artur CIV NAVSURFWARCENDIV CORONA wrote:
> I am pretty new to CMake. Is there a way to specify a
> default build dir in CMakeLists.txt?
The build directory is always a user selection. There can be more than
one build tree per source tree so trying to turn an in-source invocatio
Xavier Larrode wrote:
> I have done lots of FindPackage (for linux) for Ogre, Cegui, GLADE2
> etc... And i would like to make it generic.
[snip]
> So the question is, how to provide an argument to an INCLUDE (file) and
> use it
You can just set a variable before the INCLUDE command. However you
s
Alexander Neundorf wrote:
> I'd like to exclude some files from being scanned for dependencies, i.e. all
> files which have ecos/install/include/ as part of their path.
> I found CMAKE_C_INCLUDE_SCAN_REGEX, but I don't think I can use it for
> excluding directories, or is there a way to do this ?
On 2006-09-18 10:24-0400 Brad King wrote:
This is a reasonable request. I'll have to discuss it with the other
developers but it is at least worth putting in the bug tracker. Please
put in the request. At least then the final discussion will be
documented in an easy-to-reference place.
I am
Hi,
I am pretty new to CMake. Is there a way to specify a
default build dir in CMakeLists.txt? Something like:
CMAKE_BUILD_DIR(./build)
or
CMAKE_BUILD_DIR($SRC_DIR/build)
which would be equivalent to:
mkdir build
../ccmake
That should be portable as well. For exam
Hi,
I'd like to exclude some files from being scanned for dependencies, i.e. all
files which have ecos/install/include/ as part of their path.
I found CMAKE_C_INCLUDE_SCAN_REGEX, but I don't think I can use it for
excluding directories, or is there a way to do this ?
Thanks
Alex
--
"Feel free
Hi all,
I have done lots of FindPackage (for linux) for Ogre, Cegui, GLADE2
etc... And i would like to make it generic.
For now, i juste make a "query replace" from libglade-2.0 for instance
to OGRE and i would like to make it better.
Here is an example of my code with REGEX wich separate a
On 9/18/06 10:32 AM, "Brad King" <[EMAIL PROTECTED]> wrote:
> Mike Jackson wrote:
>> Has anyone created an HDF5 cmake build script for the HDF5 1.6.5
>> distribution?
>>
>> I took the cmake file from the XMDF project and put in the sources for the
>> HDF5 1.6.5 project and tried to build but got
Mike Jackson wrote:
> Has anyone created an HDF5 cmake build script for the HDF5 1.6.5
> distribution?
>
> I took the cmake file from the XMDF project and put in the sources for the
> HDF5 1.6.5 project and tried to build but got some link errors. I am
> assuming that I _all_ the sources didn't ne
Brandon J. Van Every wrote:
> I'm going up the Dart / CTest learning curve. How am I supposed to
> implement tests that depend on my project already being installed?
> Doing what I thought would be obvious, I found a way to crash
> CMakeSetup. I've reported this as bug #3779.
> ADD_DEPENDENCIES
Alan W. Irwin wrote:
> So far all but one of those who responded to the discussion are in support
> of the idea, but it is also fair to say that only a handful of subscribers
> to this list have responded yet.
>
> I am particularly interested in the opinion of Bill Hoffman, Brad King, and
> other
Has anyone created an HDF5 cmake build script for the HDF5 1.6.5
distribution?
I took the cmake file from the XMDF project and put in the sources for the
HDF5 1.6.5 project and tried to build but got some link errors. I am
assuming that I _all_ the sources didn't need to go in but I am unsure whic
You guys should add yourselves to the list of projects using CMake on
the CMake Wiki:
http://www.cmake.org/Wiki/CMake_Projects
Thanks for sharing your story here...
- David
Alan W. Irwin wrote:
I am happy to report that the PLplot developers have essentially
completed
their new CMake Build
principal topic which is whether "elseif" should be
implemented for CMake or not.
I'd like to vote in favour of an ELSEIF construct
JB
--
John Biddiscombe,email:biddisco @ cscs.ch
http://www.cscs.ch/about/BJohn.php
CSCS, Swiss National Supercomputing Centre | Tel
On 2006-09-17 20:27-0700 Brandon J. Van Every wrote:
... some rhetorical questions trying to convince me (and I guess
others) that I should not use CMAKE_ALLOW_LOOSE_LOOP_CONSTRUCTS.
Regardless of such argumentation, the basic point remains,
CMAKE_ALLOW_LOOSE_LOOP_CONSTRUCTS is already in the CM
27 matches
Mail list logo
