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 versio
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.
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
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
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
> w
e 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/16 13:42, Sven B
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
is there 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 conditions
Hi all,
Is there any chance that the version compatibility matrix will be
updated for cmake 3.x features?
Best regards,
Marcel Loose.
attachment: loose.vcf--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware
, 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.
attachment: loose.vcf--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http
24, 2015 at 12:05 PM, Marcel Loose lo...@astron.nl
mailto:lo...@astron.nl wrote:
Hi all,
Several times I've read the last paragraph of the documentation of
module CMakeParseArguments, but I can't get my head around it.
Keywords terminate lists of values, e.g. if directly
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 in there will (obviously)
always be (at least) one cycle behind with those in your source tree.
Cheers,
Marcel Loose.
attachment: loose.vcf--
Powered
${ASM_DIALECT}_COMPILER_INIT ${CMAKE_ASM_COMPILER})
include(CMakeDetermineASMCompiler)
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
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,
Marcel Loose
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.
attachment: loose.vcf--
Powered by www.kitware.com
that the
correct libraries on put on the link line in the correct order. There's
only one exception: circular dependencies. In that case you 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.
attachment
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 may be
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
target_link_libraries(eea
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 trouble?
I've further analyzed
, e.g. libc6:i386.
Hope this helps,
Marcel Loose.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQEcBAEBAgAGBQJT7+UrAAoJEEpMyb1AIWdYH8EH/2xcKu1vtXuoGvMDEzFZwkos
DRsR3BPjiU5MYyoGIaatIH7N4ioR6r0vniS4r+BP4qDqbt33Wuv/UHTMbGTN3iyf
4HCJI3xCEO6MCDpkhl59EciRyQb4GmFM9pi/NYDzTUaPvfQoLQ/ZldHaP0jkm72q
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.
What is the proper way to get
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.
What is the proper way to get
)
...
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: Using GnuPG
.
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 client is
# available. This version
${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 -Ipath.
Hope this helps.
Regards,
Marcel Loose.
On 17/06/14 13:46, majo huber wrote:
Hi @all,
I
On 04/04/14 12:45, Nils Gladitz wrote:
CMake execution time of one of my projects jumps from 0m6.121s
(2.8.12.2) to 1m5.084s (3.0.20140404-gce0aa).
Most time seems to be spend after -- Configuring done.
Any ideas?
Nils
Maybe this http://public.kitware.com/Bug/view.php?id=14758 has
[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.
attachment: loose.vcf--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http
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,
Marcel Loose.
On 28
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 attempts to find it againg will be a no-op.
--
Gruesse
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.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net
, that can build these packages in the right order without actually
installing them. We don't have any Autotools-based packages, but it
shouldn't be too hard (I guess) to wrap these as a separate package.
Best regards,
Marcel Loose.
attachment: loose.vcf--
Powered by www.kitware.com
Please
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 style
() 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,
Marcel Loose.
attachment: loose.vcf
it will execute or an empty string if there's no
match. With type, I've seen different outputs, like:
$ type ls
ls is aliased to `ls --color=auto'
$ type rm
rm is hashed (/bin/rm)
$ type ld
ld is /usr/bin/ld
This make it pretty hard to parse :(
Best regards,
Marcel Loose.
attachment: loose.vcf--
Powered
On 01/12/13 09:34, Nils Gladitz wrote:
On 30.11.2013 20:49, Marcel Loose (Astron) wrote:
According to the CMake documentation, the TARGET property LOCATION for a
non-imported target is provided for compatibility with CMake 2.4 and
below. My question is: are there any plans to deprecate
target is provided for compatibility with CMake 2.4 and
below. My question is: are there any plans to deprecate this property? I
want to know, because AFAIK, the only way to determine the full path to
a built target is to use this property.
Best regards,
Marcel Loose.
-BEGIN PGP SIGNATURE
to
a built target is to use this property.
Best regards,
Marcel Loose.
attachment: loose.vcf--
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
CMAKE_Fortran_COMPILER_WORKS is empty.
What's the correct way of handling this, without breaking backward
compatibility?
Best regards,
Marcel Loose.
attachment: loose.vcf--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
(... OPTIONAL)?
Best regards,
Marcel Loose.
attachment: loose.vcf--
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 this link
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 expecting
/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. Can you run CMake --debug
, and then it
finds it. However, IMHO, using this trick should only be necessary as a
last resort. Is this a bug?
Best regards,
Marcel Loose.
attachment: loose.vcf--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep
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
where Cluster Manager is installing
,
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 lo...@astron.nl wrote:
Hi,
It fails to find CUDA 5.0. See below.
$ env | grep CUDA
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 lo...@astron.nl
To: David Cole dlrd...@aol.com
Cc: cmake cmake@cmake.org
Sent: Tue, Apr 16, 2013 4:16 am
Subject: Re: [CMake] Regression
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 marcel.lo...@zonnet.nl wrote:
Hi all,
I noticed that, starting from cmake 2.8.8, INCLUDE_DIRECTORIES no longer remove
duplicates. I
-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/build
Best regards,
Marcel Loose.
--
Powered
,
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 this link to subscribe/unsubscribe:
http://www.cmake.org
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 can we
:
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), this triggers a policy warning
. 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,
Marcel Loose.
attachment
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 marcel.lo...@zonnet.nl
mailto:marcel.lo...@zonnet.nl wrote:
Thanks, that seems to work.
Is the idiom
if(POLICY CMP)
cmake_policy(PUSH
,
Marcel Loose.
Op 13-12-12 14:00, David Cole schreef:
You could use if(POLICY (if 2.6.2 supports that... I think it does,
but it was very long ago..) to avoid the call on older CMakes.
On Thu, Dec 13, 2012 at 6:31 AM, Marcel Loose lo...@astron.nl
mailto:lo...@astron.nl wrote:
Hi all
for the new CMake,
but get an error in return for the old CMake. What am I doing wrong??
Best regards,
Marcel Loose.
attachment: loose.vcf--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic
regards,
Marcel Loose.
attachment: loose.vcf--
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 this link to subscribe
and a non-cache
variable THREADS_LIBRARIES?
Best regards,
Marcel Loose.
attachment: loose.vcf--
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
(see issue
#8466). At that time David was very much against it, fearing to find a
***huueee*** can of worms right underneath the surface. Seems
I'm slowly getting more fellow thinkers ;)
Regards,
Marcel Loose.
attachment: loose.vcf--
Powered by www.kitware.com
Visit other Kitware open
Hi Stephen,
On Fri, 2012-02-17 at 12:06 +0100, Stephen Kelly wrote:
-- 8 8 8 8 8 8 8 8 8 --
diff --git a/templates/tests/CMakeLists.txt
b/templates/tests/CMakeLists.txt
index d2e37d2..ad471c7 100644
--- a/templates/tests/CMakeLists.txt
+++
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:
() 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://www.cmake.org/Wiki
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 overcomplete?
Best regards,
Marcel Loose
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 Fillion-Robin wrote:
Hi
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't be answering
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 \error message here
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
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 more
sources
are generated by a custom command
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 RD, Astron, the Netherlands
--
Marcel Loose
Senior Software Engineer, Computing Group RD, 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 more sources
are generated by a custom command.
The situation
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 situation is as follows. There are a couple of targets
(executables
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
when building just one
target in parallel, but I *do* have occasional broken builds when
building multiple targets in parallel. In that case, one of the targets
is a custom target. I therefore recommended my colleague to build one
target at a time when doing parallel builds.
Regards,
Marcel Loose
the test program. Correct?
Best regards,
Marcel Loose.
--
Marcel Loose
Senior Software Engineer, Computing Group RD, Astron, the Netherlands
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource
On Mon, 2011-05-23 at 07:21 -0400, David Cole wrote:
On Mon, May 23, 2011 at 4:13 AM, Marcel Loose lo...@astron.nl wrote:
Hi all,
A colleague of mine reported a bug in our CMake-base build
system when
doing a parallel build of multiple targets where
solved.
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
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 RD, Astron, the Netherlands
On 11-1-2011 at 21:51, in message
20110111213036.af4c126...@public.kitware.com, Rolf Eike Beer
e...@sf-mail.de 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
problems when cross-compiling. So, why is there no CheckCXXSourceLinks?
Best regards,
Marcel Loose.
--
Marcel Loose
Senior Software Engineer, Computing Group RD, Astron, the Netherlands
___
Powered by www.kitware.com
Visit other Kitware open-source
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 RD, Astron, the Netherlands
David Cole 11-01-11 13:44
Doesn't CheckCXXSourceCompiles link?
I
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, Computing Group RD, Astron, the Netherlands
.
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
Follow
/CTest:Using_CTEST_and_CDASH_without_CMAKE
useful.
Hope this helps,
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
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-topic
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 Loose.
___
Powered by www.kitware.com
Visit other
On 8-12-2010 at 11:41, in message
aanlktike_bxnege96vtpzinyv6scwvjwtg+un74vn...@mail.gmail.com, Klaim
mjkl...@gmail.com 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
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
as EXTERNAL_PROJECT(), etc.
Good luck.
Marcel Loose.
On 6-12-2010 at 21:46, in message
aanlktimmvbbx-bq1kceahsxd=pkz-aagkbsj5dscu...@mail.gmail.com, Klaim
mjkl...@gmail.com wrote:
It's a bit clearer to me now ;-)
Reading between the lines I get the feeling that you're probably
better
off using just
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:13, in message
aanlktimfweyejp
to import the required
subproject. UNLESS: your subprojects cannot really exist as stand-alone
products, but are just parts of one overall project. In that case, I
would choose to create just one CMake project.
HTH,
Marcel Loose.
___
Powered
On 30-11-2010 at 18:48, in message
20101130174852.gc10...@cryptio.net, Tyler
Roscoe ty...@cryptio.net 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
Roscoe ty...@cryptio.net wrote:
On Wed
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.
___
Powered by www.kitware.com
Visit other Kitware open
/en/Underlinking
http://www.gentoo.org/proj/en/qa/asneeded.xml
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
.
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.
___
Powered by www.kitware.com
Visit other Kitware open-source
. To be honest, the people at Kitware don't
make that an easy job, because almost every patch-release contains new
features :-(
Best regards,
Marcel Loose.
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com
On 24-11-2010 at 17:45, in message
20101124164507.gg23...@cryptio.net, Tyler
Roscoe ty...@cryptio.net 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
to CMAKE_INSTALL_PREFIX_INITIALIZED_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
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 other.
HTH,
Marcel Loose.
___
Powered by www.kitware.com
Visit other
to NEW for CMake 2.8.4 and
later, but I think that's what David suggested as well.
Just my 2cts.
Regards,
Marcel Loose.
___
cmake-developers mailing list
cmake-developers@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
be read-only!). Or maybe I completely
misunderstood your question.
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
is that there's something else going
wrong here.
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
1 - 100 of 412 matches
Mail list logo
