Hi,
I'm trying to bootstrap cmake on a OS/390 mainframe. I have succeeded so far
that the cmake executable is created in the Bootstrap.cmk folder but the
actual bootstrapping of cmake itself fails.
Attached are two logfiles. The first is from the bootstap and the other is
from the bootstrapp
Hi,
I'm trying to setup a cmake system where as cmake will by
default be a release build. If someone issues cmake
-DCMAKE_BUILD_TYPE:STRING=debug it should overwrite the default to
produce a debug build.
The only way I've found to do this is with:
IF(CMAKE_BUILD_TYPE MATCHES "debug"
Weiguang Guan wrote:
Hi Mathieu,
I am working directly on Windows XP rather than on Cygwin layer. I
think this might be a cmake issue, because the error message box
appears after I hit the "Configure" button of CMake, and the same
error message pops up when configuring an ITK build with cmake
Hi Mathieu,
I am working directly on Windows XP rather than on Cygwin layer. I think this
might be a cmake issue, because the error message box appears after I hit the
"Configure" button of CMake, and the same error message pops up when
configuring an ITK build with cmake.
The error message
Hi Mathieu,
I am working directly on Windows XP rather than on Cygwin layer. I think
this might be a cmake issue, because the error message box appears after
I hit the "Configure" button of CMake, and the same error message pops up
when configuring an ITK build with cmake.
The error message
Bill Hoffman wrote:
> Axel Roebel wrote:
> >> 1. Look for swig executable
> >> 2. use `swig -swiglib' to get the swiglib path
> >> 3. FIND_PATH(SWIG_DIR swig.swg ${SWIG_outlib} /usr/share/swig1.3 ...)
> >
> > could you tell me why you add this path
> > /usr/share/swig1.3 ?
>
> This is a an old modu
Wheeler, Frederick W (GE, Research) wrote:
correctly. Then you can use make -j3 to do the build. Due to a bug
in the cygwin make, you have to use this patched one:
http://www.cmake.org/files/make.exe
I just took a crack at this, not to be able to build in parallel (w/
-j3), but to use
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
CMake List:
I'm trying out using Cygwin GNU make to do a .net 2003 build of VXL
from the Cygwin bash command line. It seems to take a lot longer than
NMake and
I'm wondering if anyone knows for sure why or has any kind of
solution. Details below ...
Bill Hoffman recently wrote to the VXL Users
> Message: 1
Date: Tue, 05 Dec 2006 20:28:36 -0800 (PST)
From: "Alan W. Irwin" <[EMAIL PROTECTED]>
Subject: Re: [CMake] Weird if nesting problem
To: cmake
Message-ID: <[EMAIL PROTECTED]>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
On 2006-12-05 20:05-0800 Brandon J. Van Every wro
On Wednesday 06 December 2006 18:03, Alexander Neundorf wrote:
> Original-Nachricht
> Datum: Wed, 6 Dec 2006 14:34:38 +0100
> Von: "Sebastian Trüg" <[EMAIL PROTECTED]>
> An: cmake@cmake.org
> Betreff: Re: [CMake] Advanced cmake in Nepomuk-KDE: changing vars at build
> time
>
> >
Original-Nachricht
Datum: Wed, 6 Dec 2006 14:34:38 +0100
Von: "Sebastian Trüg" <[EMAIL PROTECTED]>
An: cmake@cmake.org
Betreff: Re: [CMake] Advanced cmake in Nepomuk-KDE: changing vars at build time
> In case anyone is interested. I solved it:
>
> made the tool subdir indepen
Axel Roebel wrote:
1. Look for swig executable
2. use `swig -swiglib' to get the swiglib path
3. FIND_PATH(SWIG_DIR swig.swg ${SWIG_outlib} /usr/share/swig1.3 ...)
could you tell me why you add this path
/usr/share/swig1.3 ?
This is a an old module, the FIND_* stuff has changed a
Dear David,
Quoting David Cole <[EMAIL PROTECTED]>:
> What's the motivation behind your question?
It's just an end user demand. I'm porting from the autotools to Cmake.
With the autotools makefiles the building users were used to get a simple
final message echoed on their terminal going l
On Wednesday 06 December 2006 00:58, Tristan Carel wrote:
> On 12/5/06, Axel Roebel <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I just started to add swig support to our project
> > http://sourceforge.net/projects/sdif. The project supports
> > swig bindings to perl, python and java.
> >
> > I insta
What's the motivation behind your question?
(1) Do you want to do this custom command at the end of *every* developer's
*every* call to make from your top level?
(2) Or do you want to post an automatic build from a build machine when the
build is 'done'...?
(3) Something else?
For (2), I'd recom
Dear David Cole,
Quoting David Cole <[EMAIL PROTECTED]>:
> You could add a custom target that depends on all the other targets in your
> project.
True enough. But for big projects this places a global constraint on all
CMakeLists.txt maintainers who get to update the custom global target
d
You could add a custom target that depends on all the other targets in your
project.
On 12/6/06, Eric BOIX <[EMAIL PROTECTED]> wrote:
Dear cmake users,
I would like to launch a command after ALL the targets are build (think
of e.g. displaying a small message). I could achieve this with
Dear cmake users,
I would like to launch a command after ALL the targets are build (think
of e.g. displaying a small message). I could achieve this with an
ad-hoc ADD_CUSTOM_COMMAND( TARGET target POST_BUILD COMMAND ...)
at the condition of knowing the name of cmake's internal global buil
In case anyone is interested. I solved it:
made the tool subdir independant from the main CmakeLists.txt and call cmake
and make manually via execute_command. works like a charm.
On Tuesday 05 December 2006 11:39, Sebastian Trüg wrote:
> Hi,
>
> I have the following problem:
>
> In the Nepomuk-K
Original-Nachricht
Datum: Tue, 05 Dec 2006 21:04:23 +0100
Von: Michel Hermier <[EMAIL PROTECTED]>
An: [EMAIL PROTECTED]
Betreff: Re: [CMake] PKGCONFIG backward compatibility on CVS trunk.
> Bill Hoffman wrote:
> > Michel Hermier wrote:
> >> Hi,
> >>
> >> I'm experiencing a str
On 12/6/06, Bill Hoffman <[EMAIL PROTECTED]> wrote:
Crni Gorac wrote:
> OK, I've tried in the meantime various arrangements with
> ADD_CUSTOM_TARGET(), but seems hard to employ it to have CMake to put
> following simple dependency of an executable "foo" on system library
> "libbar.a" into generat
22 matches
Mail list logo
