I work on a similarly large project and have found that building shared
libraries for development is much faster (in terms of compile/link time)
when making small changes (working in Visual Studio). Nightly or test builds
can use static libraries to produce single executables.
Provided you have se
{FOO})
IF(myFOO)
... ... ...
ENDIF(myFOO)
HTH,
David
On 7/19/07, *Mike Talbot* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Hi,
I'm trying to work out how to test for an environment variable in
an IF
command, the following doesn't work:
SE
what the right syntax for doing this is, please?
Thanks,
Mike
--
Mike Talbot
Core Petrel Architect (Abingdon)
Schlumberger
Lambourn Court, Wyndyke Furlong,
Abingdon Business Park, Abingdon,
Oxfordshire, OX14 1UJ, UK
Office: +44 (0)1235 543 488
Mobile: +44 (0)7790 382 746
__
Alexander Neundorf wrote:
On Wednesday 11 July 2007 06:01, Mike Talbot wrote:
Hi,
I'm working on quite a large baseline (>100 projects) that uses cmake
and am trying to find a way to allow users to select only a subset of
projects to include in the generated solution/makefile.
they are set
(but they were the first time).
Any ideas on how to solve this or a better approach?
Thanks
Mike
--
Mike Talbot
Core Petrel Architect (Abingdon)
Schlumberger
Lambourn Court, Wyndyke Furlong,
Abingdon Business Park, Abingdon,
Oxfordshire, OX14 1UJ, UK
Office: +44 (0)1235 54
Cristian Adam wrote:
Please update your findboost.cmake with the changes the original
poster made, by
adding boost-1.34 (and others) to SUFFIX_FOR_PATH.
Done.
I have also submitted these changes as a feature request
http://public.kitware.com/Bug/bug.php?op=show&bugid=5057&pos=0
Regards,
Mik
I have made some enhancements to FindBoost.cmake to try to add support
for the boost libraries (attached).
Basic use is something like this:
FIND_PACKAGE(Boost)
INCLUDE_DIRECTORIES(${Boost_INCLUDE_DIRS})
ADD_EXECUTABLE(signal signal.cpp)
TARGET_LINK_LIBRARIES(signal ${Boost_signal_LIBRARIES})
Hi,
I have created a custom build rule to generate doxygen documentation for
my project like this:
FIND_PACKAGE(Doxygen)
CONFIGURE_FILE(
${PROJECT_SOURCE_DIR}/doxyfile.in
${PROJECT_BINARY_DIR}/doxyfile)
ADD_CUSTOM_TARGET(DOCUMENTATION
COMMAND ${DOXYGEN} ${PROJECT_BINARY_DIR}/doxyfile)
T
the cmake generator
code to use a different GUID when writing out external projects or if
someone has a suggestion on how to fix the GUID in the generated
solution automatically that would be helpful.
(I am using cmake 2.4.2)
Many thanks,
Mike
--
Mike Talbot
Senior Software Developer
Schlumberge
Hi,
I have a bunch of tests that are created with something like this:
ADD_TEST(mytest "executable_dir/${CTEST_CONFIGURATION_TYPE}/mytest.exe")
Running these with "ctest -C Debug" or "ctest -C Release" works fine.
However I want to create a ctest script to build and test my project and
it lo
I have a similar problem, except that using ADD_DEPENDENCIES to make the
library with generated files a dependency of the targets that use it,
causes the target libraries to include a copy of the dependent library
when built as static libraries with VC71 (this is a long standing
(mis)feature of
Jan Woetzel wrote:
Mike Talbot wrote:
2.4.2 ... doesn't define the preprocessor symbol WIN32 ... for the VS
7.1 generator.
I cannot confirm this.
It works here as expected
- with cmake 2.4.2 on Windows
- using Visual studio .net 2003 generator.
Have a look at a hello world ex
Hello,
I'm in the process of upgrading from cmake 2.2.3 to 2.4.2 and found that
the new version doesn't define the preprocessor symbol WIN32 (which
2.2.3 used to) for the VS 7.1 generator. Is this a bug or feature? (I
can work around the problem by defining it explicitly with
ADD_DEFINITION
Brad King wrote:
Jan Woetzel wrote:
is there a way to compile/link only the "libs" (ADD_LIBRARY)
but skip linking the executables (ADD_EXECUTABLE)
using a global option/switch on cmake level?
I want to save compilation time when I need only the libraries for
linking my client project.
But we h
Hi,
I'm interested in using cmake for VS 2005 x64 builds; is this supported
yet? I noticed that there is an outstanding feature request for this
(Bug #2237) but that is 6 months old; if it would help I can provide
some sample .sln & .vcproj files.
Thanks,
Mike
--
Mike Talb
Xavier Delannoy wrote:
On Thu, 02 Feb 2006 15:02:00 +
Mike Talbot <[EMAIL PROTECTED]> wrote:
I believe that if you don't specify STATIC or SHARED in the ADD_LIBRARY
command, then you can control whether libraries are built as shared or
static via the BUILD_
ic_lib_dir
cmake -D BUILD_SHARED_LIBS:BOOL=FALSE ../srcdir
cd shared_lib_dir
cmake -D BUILD_SHARED_LIBS:BOOL=TRUE ../srcdir
--
Mike Talbot
Senior Software Developer
Schlumberger
Lambourn Court, Wyndyke Furlong,
Abingdon Business Park, Abingdon,
Oxfordshire, OX14 1UJ, UK
Tel: +44 (0)12
:/build/lib/$(OutDir)/MyUnitTest.dll but ctest does not expand
$(OutDir) to the build config (e.g. "Debug"). Am I missing something or
is this a bug?
[I am using cmake version 2.2-patch 3 on Windows XP]
Thanks,
Mike
--
Mike Talbot
Senior Software Developer
Schlumberger
Lambourn Cour
18 matches
Mail list logo