Daniel wrote:
I have tried using the --debug-output command line option but it doesn't
seem to change anything. Can someone elaborate on this? I'm not trying
to debug anything in particular just curious.
--
Daniel
I found this in the man page now that I'm no longer in Windows:
Print extra
Is there a way to clear this list ?
Intrying to convert pango til Cmake I need to change a define inside the same
source library. So I guess I need to clear this internal list or at least
remove the define in question before adding it again to avoid compiler warnings.
The problem with removing
Hi there,
Could someone please add to the general output of ctest --help that
a user can get access to the full documentation using:
ctest --help-command CTEST_TEST
it is also unclear from the output of ctest --help, that ctest
--help COMMAND will output the terse documentation.
Thanks
Would
RAISE_SCOPE(var1 var2 ... varN)
be better ?
Why was the syntax changed from that to
RAISE_SCOPE(varname value) ?
(which was basically a set() and that's why converted to
set(... PARENT_SCOPE) )
The old syntax of raise scope often required that you first set the value of
the variable
FUNCTION(SET_VAR1 varname)
SET(${varname} There's science to do PARENT_SCOPE)
ENDFUNCTION(SET_VAR1)
FUNCTION(SET_VAR2 varname)
SET_VAR1(${varname})
ENDFUNCTION(SET_VAR2)
SET_VAR2(foo)
MESSAGE(${foo})
Obviously foo is not set, since it is now set in SET_VAR2 scope. Bummer.
So
At 2/18/2008 10:10 AM, Ken Martin wrote:
FUNCTION(SET_VAR2 varname)
SET_VAR1(${varname})
ENDFUNCTION(SET_VAR2)
And you should live with that. And like it dang it! :)
I'm linking it but I'm kinda surprised you wouldn't go for something
beautiful *and* eternally classic like a new
On Monday 18 February 2008, Martin Lütken wrote:
Is there a way to clear this list ?
Intrying to convert pango til Cmake I need to change a define inside the
same source library. So I guess I need to clear this internal list or at
least remove the define in question before adding it again to
I'm setting up a project repository with subversion where I'll have external
libs linked in via
svn:externals svn property. Each external lib will have a CMakeLists.txt file.
Ideally, I'd like to have the possibility to include N subdirectories without
having to alter
the CMakeLists.txt file
On Feb 18, 2008 3:34 PM, Fernando Cacciola [EMAIL PROTECTED] wrote:
XXXConfig.cmake should ...
FindXXX.cmake shoud ...
UseXXX.cmake should set include directories, libraries, compiler and linker
flags, etc, based on the settings defined in a XXXConfig.cmake that must has
been processed
Hi,
Consider a library XXX that uses cmake as it's build system. Here's what I
think those three files should do:
XXXConfig.cmake should be generated by the cmake script that configures the
library and it should contain the settings specific to that configuration
(such as source and binary
Fernando Cacciola wrote:
XXXConfig.cmake should be generated by the cmake script that configures
the library and it should contain the settings specific to that
configuration (such as source and binary folders, detected third party
dependencies, needed flags, etc)
Correct.
FindXXX.cmake
On Monday 18 February 2008, Robert Bielik wrote:
I'm setting up a project repository with subversion where I'll have
external libs linked in via svn:externals svn property. Each external lib
will have a CMakeLists.txt file.
Ideally, I'd like to have the possibility to include N subdirectories
Hi,
I just downloaded the new CMake version 2.4 patch 8. This command now works:
SET(VS_MULTITHREADED_DEBUG_IGNORE_LIBRARY_FLAGS
/NODEFAULTLIB:nafxcwd.lib
/NODEFAULTLIB:libcmtd.lib
)
I want to do the same thing for my release builds, kind of like:
Ah you're right, I had it paired with a call to:
SET_TARGET_PROPERTIES(myapp PROPERTIES
LINK_FLAGS_DEBUG
${VS_MULTITHREADED_DEBUG_IGNORE_LIBRARY_FLAGS})
which I overlooked - I added the same for the release version and it
work. I haven't
Hi,
Is there a way to get one of your libraries to be included in your
project before default libraries? Tough to explain - I'm compiling
specifically for visual studio 2005. When CMake is done creating the
solution files, I can see the additional dependencies string looks
like this:
Mark Wyszomierski wrote:
Hi,
I just downloaded the new CMake version 2.4 patch 8. This command now works:
SET(VS_MULTITHREADED_DEBUG_IGNORE_LIBRARY_FLAGS
/NODEFAULTLIB:nafxcwd.lib
/NODEFAULTLIB:libcmtd.lib
)
I want to do the same thing for my release builds, kind of
I'm just thinking here, so please tell me if this wouldn't work...but wouldn't
it be easier to have a CMake macro that could (a) find the SVN (or TSVN)
install, (b) checkout/export from a repository provided at minimal the URL and
revision are provided, and optionally prompts for a
[EMAIL PROTECTED] ~/kk/cmake-glob-bug $ cat CMakeLists.txt
FILE (GLOB TESTS ./test/ *.cpp)
ls -liha test/
total 0
3635635 drwxr-xr-x 3 pepone pepone 72 2008-02-19 04:56 .
998787 drwxr-xr-x 4 pepone pepone 160 2008-02-19 04:52 ..
3635679 drwxr-xr-x 2 pepone pepone 48 2008-02-19 04:56 .svn
Mathieu Malaterre wrote:
Ok this was yet-another-weird-dll thingy, one cannot do:
class GDCM_EXPORT String : std::string { ... }
Please, learn a little bit more about C++. You should never inherit
from std::string (or any std::* container) as their functions or
destructor are not virtual.
19 matches
Mail list logo
