Hi,
I'm using cmake to build a library (damaris). Once installed, I would like
users to be able to find it and its dependencies using find_package(damaris).
If I understand correctly, the way to do that is to have cmake create and
install a "damaris-config.cmake" file.
Is there a tutorial so
Unfortunately I encountered exactly the same problem.
It would be nice to describe in documentation that file(TO_NATIVE_PATH
...) means "native for target system" and also would be nice to
introduce the file(TO_HOST_NATIVE_PATH ...) subcommand.
On 26.3.2018 19:40, Miroslav Keš wrote:
> I'm cros
Hello everyone,
I try to append a string (target name) on a list inside a function called in
other CMakeLists.
I have the following project’s tree:
├── CMakeLists.txt
├── test
├── CMakeLists.txt
└── app
├── CMakeLists.txt
├── appA
│ ├── CMakeLists.txt
│
On 09/26/2018 10:23 AM, Hendrik Greving wrote:
> Is there any way before 3.13 to achieve what I need? Right now we
> modify LINK_FLAGS based on something that is computed with values
> from LOCATION.
[snip]
> our cmake setup is using LOCATION property for two targets to compute
> a relative path fr
Matthieu,
I think are asking about the CMakePackageConfigHelpers CMake module
(https://cmake.org/cmake/help/latest/module/CMakePackageConfigHelpers.html)
that defines the macro 'configure_package_config_file'.
You can probably find several tutorials or examples by searching github or
stackover
Using a cache variable seems not required. A function creates a new scope
and inherit a copy of all variables defined in the upper scope.
So, by adding a set command using PARENT_SCOPE in your function you can
update the variable in the parent scope:
function(addTest targetName)
Hi CMakers,
Hi try not do that too often but here comes a little promotion for a book
which (I think) deserve attention.
The CMake Cookbook by Radovan Bast, Roberto Di Remigio
https://www.packtpub.com/application-development/cmake-cookbook
I'm not the author but I participate in the book review a
As part of our build we use “mkdocs” to generate our documentation. Last night
I thought I made an innocuous change to our CMake files which ended up blowing
up all of our macOS builds (10.10 and 10.13 systems). It is all related to
trying to get Python/Mkdocs/Click to use a locale that is UTF-8
Thanks, those pointers helped a lot!
Matthieu
From: Thompson, KT
Sent: Thursday, September 27, 2018 3:30:33 PM
To: Dorier, Matthieu; cmake@cmake.org
Subject: RE: How to produce a -config.cmake file
Matthieu,
I think are asking about the CMakePackageConfigHe
Hi,
I'm using cmake 3.11.4 and the FindXercesC.cmake file shipped with it.
When I call find_package(XercesC REQUIRED) and XercesC is not in a standard
location, I have to set XercesC_INCLUDE_DIR to its include directory and
XercesC_LIBRARY to the location of the library.
If I set XercesC_LI
On 2018-09-27 20:26+0200 Eric Noulard wrote:
Hi CMakers,
Hi try not do that too often but here comes a little promotion for a book
which (I think) deserve attention.
The CMake Cookbook by Radovan Bast, Roberto Di Remigio
https://www.packtpub.com/application-development/cmake-cookbook
I don't
On Thu, 27 Sep 2018 at 23:34, Dorier, Matthieu wrote:
>
> When I call find_package(XercesC REQUIRED) and XercesC is not in a standard
> location, I have to set XercesC_INCLUDE_DIR to its include directory and
> XercesC_LIBRARY to the location of the library.
Correct. If Find-module can not gues
> On Sep 27, 2018, at 2:55 PM, Mateusz Loskot wrote:
>
>
>
>> I use to rely on a custom FindXercesC.cmake file that was using XercesC_ROOT
>> to figure all this out.
>> Is there any way to do the same here?
>
> There seem to be no Xxx_ROOT_DIR handled by this module
> https://cmake.org/cmake
On 27/09/18 22:55, Mateusz Loskot wrote:
On Thu, 27 Sep 2018 at 23:34, Dorier, Matthieu wrote:
When I call find_package(XercesC REQUIRED) and XercesC is not in a standard
location, I have to set XercesC_INCLUDE_DIR to its include directory and
XercesC_LIBRARY to the location of the library.
Thanks. Ok one step back. What we want is to have the same relative path
from binary/executable to linked library in build and install tree (which
we assume is the same for us). Looks like by default, e.g. cmake 3.9, puts
in an absolute path. The current (c-)makefiles compute the relative part of
a
Le jeu. 27 sept. 2018 à 23:49, Alan W. Irwin a
écrit :
> On 2018-09-27 20:26+0200 Eric Noulard wrote:
>
> > Hi CMakers,
> >
> > Hi try not do that too often but here comes a little promotion for a book
> > which (I think) deserve attention.
> > The CMake Cookbook by Radovan Bast, Roberto Di Remig
16 matches
Mail list logo