also buy the 'Mastering CMake' book. Its
a bit outdated, but the basic information on how to set up a project
still holds.
With kind regards,
Micha Hergarden
signature.asc
Description: OpenPGP digital signature
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ
On 10/10/2013 09:19 PM, Giordano Khouri wrote:
I'm surprised to see that there's no configuration specific
COMPILE_FLAGS. Please correct me if I'm wrong.
*Khouri Giordano*
Software Technology Researcher
Nikon Inc.
1300 Walt Whitman Road
Melville NY 11747-3064
Office:
Hello Olaf,
The problem is that find_package is done at configuration time of the
project, and building the external project is done during buildtime
(after configuration time that is). This is the reason why most projects
that want to use third party / external software create a so called
On 11/13/2013 11:50 PM, Paul Smith wrote:
I need to maintain my own copy of the latest cmake, and for multiple
different target systems (GNU/Linux, MacOS, Windows, Solaris...)
I have a shared location where all tools like this go, so that
regardless of the system architecture you can access
On 11/20/2013 06:08 PM, NoRulez wrote:
When I run ctest -V -S CTestScript.cmake then everything is done
successfully, except that I doesn't see the build under CDash.
Am 20.11.2013 um 17:30 schrieb Nils Gladitz nilsglad...@gmail.com:
On 20.11.2013 17:23, NoRulez wrote:
Now the problem
20.11.2013 um 18:30 schrieb Micha Hergarden micha.hergar...@gmail.com:
On 11/20/2013 06:08 PM, NoRulez wrote:
When I run ctest -V -S CTestScript.cmake then everything is done
successfully, except that I doesn't see the build under CDash.
Am 20.11.2013 um 17:30 schrieb Nils Gladitz nilsglad
On 02/20/2014 11:54 PM, Jack Smith wrote:
I think I've have an epiphany.
I've been really struggling to understand how to get my build to work,
and it seems the problem is with the configure step of cmake.
I would like to see some mechanism whereby I can delay the completion
of the
Can you verify that *${MPI_C_INCLUDE_PATH} is actually set?
I normally use 'printf' debugging to find out: message(WARNING HELLO:
**${MPI_C_INCLUDE_PATH}*)
Regards,
Micha
On 03/18/2014 07:34 AM, Bibrak Qamar wrote:
Thanks for the help.
I did that but still the error persists.
The C compiler
Hi Brian,
ExternalProject_Add has a DEPENDS option. What you can do is let X
depend on Y and use the CMAKE_CACHE_ARGS option to provide the include
path, or use the buildsystem in project X to find the headers itself.
Regards,
Micha
On 03/19/2014 03:11 AM, Brian Lewis wrote:
If X brings in Y
On 03/20/2014 04:48 AM, Brian Lewis wrote:
On 2014.03.19, at 07:21, Micha Hergarden wrote:
Hi, thanks for answering. Could you please elaborate a little?
ExternalProject_Add has a DEPENDS option. What you can do is let X
depend on Y
DEPENDS seems to mean that the external project depends
Hello all,
I do use the ExternalProject to prebuild some binaries, without the
'superproject' setup, and it does seem to work. Using the
add_dependencies, I can make sure some third party libs are prebuild
before I start to build my project. I have seen some issues with
ExternalProject (failing
http://main.cc
after CRFPP_EX_PROJ finished.
Of course , I’m not sure is this my misuse this project .
On Sep 16, 2014, at 14:55, Micha Hergarden micha.hergar...@gmail.com
mailto:micha.hergar...@gmail.com wrote:
Hello all,
I do use the ExternalProject to prebuild some binaries, without
of migrating my project to a
superbuild as well. Take a look at the openchemistry project if you
would like to see an example of that:
https://github.com/OpenChemistry/openchemistry
Regards,
Micha Hergarden
On 09/16/2014 11:04 AM, Marcel Loose wrote:
Hi Yu,
I think you need to add an explicit
at the openchemistry setup?
Regards,
Micha
On 09/16/2014 01:42 PM, Yu Jing wrote:
Hello Micha,
It seems still not work….
On Sep 16, 2014, at 17:36, Micha Hergarden micha.hergar...@gmail.com
mailto:micha.hergar...@gmail.com wrote:
Hello Yu,
It seems I too needed another trick to make it work:
set_property
the
external projects a target in my project depends on' or do you mean
'show me the dependencies the external project depens on', or something
different altogether?
With kind regards,
Micha Hergarden
signature.asc
Description: OpenPGP digital signature
--
Powered by www.kitware.com
Please keep
(if this is possible at all) would mean
adapt the ninja generator; not showing the intermediates would mean
adapt ninja? I'm not familiar enough with either to help you I'm afraid.
Maybe one of the ninja generator maintainers can help you?
With kind regards,
Micha Hergarden
On 09/23/2014 09:09 PM
On 11/09/2014 08:34 PM, SF Markus Elfring wrote:
Hello,
I configured a specific software to use the CPack modules to generate
corresponding DEB and RPM packages together with CMake 3 a while ago.
I notice now that package specifications and control files contain
outdated version data after
On 11/10/2014 07:40 PM, SF Markus Elfring wrote:
You could, as a workaround for the problem, define a add_custom_target
that removes the corresponding rpm/deb packages and just calls 'cmake
--build --target package' to regenerate them.
Thanks for your suggestion.
It's not an ideal solution,
On 11/10/2014 07:50 PM, SF Markus Elfring wrote:
I actually don't know if this is an omission or a deliberate design choice.
How often do use DEB and RPM package generation with CPack for your software?
Regards,
Markus
I used it quite often (only rpm), but having said that: I had a need for
WORKING_DIR
to the example_dir and then perform the steps needed to build. If you want
that to be a separate cmake based solution, you may want to take a look at
the external_project module.
With kind regards,
Micha Hergarden
2014-12-05 11:46 GMT+01:00 Petr Kmoch petr.km...@gmail.com:
Hi all.
I'm
If the projects are truly independent, you may also want to look at the
external_project command.
Regards,
Micha
On 12/10/2014 03:42 PM, Petr Bena wrote:
I have 3 projects, all using cmake. When I run cmake on each of them
and separately build them, it's all fine.
When I use include() on
On 07/20/2015 12:52 AM, Eric Wing wrote:
I would like to dynamically construct a macro or function name to
invoke. I basically have a core CMake system I want users to be able
to extend/plug stuff into without knowing about a lot of the core
CMake implementation. Callback functions would be an
On 07/18/2015 08:17 AM, Alexandre GOUAILLARD wrote:
dear all,
I'm trying to use cmake as a super build script for another library
build system.
Using add_custom_command and add_custom_target I have managed to
handle most of the steps so far. My libraries and executable are being
built as
On 07/24/2015 07:12 PM, michelle lopez wrote:
Hello. This is my first time using cmake. How do I get a program
that is built to run in cmake?
Hello Michelle,
Could you elaborate on that? If you want one of the targets being built
to run as part of the whole project build, you can use the
Hello,
You don't seem to tell cmake what executable you want and what sources
it is made up of. Take a look at the 'add_executable' and 'add_library'
commands. To create an executable from the sources, you may want to do
something like: add_executable(test01 test01.cc)
And for the library:
wastefull to copy files when you already have them in your
source, but keeping build files and source files separate makes it
really easy to clean up or to have multiple build directories. In my
opinion this feature is one of the virtues of cmake.
Regards,
Micha
On 07/13/2015 07:02 PM, Micha Hergarden
Forwarded Message
Subject:Re: Re: [CMake] opening files relative to cmake build directory
Date: Mon, 13 Jul 2015 17:00:52 +
From: Owen Alanzo Hogarth gurenc...@gmail.com
To: Micha Hergarden micha.hergar...@gmail.com
Resources.txt is a test but it's
On 07/12/2015 02:14 PM, Owen Alanzo Hogarth wrote:
I have a little project that's setup like this
project
main.c
build
resources
source
.../module1
.../module2
.../etc
main.c loads dynamic libs from under the source folder.
I am trying to open up a file using c fopen
I create a
On 07/20/2015 05:16 PM, MM wrote:
I want to refer to
== toplevl cmakelists file ===
PROJECT(prj)
ADD_SUBDIRECTORY(dir1)
==dir1 cmakelists.txt===
ADD_CUSTOM_COMMAND( TARGET prj # this doesn't work
)
In what way do you want to refer to it? You may want to use the DEPENDS
parameter here.
On 08/06/16 17:58, Kristian wrote:
> Hey guys,
>
> I am creating a RPM package with CMake. Here is a small example of how
> it looks:
>
>
>
> cmake_minimum_required(VERSION 3.5)
>
> set(BOOST_LIB "${CMAKE_CURRENT_SOURCE_DIR}/boost")
>
> file(GLOB_RECURSE BOOST_LIBRARIES ${BOOST_LIB}/*)
>
On 08/02/16 19:35, Alain Miniussi wrote:
> On 08/02/2016 18:43, Alain Miniussi wrote:
>>
>> Hi,
>>
>> I am trying to fix FindHDF5.cmake (support for HDF5_ROOT is broken,
>> only environment variable is supported and it will be eventually
>> probably ignored in find_program).
>>
>> To that end, I'd
Hello Mike,
The externalproject_add command has an option that might do what you want:
https://cmake.org/cmake/help/v3.8/module/ExternalProject.html
See:
|PATCH_COMMAND ...|
Command to patch downloaded source
Regards,
Micha
On 15-03-17 07:51, mike lojkovic wrote:
> So, I'm trying to get
On 30-07-17 04:36, jupiter wrote:
> I thought if I add -DCMAKE_CC_COMPILER=gcc that error should go, no,
> it still compile with the specific default cc:
>
> /usr/bin/cc
>
> How could I fix it?
>
> Thank you.
>
> On Sun, Jul 30, 2017 at 11:51 AM, jupiter
SMAT-master/catsmat/catsmat/cmake/../../libIMUSANT/FileProcessing/inc/IMUSANT_processing.h:61:35:
> error: expected ';' at end of declaration list
>
> const char * what () const noexcept
>
> ^
>
>^
>
>
>
>
/libmusicxml-3.00-src/cmake)
> add_subdirectory (catsmat/libIMUSANT/cmake)
> add_subdirectory (catsmat/libIMUSANT_Tests/cmake)
> add_subdirectory (catsmat/catsmat/cmake)
>
> set(CMAKE_CXX_STANDARD 14)
>
> On Thu, Jul 6, 2017 at 2:48 AM, Micha Hergarden
> <micha.herg
On 05-07-17 22:50, Sean Wayland wrote:
> I am attempting to write a cmakelists.txt file for an application.
> The application has a couple of dependencies.
> I have been able to build targets for the dependencies but when I try
> and add an executable for the main application I encounter this
:
4b989d5f158e5135bf543438af00b03db0102ade
My questions:
- I anyone else running into this?
- Is this new behaviour intended?
- If so, what must I change to my scripts to get my build working again?
- If not, what can I do to help resolve it?
Please let me know if more information is needed.
With kind regards,
Micha Hergarden
On 02/05/2014 10:15 AM, Stephen Kelly wrote:
Micha Hergarden wrote:
I have checked out and build the most recent versions to figure out when
this phenomena is introduced, and have narrowed it down to the following
commit :
4b989d5f158e5135bf543438af00b03db0102ade
Hi,
Thanks
it was
time I contributed some of it back.
With kind regards,
Micha Hergarden
signature.asc
Description: OpenPGP digital signature
--
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
package seems good. So, no further comments.
With kind regards,
Micha Hergarden
signature.asc
Description: OpenPGP digital signature
--
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
Hello Djou,
You will be better of asking this question on the 'cmake' mailing list
itself. That is geared towards cmake users. This list is for people
developing cmake itself.
Here is a cmake example to get you started:
project(DEMO)
cmake_minimum_required(VERSION 2.8)
add_executable(demo
41 matches
Mail list logo