Darren Weber wrote:
Using VTK_USE_RPATH=ON and building with that change resulted in full
path specifications in the .so file, but the path is now specific to
build directory, not the installation directory. So, how do we set
CMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=ON
How do you start ccmake? If
>> 3) Assume you have a lot of features to select including dependencies.
>> How can I realize to set a dependent feature in the CMake GUI setup, if
>> another is changed?
>> Example 1: your car can have a "radio" (bool) and "mp3" (bool). If
>> you select "mp3"=ON, "radio" is also set to ON.
>>
On Fri, Sep 5, 2008 at 10:12 PM, Philip Lowman <[EMAIL PROTECTED]> wrote:
> Incidentally, CMake doesn't have "/MAP" in it's list of understood VS flags
> so it will show up under the Additional Linking Flags section of the Linker
> properties and not where you're probably used to seeing it.
>
And
On Mon, Sep 1, 2008 at 3:27 AM, Ingrid Kemgoum <[EMAIL PROTECTED]>wrote:
> hi,
> i'm trying to export only some functions of a library with cmake
> i know with windows we use *__declspec(dllimport)* and *
> __declspec(dllexport)* to generate the appropriate .lib of the dll
> is there a manner of
On 8/21/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hello,
>
> we are currently developing with MPC (Makefile project creator) and I'm
> trying to find out what advantages we would have with a switch to CMake.
> First of all I would like to say, that CMake is very useful for me.
> Still ther
My setup: Win XP, VS 9 2008 Express, CMake 2.6.1
I'm having trouble getting cmake to generate nmakefiles (or VS solutions) w/
the static C/C++ runtime lib flags. I cannot figure out how to pass the
'/MT' flag (and NOT the /MD flag) to cl.exe.
My CMakeLists.txt is simple, with one directory, one
Using VTK_USE_RPATH=ON and building with that change resulted in full
path specifications in the .so file, but the path is now specific to
build directory, not the installation directory. So, how do we set
CMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=ON
FYI:
{{{
[ [EMAIL PROTECTED] ~/src/kitware/VTK_bui
On 05.09.08 16:13:21, Brad King wrote:
> Alexander Neundorf wrote:
> > On Friday 05 September 2008, Yann Cointepas wrote:
> I do not recommend searching for required dependencies inside
> "FooConfig.cmake". The process that put it there in the first place
> should have hard-coded inside it the loc
On Friday 05 September 2008, Brad King wrote:
...
> > Brad, any objections to set these two variables always, also in Config
> > mode ? If not I can do that if you're not faster.
>
> It doesn't hurt to have them available. Please send me a proposed patch.
See attached.
It also moves setting the v
On 05.09.08 21:46:17, Alexander Neundorf wrote:
> On Friday 05 September 2008, Andreas Pakulat wrote:
> > On 04.09.08 21:50:03, Alexander Neundorf wrote:
> ...
> > > This pops up a dialog in kdevelop saying "This project doesn't contain
> > > any files yet. Populate it ?"
> > >
> > > Why ? The file
VTK_USE_RPATH should be sufficient...
On Fri, Sep 5, 2008 at 5:51 PM, Darren Weber
<[EMAIL PROTECTED]>wrote:
> On Wed, Sep 3, 2008 at 3:28 PM, Mike Jackson
> <[EMAIL PROTECTED]> wrote:
> > Cross posting to vtkusers list as that may be more appropriate:
> >
> >
> > Can you rebuild VTK with these
On Wed, Sep 3, 2008 at 3:28 PM, Mike Jackson
<[EMAIL PROTECTED]> wrote:
> Cross posting to vtkusers list as that may be more appropriate:
>
>
> Can you rebuild VTK with these two settings:
>
> CMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=ON \
Where is this? I don't see it in ccmake. How do you set it?
>
On Fri, Sep 5, 2008 at 10:13 PM, Brad King <[EMAIL PROTECTED]> wrote:
> I disagree. The fact that FooConfig.cmake was loaded means that Foo
> *was* found. It is up to the module to report other information for
> consumption by the project. Perhaps the project finding Foo just wants
> to load s
Can somebody tell me how to enhance this so that it removes empty directories?
I am testing the OS X framework building support, and the problem is that all
the empty directory husks are left behind.
Also, how bad is it to remove the check:
IF(EXISTS \"\${file}\")\n")
I have code that creates
Alexander Neundorf wrote:
> On Friday 05 September 2008, Yann Cointepas wrote:
>> 1) Why do I need Foo_FIND_QUIET in FooConfig.cmake ?
>> First, I would like to display a message with the Foo version found if
>> QUIET is not used.
Okay.
>> 2) Why do I need Foo_FIND_REQUIRED in FooConfig.cmake ?
>
For our cross-compiling, we need to set some "peculiar" compiler options.
However, those options make CMake fail when it calls the compiler for
CheckTypeSize, testCCompiler, and CheckIncludeFile (what I call the "CMake
compiles").
Is there a way to differentiate the options passed on the CMake
On Friday 05 September 2008, Yann Cointepas wrote:
> 1) Why do I need Foo_FIND_QUIET in FooConfig.cmake ?
> First, I would like to display a message with the Foo version found if
> QUIET is not used.
>
> 2) Why do I need Foo_FIND_REQUIRED in FooConfig.cmake ?
> FooConfig.cmake will be packaged and
On Friday 05 September 2008, Andreas Pakulat wrote:
> On 04.09.08 21:50:03, Alexander Neundorf wrote:
...
> > This pops up a dialog in kdevelop saying "This project doesn't contain
> > any files yet. Populate it ?"
> >
> > Why ? The filelist file is not empty.
>
> For some reason kdevelop thinks it
Sean McBride wrote:
On 9/5/08 9:02 AM, Bill Hoffman said:
I have a release candidate (RC 3) for 2.6.2 ready for CMake.
Thanks.
The files can be found here:
http://www.cmake.org/files/v2.6/*RC-3*
The changes from 2.6.2 are as follows:
From 2.6.1 I assume?
Yes.
- .m compiled with gcc a
On 9/5/08 9:02 AM, Bill Hoffman said:
>I have a release candidate (RC 3) for 2.6.2 ready for CMake.
>
>Thanks.
>
>The files can be found here:
>
>http://www.cmake.org/files/v2.6/*RC-3*
>
>The changes from 2.6.2 are as follows:
>From 2.6.1 I assume?
>- .m compiled with gcc and g++ on mac
I'm cur
I have a release candidate (RC 3) for 2.6.2 ready for CMake.
Thanks.
The files can be found here:
http://www.cmake.org/files/v2.6/*RC-3*
The changes from 2.6.2 are as follows:
Changes in CMake 2.6.2 RC 3
- Fix bug, and remove extra closing > in visual fortran projects.
- Fix bug in ctest -C w
On Thu, Sep 4, 2008 at 8:24 PM, Christopher Harvey
<[EMAIL PROTECTED]>wrote:
> Hello list,
>
> I'll just start off by pasting my CMakeLists.txt, and I'll explain the
> problem right after.
>
> CMAKE_MINIMUM_REQUIRED(VERSION 2.6)
> ADD_LIBRARY(Portal SHARED
> BSPWorld.cc
>
On Thu, Sep 4, 2008 at 5:37 PM, Brad King <[EMAIL PROTECTED]> wrote:
> Philip Lowman wrote:
> > Ultimately, TARGET_LINK_LIBRARIES() works just fine the way it is with
> > the debug/optimized keywords satisfying normal use cases. The
> > debug/optimized keywords are in the lexicon and they aren't
1) Why do I need Foo_FIND_QUIET in FooConfig.cmake ?
First, I would like to display a message with the Foo version found if QUIET
is not used.
2) Why do I need Foo_FIND_REQUIRED in FooConfig.cmake ?
FooConfig.cmake will be packaged and installed on various systems (in a
Foo-devel package). Therefo
I'm trying to make add_test depend on the source of the test executable so if
it is changed then running "make test" will regenerate the executable first.
Any ideas?
--
Cheers,
Mike Arthur
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mai
I must say I am pretty glad about that.
Kind regards,
Cyril
Brad King a écrit :
Philip Lowman wrote:
Ultimately, TARGET_LINK_LIBRARIES() works just fine the way it is with
the debug/optimized keywords satisfying normal use cases. The
debug/optimized keywords are in the lexicon and they aren
26 matches
Mail list logo
