On 2. Dec, 2009, at 20:22 , Tyler Roscoe wrote:
On Wed, Dec 02, 2009 at 07:58:43PM +0100, Jörg Förstner wrote:
I thought CMake would find the custom command and generate the file
"gen.h"
Instead an error occurs, this is the output:
-- Configuring done
CMake Error in libfoo.so/CMakeLists.txt
-- Forwarded message --
From: John Drescher
Date: Wed, Dec 2, 2009 at 8:44 PM
Subject: Re: [CMake] A bug for Code::Blocks MinGW?
To: Song Zhiwei
> I use CMake to generate a Code::Blocks MinGW Makefiles for my project
> Module4Test. Module4Test.cbp contains lines as below:
>
>
NO one knows?
2009/12/2 Song Zhiwei :
> Hi all,
>
> I use CMake to generate a Code::Blocks MinGW Makefiles for my project
> Module4Test. Module4Test.cbp contains lines as below:
>
>
>
>
>
>
>
>
> As you noticed, no " are added aroun
On Wed, Dec 02, 2009 at 07:58:43PM +0100, Jörg Förstner wrote:
> I thought CMake would find the custom command and generate the file "gen.h"
> Instead an error occurs, this is the output:
>
> -- Configuring done
> CMake Error in libfoo.so/CMakeLists.txt:
> Cannot find source file "gen.h". Tried
Hi,
I have a generator which is given a data file "data.txt" and then generates an
include file "gen.h".
"gen.h" is told to CMake to be a generated file.
"gen.h" is added to the library.
I thought CMake would find the custom command and generate the file "gen.h"
Instead an error occurs, this is
Brad
Great. Thanks very much for looking at it.
JB
> -Original Message-
> From: Brad King [mailto:brad.k...@kitware.com]
> Sent: 02 December 2009 17:57
> To: Biddiscombe, John A.
> Cc: cmake@cmake.org
> Subject: Re: [CMake] Fortran name mangling
>
> Brad King wrote:
> > My guess is tha
I am using CMake to build several medium-sized C++ projects on several
Linux and Windows platforms (with an eye to supporting Mac and several
Unices eventually). The next step is to get a Continuous Integration
envrionment up and running.
>From my readings around the web and in _Mastering CMake_,
Brad King wrote:
> My guess is that CMake is generating a bad .vfproj file
It was generating a bad file in the case of per-source compiler definitions.
> perhaps
> due to the presence of both C and Fortran sources in one of the
> detection project targets.
This was not the cause because there ar
Just took a look at the Darwin-icc.cmake file. Yep, that is old. You
can try a few things.
You can just move aside the Darwin-icc.cmake file and see what
happens. It might work. I vaguely remember back in the ICC Version 9
days with OS X 10.4 that ICC did not like a few of the flags that
Michael Wild wrote:
On 2. Dec, 2009, at 16:36 , Sean McBride wrote:
On 12/2/09 10:10 AM, Bill Hoffman said:
Well, as Dave mentioned the -j flag only works with gmake. It does not
work with Xcode, as you tried here: :)
http://www.cdash.org/CDash/viewNotes.php?buildid=484307
Which is why
On 2. Dec, 2009, at 16:36 , Sean McBride wrote:
On 12/2/09 10:10 AM, Bill Hoffman said:
Well, as Dave mentioned the -j flag only works with gmake. It does
not
work with Xcode, as you tried here: :)
http://www.cdash.org/CDash/viewNotes.php?buildid=484307
Which is why nothing built for t
On 12/2/09 10:10 AM, Bill Hoffman said:
>Well, as Dave mentioned the -j flag only works with gmake. It does not
>work with Xcode, as you tried here: :)
>
>
>http://www.cdash.org/CDash/viewNotes.php?buildid=484307
>
>Which is why nothing built for that build. :)
Doh! I blindly changed all 30 o
What I don't understand is how the different files in the Platform's directory
work. There appease to be an OS, compiler, and OS-compiler. As the intel
compiler icc and icpc tries to emulate gcc, g++ respectfully on both the mac
and linux, I would think that it may make since for there to be a
Sean McBride wrote:
On 12/1/09 12:30 PM, Bill Hoffman said:
Is that better/worse/equivalent to David's suggestion of:
set(CTEST_BUILD_FLAGS -j4) ?
Worse most likely. :)
Both should work.
Thanks. If our dashboards are all red tomorrow, you'll know why. :)
Well, as Dave mentioned the -j
I just found out that in the new CMake-2.8 there is also
export(PACKAGE package_name)
which adds your build-tree to the user's package database and helps
CMake finding build-trees when using find_package(package_name) from
another project. However, this still requires that you create an
ex
Michael
Thank you. That seems to do what I need.
JB
> You can use
>
> export(TARGETS target ...
>[NAMESPACE namespace]
>[APPEND]
>FILE output_file
>)
>
> which you can then include() in your dependent project.
>
> Michael
___
Powere
On 2. Dec, 2009, at 10:09 , Biddiscombe, John A. wrote:
The command
INSTALL(
TARGETS ${PROJ_LIB_NAME}
EXPORT proj-targets
LIBRARY DESTINATION lib
ARCHIVE DESTINATION lib
RUNTIME DESTINATION bin
)
Works very nicely, when 'make install' is invoked, is there a way of
achieving a similar
The command
INSTALL(
TARGETS ${PROJ_LIB_NAME}
EXPORT proj-targets
LIBRARY DESTINATION lib
ARCHIVE DESTINATION lib
RUNTIME DESTINATION bin
)
Works very nicely, when 'make install' is invoked, is there a way of achieving
a similar result which is generated in the build directory -
Hi all,
I use CMake to generate a Code::Blocks MinGW Makefiles for my project
Module4Test. Module4Test.cbp contains lines as below:
As you noticed, no " are added around C:/Documents\
/Makefile, so the build fails.
Is i
19 matches
Mail list logo
