Hi Mahmood,
I think that "-DBoost_LIBRARY_DIRS" should be "-DBoost_LIBRARY_DIR".
Cheers,
Marcel Loose.
On 25/10/2019 09:54, Mahmood Naderan via CMake wrote:
> Even with the latest 3.15.4, I get the same error
>
>
> $ cmake --version
> cmake version 3.
Hi Steven,
When you run patch manually, do you then supply the same absolute paths?
Looking at the patch file I noticed that it contains a relative path. So
maybe you should cd to
${CMAKE_BINARY_DIR}/boost/src/external_boost/project-config.jam before
running the patch command.
Cheers,
Marcel.
Op
Hi Suzuki,
Sorry for chiming in late, but you may want to try the PPA for Ubuntu
Toolchain test builds, which contains compiler builds up to gcc-8 for
Ubuntu version as old as 10.04. Much less of a hassle than building GCC
yourself, I can tell from experience. Check out
https://launchpad.net/~ubun
Hi Michele,
This could become a painful exercise. You basically have two options:
1) Treat it as a cross-compilation project, or
2) Create a virtual machine running CentOS 5.8 and do the build there.
If I were you, I would go for the second option.
Cheers,
Marcel.
Op 07-03-17 om 17:56 schreef Mi
Hi Walter,
The dash before levent looks different from the ones before lrt and
lpthread. Are you sure it's not some kind of Unicode character?
Cheers,
Marcel Loose.
On 15/09/16 18:56, Gunter, Walter E wrote:
>
> I am cross-compiling for an arm, and can run cmake successfully, but
&
l have been set
such that the correct binaries and libraries can be found, right? CMake
also searches for libraries in the paths specified in the environment
variables PATH and LIB (unfortunately not LD_LIBRARY_PATH). Isn't that
the way to tackle this problem?
Cheers,
Marcel Loose.
On 30/06/1
See also https://cmake.org/Bug/view.php?id=10200
Cheers,
Marcel Loose.
On 27/06/16 09:23, Andreas Naumann wrote:
> Thanks for the 6 year old hint. But obviously, the patch is not in any
> recent cmake version.
> Therefore, I could use it in my own project and ship my own
> FindSubv
rking copy.
Cheers,
Marcel Loose.
Op 24-06-16 om 19:48 schreef Andreas Naumann:
> Dear cmake users,
>
> I have a question if, and how, you use the Subversion module of cmake.
> The module provides the macro Subversion_WC_INFO, which extracts
> information of a working copy. I use this i
e for less than historic reasons. Maybe someone from Kitware can
shed a light on this.
Regards,
Marcel Loose.
On 09/12/15 07:33, Alan W. Irwin wrote:
> For the lapack CMake-based build and test system, some of the ctests
> can exceed 1500 seconds (the default limit) for special condition
Hi all,
Is there any chance that the version compatibility matrix will be
updated for cmake 3.x features?
Best regards,
Marcel Loose.
<>--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers v
n
> MY_INSTALL_DESTINATION set to"
>
> Petr
>
> On Tue, Feb 24, 2015 at 12:05 PM, Marcel Loose <mailto:lo...@astron.nl>> wrote:
>
> Hi all,
>
> Several times I've read the last paragraph of the documentation of
> module CMakeParseArguments
be set to "OPTIONAL", but would
be empty [...] ???
Reading the first sentence of this paragraph, I concluded that
MY_INSTALL_DESTINATION will be empty, not would be.
Best regards,
Marcel Loose.
<>--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
is message in context:
> http://cmake.3232098.n2.nabble.com/Include-path-perference-tp7589463.html
> Sent from the CMake mailing list archive at Nabble.com.
Hi Brandon,
I'm confused as to why you would want to look for dependencies in
CMAKE_INSTALL_PREFIX at all. The header files
akeDetermineASMCompiler)
set(ASM_DIALECT)
CMakeTestASM-BGPCompiler.cmake:
set(ASM_DIALECT "-BGP")
include(CMakeTestASMCompiler)
set(ASM_DIALECT)
Hope this helps.
Regards,
Marcel Loose.
On 15/10/14 04:23, George Zagaris wrote:
> Dear all,
>
> I am working on a project where on certain
Hi Yu,
I think you need to add an explicit dependency of main.cc on the
"generated" (well, not really generated, but installed) header file
crfpp.h. CMake has no clue as to what files are being compiled/installed
by your external project, so you have to make this explicit.
HTH,
Ma
e and
interrupt them with Ctrl-C, cleanup is done properly. However, if I run
them from CTest and interrupt them, cleanup is not done.
Is there a way to let CTest pass these signals? Or is there another
solution for this?
Best regards,
Marcel Loose.
<>--
Powered by www.kitware.com
Please keep
ou may need to
help CMake a bit. IMHO you should try very hard to avoid circular
library dependencies; they are a real PITA.
> Thanks,
> Olaf
>
Cheers,
Marcel Loose.
<>--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.or
nk the order of add_subdirectory(), add_library(), and
target_link_libraries() is important. You might want to check those as well.
Cheers,
Marcel Loose.
On 21/08/14 13:29, Olaf Peter wrote:
> no idea here? It's seems to be a C++ problem, but how to solve it.
> Changing the order of
>
On 20/08/14 22:50, Alexander Neundorf wrote:
> On Tuesday, August 12, 2014 09:06:13 Brad King wrote:
> ...
>> FYI, the only intended use case for setting a policy to OLD is to
>> quiet warnings in a maintenance branch of an existing release.
>> Some day support for OLD behavior of some policies ma
install all 32-bit libraries at once
(package ia32-libs), or one at a time, by just specifying the
architecture of the package, e.g. libc6:i386.
Hope this helps,
Marcel Loose.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQEcBAEBAgAGBQJT7+UrAAoJEEpMyb1AIWdYH8EH/2xcKu1vtXuoGvMDEzFZwkos
DRsR3
Op 12-08-14 om 15:06 schreef Brad King:
> On 08/12/2014 03:48 AM, Marcel Loose wrote:
>> On a side note. Even using the new PRIVATE and PUBLIC keywords I am
>> unable to exactly specify which libraries are needed for linking.
>
> Can you provide a concrete example of this
On 11/08/14 18:47, Brad King wrote:
> On 08/09/2014 09:46 AM, Marcel Loose wrote:
>> CMake 2.8.12 introduced the keywords PRIVATE, INTERFACE and PUBLIC, and
>> immediately deprecated the LINK_INTERFACE_LIBRARIES keyword,
>> triggering policy warnings CMP0022 and CMP0023.
>
On 11/08/14 18:47, Brad King wrote:
> On 08/09/2014 09:46 AM, Marcel Loose wrote:
>> CMake 2.8.12 introduced the keywords PRIVATE, INTERFACE and PUBLIC, and
>> immediately deprecated the LINK_INTERFACE_LIBRARIES keyword,
>> triggering policy warnings CMP0022 and CMP0023.
>
ION_LESS 2.8.12)
...
else()
...
endif()
Of course I could put this logic in a macro, but how then do I handle
the new keywords. Some hints or tips would be very much appreciated.
Kind regards,
Marcel Loose.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: U
.
Cheers,
Marcel Loose.
On 02/07/14 09:04, Eric Noulard wrote:
> May be you can avoid localized output by setting LANG env var to "C".
>
>
> Or you can ask svn for xml output which may not be localized e.g.
>
> # Get the SVN revision number of an svn command line cl
${CMAKE_BINARY_DIR}/include to
the include path using include_directories().
Now proj2 should be able to locate lib1/lib1.h through the symbolic
link, because ${CMAKE_BINARY_DIR}/include is in the -I.
Hope this helps.
Regards,
Marcel Loose.
On 17/06/14 13:46, majo huber wrote:
> Hi @all,
>
&g
-U option to remove WITH_DATE from the cache: cmake
-UWITH_DATE [whatever options you want to pass to cmake].
Other than that, if you want to rebuild the cache, why not simply delete
it before you run cmake?
Regards,
Marcel Loose.
<>--
Powered by www.kitware.com
Please keep messages o
That's a nice long list ;)
I noticed when building this RC on Ubuntu 13.10, that 'make test' fails:
$ make test
Running tests...
make: Bootstrap.cmk/ctest: Command not found
make: *** [test] Error 127
Copying ./bin/ctest to ./Bootstrap.cmk solves this issue.
Best regards,
Marce
ent* entities.
Best regards,
Marcel Loose.
op 14-02-14 09:02, Jakub Zakrzewski schreef:
> Hi,
>
> what about searching multiple times, each time giving only the path
> you want (in order of prefference)? If I'm correct, once the
> library is found, next at
.
>
Hi David,
For what it's worth. This problem is related to another issue I
reported: http://public.kitware.com/Bug/view.php?id=14094. Here I also
got a quite long, but still manageable list of include directories.
Regards,
Marcel Loose.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4
Hi all,
Should I file this as a bug in the issue tracker then?
Best regards,
Marcel Loose.
op 03-02-14 17:57, David Cole schreef:
> I think it's mostly just a speed/space trade-off. If you don't want to
> consume the RAM temporarily (and in this case, I think it's a gi
hat you mean by "installed". We're in a similar
situation. We have a lot of so-called packages in our project, that can
depend on other (internal) packages. I've setup a build system, using
CMake, that can build these packages in the right order without actually
installing
On 31/01/14 14:11, Paul Smith wrote:
> On Fri, 2014-01-31 at 02:26 -0800, Alan W. Irwin wrote:
>> And to answer the OP's question, I can highly recommend uncrustify for
>> code styling
> I agree with Alan. We did a huge reformatting effort last year to
> change a very large C++ codebase from a sty
_directories() in the offending macro with:
-include_directories(${_dirs})
+list(APPEND _inc_dirs ${_dep_inc_dirs})
+list(REMOVE_DUPLICATES _inc_dirs)
+set_directory_properties(PROPERTIES INCLUDE_DIRECTORIES "${_inc_dirs}")
Any suggestions or comments?
Best regards,
M
built target is to use this property.
Best regards,
Marcel Loose.
<>--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each of
of
enable_language(... OPTIONAL)?
Best regards,
Marcel Loose.
<>--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Fol
lls, however, the error is triggered, because
CMAKE_Fortran_COMPILER_WORKS is empty.
What's the correct way of handling this, without breaking backward
compatibility?
Best regards,
Marcel Loose.
<>--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/
Hi Robert,
I created an issue for this in Mantis:
http://public.kitware.com/Bug/view.php?id=14122
Best regards,
Marcel Loose.
On 01/05/13 15:09, Robert Maynard wrote:
It looks like you used the ubuntu cuda package which installs the cuda
library to a directory that FindCUDA wasn't expe
erating /home/marcel/temp/cmake/cuda/build
-- Generating done
-- Build files have been written to: /home/marcel/temp/cmake/cuda/build
Best regards,
Marcel Loose.
Op 29-04-13 18:04, Robert Maynard schreef:
I have had no problem with Ubuntu 12.10 and Cuda 5; findCuda is able
to find cuda in /usr/lib.
,
Marcel Loose.
On 29/04/13 16:54, Robert Maynard wrote:
You have a nonstandard install path that will require you to use
CUDA_PATH / CUDA_BIN_PATH and CUDA_LIB_PATH.
On Mon, Apr 29, 2013 at 10:10 AM, Marcel Loose wrote:
Hi,
It fails to find CUDA 5.0. See below.
$ env | grep CUDA
CUDA_PATH=/cm
Only when explicitly setting CUDA_LIB_PATH, libcuda.so is found.
BTW: On Ubuntu I also need to set CUDA_LIB_PATH, but then to
/usr/lib/nvidia-current.
Regards,
Marcel Loose.
On 29/04/13 15:36, Robert Maynard wrote:
Can you provide what Cuda version FindCuda is failing to find, and
wher
finds it. However, IMHO, using this trick should only be necessary as a
last resort. Is this a bug?
Best regards,
Marcel Loose.
<>--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-top
build issue you're having, or is this just an
aesthetic "I don't like seeing -I duplicate arguments" thing...?
D
-Original Message-
From: Marcel Loose
To: David Cole
Cc: cmake
Sent: Tue, Apr 16, 2013 4:16 am
Subject: Re: [CMake] Regression in INCLUDE_DIRECTORI
duplicates during generation, though. You shouldn't see duplicates
in the generated make files or project files...
On Apr 15, 2013, at 5:34 PM, Marcel Loose wrote:
Hi all,
I noticed that, starting from cmake 2.8.8, INCLUDE_DIRECTORIES no longer remove
duplicates. I this a regression?
s/build
$ ~/x86_64/usr/local/cmake-2.8.8/bin/cmake ..
-- INCLUDE_DIRECTORIES=
-- INCLUDE_DIRECTORIES=/usr/include
-- INCLUDE_DIRECTORIES=/usr/include;/usr/include
-- Configuring done
-- Generating done
-- Build files have been written to:
/home/marcel/temp/cmake/include_directories/buil
s of CMake. Finally, the changes I
made for Boost are probably the most controversial and likely not
generic enough. For one thing I define all uppercase variables for all
the relevant Boost-variables that are set.
Should I file an issue in Mantis for BLAS and LAPACK?
Best regards,
Ma
On Wednesday 19 December 2012, Marcel Loose wrote:
> Hi David,
>
> I need to set a policy to OLD, because I have wrapped a few existing
> Find*.cmake files to overcome some bugs or shortcomings.
However, since
> CMake 2.8.4 (or 2.8.3, I'm not sure), thi
e now
included from my CMAKE_MODULE_PATH and some from CMAKE_CURRENT_LIST_DIR,
which expands to somewhere inside CMAKE_ROOT.
Best regards,
Marcel Loose.
Op 17-12-12 15:30, David Cole schreef:
If you need to set a policy to OLD, then we have failed...
Why do you need to set a policy to OLD?
How c
tion to see if there is such a way to re-write the code to
work with older AND newer CMakes before I would ever consider setting
a policy to OLD in my own CMakeLists files.
HTH,
David
I can send specific examples if you want. I'm not sure I can send
attachments to the mailing list, tho
Hi David,
See my remarks inline.
On 15/12/12 16:47, David Cole wrote:
On Sat, Dec 15, 2012 at 10:33 AM, Marcel Loose <mailto:marcel.lo...@zonnet.nl>> wrote:
Thanks, that seems to work.
Is the idiom
if(POLICY CMP)
cmake_policy(PUSH)
cmake_polic
Thanks, that seems to work.
Is the idiom
if(POLICY CMP)
cmake_policy(PUSH)
cmake_policy(SET CMP OLD)
cmake_policy(POP)
endif()
one that you also need to use with newer CMakes? Or does it then suffice
to do
cmake_policy(SET CMP OLD)
Best regards,
Marcel Loose
Make.
This sounds like a catch-22. I've fixed the warning for the new CMake,
but get an error in return for the old CMake. What am I doing wrong??
Best regards,
Marcel Loose.
<>--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource
ng a cache variable THREADS_LIBRARY and a non-cache
variable THREADS_LIBRARIES?
Best regards,
Marcel Loose.
<>--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ
oject developers. Use -Wno-dev to suppress it.
-- "y" evaluate to FALSE
I.e., it doesn't produce a warning when using "x" in an if() statement,
but it does when using "y".
Best regards,
Marcel Loose.
<>--
Powered by www.kitware.com
Visit other Kitwa
u should fix your add_library() line.
Best regards,
Marcel Loose.
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://w
On Wed, 2011-07-27 at 12:14 +0100, Sanatan Rai wrote:
> Hi,
>This is a newbie question. So apologies in advance if this is
covered
> somewhere in the docs (I haven't been able to find a satisfactory
explanation).
>
> The issue is this:
>
> * I have a library called (lib)atmath as per:
>
> in
regexes in cmCTestErrorMatches.
":[ \\t]cannot find" # matches first line
"([^ :]+):([0-9]+): ([^ \\t])" # matches second and third line
I know I can create exception regexes, but I'm wondering whether the
current set of regexes may be overco
Ah, sorry.
I didn't check the (almost) latest cmake. I'm currently stuck with
Ubuntu LTS 10.04, which ships cmake 2.8.0. I'll backport then.
Regards,
Marcel Loose.
On Wed, 2011-07-20 at 22:14 +0200, Alexander Neundorf wrote:
> On Wednesday 20 July 2011, Jean-Christophe F
at
http://www.cmake.org/Wiki/CMakeMacroParseArguments which sounds like a
very useful macro to have.
I was wondering why this macro is only implemented in CPack.cmake as
cpack_parse_arguments(). Is there a reason for not having it as standard
CMake module?
Best regards,
Marcel Loose.
--
Marcel
Thanks David,
I never realized you can use just about any CMake-construct inside
CODE...
Regards,
Marcel Loose.
On Wed, 2011-07-20 at 10:41 -0400, David Cole wrote:
> To produce an error from an install(CODE snippet, simply add:
>
>
> if(error)
> message(FATAL_ERROR
Hi Jc,
Thanks for the tip. It makes sense to let the build fail early (i.e.
during compilation, instead of installation). I'll take it into
consideration.
Regards,
Marcel Loose.
On Wed, 2011-07-20 at 06:41 -0400, Jean-Christophe Fillion-Robin wrote:
> Hi Marcel,
>
> Aware I won&
mands executed
inside INSTALL(CODE ...), so that I can let 'make install' exit with a
non-zero exit status?
Best regards,
Marcel Loose.
--
Marcel Loose
Senior Software Engineer, Computing Group R&D, Astron, the Netherlands
___
Powered by www
On Wed, 2011-06-29 at 23:43 +0200, Marcel Loose wrote:
> On Wed, 2011-06-29 at 20:46 +0200, Michael Wild wrote:
> > On 06/29/2011 05:22 PM, Marcel Loose wrote:
> > > Hi all,
> > >
> > > I'm having a problem with a parallel 'make' where one or mor
On Wed, 2011-06-29 at 21:55 +0200, Marcel Loose wrote:
Seems my webmail client completely screwed up the subject threading.
Sorry for the noise.
Best regards,
Marcel Loose.
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
On Wed, 2011-06-29 at 20:46 +0200, Michael Wild wrote:
> On 06/29/2011 05:22 PM, Marcel Loose wrote:
> > Hi all,
> >
> > I'm having a problem with a parallel 'make' where one or more
sources
> > are generated by a custom command.
> >
> > The
--
Marcel Loose
Senior Software Engineer, Computing Group R&D, Astron, the Netherlands
>>> Michael Wild 29-06-11 20:47 >>>
On 06/29/2011 05:22 PM, Marcel Loose wrote:
> Hi all,
>
> I'm having a problem with a parallel 'make' where one or mo
hen doing a
parallel build, these build.cmake files are also processed in parallel.
Am I correct in this assumption? And if so, what's the proper solution
for this problem?
Best regards,
Marcel Loose.
--
Marcel Loose
Senior Software Engineer, Computing Group R&a
idually in the
> correct order by hand? That would be strange, IMO. Maybe, someone
> can shed light upon this issue.
>
Hi Michael,
Nice example. Do you know, by any chance, if this only happens with
custom targets/commands. I get the feeling that race condition only seem
to happen with these
On Mon, 2011-05-23 at 07:21 -0400, David Cole wrote:
> On Mon, May 23, 2011 at 4:13 AM, Marcel Loose wrote:
> Hi all,
>
> A colleague of mine reported a bug in our CMake-base build
> system when
> doing a parallel build of multiple target
d the target to build the test program. Correct?
Best regards,
Marcel Loose.
--
Marcel Loose
Senior Software Engineer, Computing Group R&D, Astron, the Netherlands
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
t search the "normal" path and only then uses the
"config" path suffix. The former, however, immediately starts of using
the "config" path suffix.
Problem solved.
Regards,
Marcel Loose.
___
Powered by www.kitware.com
Vi
suffixes are searched, not the
directories in the search path *without* the suffixes.
Is this a bug in the documentation or a bug in the implementation of
CMake?
Best regards,
Marcel Loose.
--
Marcel Loose
Senior Software Engineer, Computing Group R&D, Astron, the Netherl
>>> On 11-1-2011 at 21:51, in message
<20110111213036.af4c126...@public.kitware.com>, Rolf Eike Beer
wrote:
> Am Dienstag, 11. Januar 2011, 11:20:06 schrieb David Cole:
>> Yes... this confused me when I first encountered it as well.
>>
>> TRY_COMPILE is misnamed in CMake.
>>
>> In functionality
so my
background in the GNU Autotools, which has TRY_COMPILE, TRY_LINK and
TRY_RUN, didn't really help. Sorry for the noise.
Best regards,
Marcel Loose.
--
Marcel Loose
Senior Software Engineer, Computing Group R&D, Astron, the Netherlands
>>> David Cole 11-01-11 13:44 >>>
problems when cross-compiling. So, why is there no CheckCXXSourceLinks?
Best regards,
Marcel Loose.
--
Marcel Loose
Senior Software Engineer, Computing Group R&D, Astron, the Netherlands
___
Powered by www.kitware.com
Visit other Kitware open-so
> module?
>
> -Todd
Hi Todd,
I think this is a good idea. You might consider taking into account
which languages are currently enabled, either explicitly with
enable_language() or implicitly with project().
Best regards,
Marcel Loose.
--
Marcel Loose
Senior Software Engineer, Co
BRARY.
Best regards,
Marcel Loose.
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
F
s use strace, but this is IMHO really not
the way it should be.
Best regards,
Marcel Loose.
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topi
d in fact like to run ctest
without cmake. You can do that, be you'll need some plumbing (i.e. a
small ctest-script) to get ctest going. I think you'll find
http://www.cmake.org/Wiki/CTest:Using_CTEST_and_CDASH_without_CMAKE
useful.
Hope this helps,
Marcel Loose.
___
Sorry,
I really wouldn't know, I do development on Linux. My knowledge of MS
Visual Studio is negligible.
On a general note, though, CMake uses a so-called generator to generate
the Visual Studio project files, as it can also generate Unix Makefiles,
or KDevelop project files.
Maybe you should s
>>> On 8-12-2010 at 11:41, in message
, Klaim
wrote:
> Thanks! I'll try this solution.
>
> By the way is there a way to list all projects found recursively in
a
> folder?
Not that I know of.
You can of course do a grep, but that's probably not what you mean.
Regards,
Marcel.
_
is to generate
ConfigXXX.cmake files for your XXX library. These ConfigXXX.cmake files
should set the same variables as a FindXXX.cmake file would. Only
difference is that you can generate the ConfigXXX.cmake file using the
information about XXX availabe to CMake.
Hope this helps,
Marcel
project as EXTERNAL_PROJECT(), etc.
Good luck.
Marcel Loose.
>>> On 6-12-2010 at 21:46, in message
, Klaim
wrote:
>>
>>
>> It's a bit clearer to me now ;-)
>> Reading between the lines I get the feeling that you're probably
better
>> off using j
he feeling that that's not the case in your situation.
You might consider to use multiple PROJECT() commands inside your
source tree. It will make your life slightly easier when you later
decide you do want to split things up.
Hope this helps.
Marcel Loose.
>>> On 3-12-2010 at 13:
27;ll use this organisation
for
> another big project too.
>
> Any help would be really.helpful :)
> Thanks for reading. Tell me if I was not clear on some points.
>
> Klaim
Hi Klaim,
It's not completely clear to me how tightly your subprojects are
coupled.
I would
is what we do, and it definitely works for us. Set it _before_
the
> PROJECT() statement.
+1 for me. I have a LofarInit.cmake file that is included before
PROJECT(LOFAR). I wouldn't want this "feature" to break.
Regards,
Marcel Loose.
>>> On 30-11-2010 at 18:48, in message
<20101130174852.gc10...@cryptio.net>, Tyler
Roscoe wrote:
> On Thu, Nov 25, 2010 at 02:01:31PM +0100, Marcel Loose wrote:
>> >>> On 24-11-2010 at 17:45, in message
>> <20101124164507.gg23...@cryptio.net>, Tyler
lowing links of interest. They discuss the virtues
and risks of using --as-needed in the light of underlinking and
overlinking; and how to fix broken packages in distributions.
http://wiki.mandriva.com/en/Overlinking
http://wiki.mandriva.com/en/Underlinking
http://www.gentoo.org/proj/en/qa/asneeded
andy and definitely worth the effort.
However, how's keeping
http://www.cmake.org/Wiki/CMake_Released_Versions up-to-date?
Since, you're matrix is "just" a user-friendly representation of that
information.
Regards,
Marcel Loose.
>>> On 24-11-2010 at 17:45, in message
<20101124164507.gg23...@cryptio.net>, Tyler
Roscoe wrote:
> On Wed, Nov 24, 2010 at 12:11:56PM +0100, Micha Renner wrote:
>>
>> > SET(CMAKE_INSTALL_PREFIX "/foo/bar" CACHE PATH "Foo install
prefix")
>> >
>> > So, without the test to
CMAKE_INSTALL_PREFIX_
t the top of your CMakeLists.txt file:
CMAKE_MINIMUM_REQUIRED(VERSION 2.8.2)
But you do have a point. It would really help people developing CMake
files to know whether they can use a given command or not if they want
to support, say, CMake 2.6.0. To be honest, the people at Kitware don't
m
TIALIZED_TO_DEFAULT,
and without the FORCE option.
Reason: if someone unsets CMAKE_INSTALL_PREFIX on the command-line with
-U, CMAKE_INSTALL_PREFIX will default to /foo/bar (which is the
project's default), instead of /usr/local (which is CMake's default).
Just my 2cts.
Marcel Loose.
rectories is a per-directory setting. So, if
you're free to reorganize your source files, you could put the two
groups of files in two different directories. Then you can use
include_directories() in each directory. Make sure you don't make one of
these directories a subdirectory of the
header files in the build
directory, which is IMHO the only sensible place to put generated files
(your source tree might even be read-only!). Or maybe I completely
misunderstood your question.
Best regards,
Marcel Loose.
___
Powered by www.kitware.com
Vis
gt;
>
> __
> Alan W. Irwin
>
> Astronomical research affiliation with Department of Physics and
Astronomy,
> University of Victoria (astrowww.phys.uvic.ca).
>
> Programming affiliations with the FreeEOS eq
Hi David,
I've got one more, one that I just entered in Mantis.
#11410 - Result of IF() is inconsistent
Regards,
Marcel Loose.
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opens
regards,
Marcel Loose.
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow
.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www
Hi Alex,
On Sun, 2010-10-31 at 10:20 +0100, Alexander Neundorf wrote:
> On Thursday 28 October 2010, Marcel Loose wrote:
> > Hi all,
> >
> > What is the best way to work around a broken Find module?
> >
> > A technique I've used up till now is to wrap the
ideas?
Best regards,
Marcel Loose.
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMak
1 - 100 of 426 matches
Mail list logo
