On Fri, Feb 27, 2009 at 5:24 PM, Brad King brad.k...@kitware.com wrote:
Philip Lowman wrote:
I wasn't thinking of it in that context when I said that. Yes, I think
you're correct and I've noticed that behavior before. I usually work around
it with make foo/fast assuming foo is the shared
On Friday 27 February 2009, Philip Lowman wrote:
On Fri, Feb 27, 2009 at 1:13 PM, Matt Williams li...@milliams.com wrote:
...
There is no indication in the readme.txt which is preferred though I have
been
assuming the mixed case version. Based on bits and pieces I guess I am
right
(for
On Thursday 26 February 2009, Phil Smith wrote:
I got back on this, and found a big part of my problem. The Wiki page says:
Edit CMakeASM_FOOInformation.cmake. ... then include the generic
CMakeASMInformation.cmake. and later:
Edit CMakeDetermineASM_FOOCompiler.cmake. ...then include the
2009/3/1 Alexander Neundorf a.neundorf-w...@gmx.net:
On Friday 27 February 2009, Steve Huston wrote:
Thanks for the advice, Bill.
My situation is somewhat different, though. The output source files
are not known ahead of time. Thus, the general scheme is:
- build runs the source generator;
Yes, that was it. Thank you. I had hacked it into working by just setting
CMAKE_ASM_COMPILER, but that was clearly a hack.
One nit that I did have to work around: it doesn't seem to support operands on
the compiler name, though in trolling through code trying to understand what
I'd done wrong,
Hello, I ran into a problem with getting the CTest to run when
linking with a DLL.
1) My program links with ITK, and I build this as a DLL on windows.
2) During testing, my program needs to find the ITK dll. I do not
wish to add to the global path.
3) My understanding is that the workaround
On Sunday 01 March 2009, Phil Smith wrote:
Yes, that was it. Thank you.
You're welcome :-)
...
I'd offer some updates to http://www.kwwidgets.org/Wiki/CMake/Assembler to
help others avoid my idiocy if you're interested.
Yes, please do so.
Alex
On Sunday 01 March 2009, you wrote:
2009/3/1 Alexander Neundorf a.neundorf-w...@gmx.net:
On Friday 27 February 2009, Steve Huston wrote:
...
Can you run the source generator at cmake time ?
Yes you are right and I miss that,
if the generator is launched at CMake time it may help a lot.
I had another idea. About how many generated files are there, and how
big are they? It they are smallish, you could generate a single source
file that includes the generated files.
generated.cxx
#include gen1.cxx
#include gen2.cxx
#include gen3.cxx
...
Then you could have a custom command
Hello too,
We use something like
if(BUILD_SHARED_LIBS AND WIN32 AND NOT CYGWIN)
SET(LIBRARY_OUTPUT_PATH ${CMAKE_CURRENT_BINARY_DIR}/dll)
endif(BUILD_SHARED_LIBS AND WIN32 AND NOT CYGWIN)
so that all DLLs end up in one directory (since we build many of them,
otherwise they would be scattered
On Sun, Mar 1, 2009 at 3:55 PM, Alexander Neundorf
a.neundorf-w...@gmx.netwrote:
On Friday 27 February 2009, Philip Lowman wrote:
On Fri, Feb 27, 2009 at 1:13 PM, Matt Williams li...@milliams.com
wrote:
...
There is no indication in the readme.txt which is preferred though I
have
been
From: Werner Smekal sme...@iap.tuwien.ac.at
Subject: Re: [CMake] [CTest] DLLs, scripts, and build types
To: gregsharp@yahoo.com
Cc: cmake@cmake.org
Date: Sunday, March 1, 2009, 2:11 PM
Hello too,
We use something like
if(BUILD_SHARED_LIBS AND WIN32 AND NOT CYGWIN)
From: Eric Noulard eric.noul...@gmail.com
Can you run the source generator at cmake time ?
Yes you are right and I miss that,
if the generator is launched at CMake time it may help a lot.
Moreover I would say that the source file list generated by the
generator may be some kind of CMake
13 matches
Mail list logo
