Original-Nachricht
Datum: Thu, 07 Dec 2006 17:50:12 -0500
Von: Darby J Van Uitert <[EMAIL PROTECTED]>
An: cmake@cmake.org
Betreff: [CMake] combining projects
> Hi,
>
> I have a current project building under CMake which has multiple parts
> that I want to keep separate. It
Von: Jens Hannemann <[EMAIL PROTECTED]>
...
> This works fine with the usual Unix Makefiles generator (as a matter of
> fact,
> I can actually drop the LIBFOO_HEADERS dependency in ADD_LIBRARY, and
> the packages and dependencies are generated just fine). But when using
> the KDevelop3 generator
Hi,
I have a current project building under CMake which has multiple parts
that I want to keep separate. It has a group of core libraries, and
then an application with a gui that is separate--very similar to the
Insight Toolkit and Insight Applications except for they are in the same
reposit
> --
> Message: 5
> Date: Wed, 06 Dec 2006 10:56:39 -0800
> From: "Brandon J. Van Every" <[EMAIL PROTECTED]>
> Subject: Re: [CMake] Re: Weird if nesting problem
> To: cmake
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On Thursday 07 December 2006 20:37, Tristan Carel wrote:
> On 12/7/06, Axel Roebel <[EMAIL PROTECTED]> wrote:
> > On Wednesday 06 December 2006 17:36, Axel Roebel wrote:
> > > > I will test the module tomorrow.
> > > > Could you please put a RC2 of the `FindSWIG.cmake' on the bug
> > > > tracker?
>
Hi folks,
I'm trying to build a library with the following directory structure:
foo
|
+--libfoo
||
|+--foo.cpp
|
+--foo
|
+--foo.h
This keeps the header files containing the API separate and allows for
inclusion in the #include style.
The top-level CMakeLists.txt loo
Weiguang Guan wrote:
Hi Bill,
Thank you so much. Here I confirm that your guess is right. I paste
part of the output below. Is there a workaround?
"C:\Program Files\CMake 2.4\bin\cmake.exe"
-HZ:\visualization\software\buildWin\libraries\
thirdParty\VTK\CMakeFiles\CMakeTmp
-BZ:\visua
On 12/7/06, Axel Roebel <[EMAIL PROTECTED]> wrote:
On Wednesday 06 December 2006 17:36, Axel Roebel wrote:
> > I will test the module tomorrow.
> > Could you please put a RC2 of the `FindSWIG.cmake' on the bug tracker?
>
> That may take a day or too.
>
> I'll let you know.
There it is, called Fi
On 2006-12-07 19:41+0100 Axel Roebel wrote:
On Wednesday 06 December 2006 17:36, Axel Roebel wrote:
I will test the module tomorrow.
Could you please put a RC2 of the `FindSWIG.cmake' on the bug tracker?
That may take a day or too.
I'll let you know.
There it is, called FindSWIG.cmake-2
I
On Wednesday 06 December 2006 17:36, Axel Roebel wrote:
> > I will test the module tomorrow.
> > Could you please put a RC2 of the `FindSWIG.cmake' on the bug tracker?
>
> That may take a day or too.
>
> I'll let you know.
There it is, called FindSWIG.cmake-2
It should take care of all your comme
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
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 is given:
3>-- Ski
Hi Bill,
Thank you so much. Here I confirm that your guess is right. I paste part
of the output below. Is there a workaround?
"C:\Program Files\CMake 2.4\bin\cmake.exe"
-HZ:\visualization\software\buildWin\libraries\
thirdParty\VTK\CMakeFiles\CMakeTmp
-BZ:\visualization\software\buil
I would like to create some sort of config file for CMake so that
when I clean build ParaView on OS X I can have all the necessary
settings already to go. I am also compiling in my own modules so that
is at least 3 "configure" passes in CCMake.. which is getting tiresome..
I tried creating
Magnus wrote:
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 fro
CMAKE_BUILD_TYPE is automatically set to a default initial value by CMake in
most cases before it gets to your IF(NOT DEFINED... (So, it's "always"
defined -- in your case.)
It is conditionally set from different cmake scripts that are run based on
generator and compiler chosen. It is not set at
16 matches
Mail list logo
