[Cmake-commits] CMake branch, master, updated. v3.10.1-744-g89ec1aa

VERSION_MINOR 10) -set(CMake_VERSION_PATCH 20180109) +set(CMake_VERSION_PATCH 20180110) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

Re: [CMake] include_directories converting CMAKE_BINARY_DIR into relative path

Ah well, I figured out the problem, it was located between my chair and my keyboard. Everything works perfectly now. I sure do love cmake. Thanks, Russell On 01/09/18 15:46, Russell L. Carter wrote: Greetings, I am trying to generate a platform specific file by copying it from the source

[CMake] include_directories converting CMAKE_BINARY_DIR into relative path

Greetings, I am trying to generate a platform specific file by copying it from the source tree into a specific directory in the separate out-of-source build tree. The file generation works fine. When I try the following cmake code: set(target_dir ${CMAKE_BINARY_DIR}/nail/platform)

[Cmake-commits] CMake branch, master, updated. v3.10.1-743-ge44c582

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via e44c5828d368c81a1f478bf9c12ad4ff1bb87772 (commit) via

Re: [CMake] Multiple cross compiling

Currently CMake only supports a single platform / toolchain per build directory. If you need to build with multiple toolchains you will need to use some form of a wrapper. Which can either be an external script that invokes CMake multiple times or a CMake project that uses ExternalProject (

Re: [CMake] how to detect architecture ?

Thanks ! - Mail original - > De: "Konstantin Tokarev" > À: "Franck Houssen" , "CMake Mail List" > > Envoyé: Mardi 9 Janvier 2018 16:00:55 > Objet: Re: [CMake] how to detect architecture ? > > > > 09.01.2018, 17:58,

Re: [CMake] how to detect architecture ?

On Tue, Jan 9, 2018 at 6:57 AM, Franck Houssen wrote: > Is there a way to detect architecture ? > > Seems there is nothing simple since these old threads : > https://stackoverflow.com/questions/11944060/how-to- > detect-target-architecture-using-cmake/12024211#12024211 >

Re: [CMake] how to detect architecture ?

09.01.2018, 17:58, "Franck Houssen" : > Is there a way to detect architecture ? > > Seems there is nothing simple since these old threads : > https://stackoverflow.com/questions/11944060/how-to-detect-target-architecture-using-cmake/12024211#12024211 >

[CMake] how to detect architecture ?

Is there a way to detect architecture ? Seems there is nothing simple since these old threads : https://stackoverflow.com/questions/11944060/how-to-detect-target-architecture-using-cmake/12024211#12024211 https://stackoverflow.com/questions/16796629/cmake-create-architecture-aware-makefile

[Cmake-commits] CMake branch, release, updated. v3.10.1-6-g9559eb7

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via 9559eb7aa7bcb267f49bb304075ef952660753ee (commit) via

[Cmake-commits] CMake branch, master, updated. v3.10.1-741-ge405413

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via e40541339ae8a780bc410f0ef8b22d01e594c1ba (commit) via

[Cmake-commits] CMake branch, master, updated. v3.10.1-737-gae89a6e

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via ae89a6e110badd54c1aa8a2957f15e260224c7df (commit) via

[Cmake-commits] CMake branch, master, updated. v3.10.1-729-g847110e

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 847110e6faeffb85d12a1c145b3846263ee35bdc (commit) via

Re: [CMake] how to port to cmake a project using gnulib

On 2018-01-09 12:01- Cosimo Lupo wrote: Hello, I'm new to Cmake. I would like to port to cmake a project that is currently built with the Autotools and depends on gnulib, the GNU Portability Library: https://www.gnu.org/software/gnulib/ (The project in question is

Re: [CMake] how to port to cmake a project using gnulib

Alfred: Gnulib isn't library in usual sense, AFAIK it's a bunch of source files some of which may be added to the project if needed Cosimo: I think you should stay with autotools, otherwsie it might be a can of worms. Or get rid of gnulib. 09.01.2018, 15:55, "Cosimo Lupo"

Re: [CMake] how to port to cmake a project using gnulib

This is from the gnulib mailing list in reply to a similar question on how to use gnulib without autotools: https://lists.gnu.org/archive/html/bug-gnulib/2010-02/msg00248.html "Gnulib depends heavily on autoconf and automake. You could manually extract the portions you think you need and attempt

Re: [CMake] how to port to cmake a project using gnulib

Thanks for your help, Alfred. The problem is that very concept of "external dependency" seems to be at odds with the way gnulib is supposed to work. And the docs are clear that "Gnulib assumes that your project uses Autoconf. When using Gnulib, you will need to have Autoconf among your build

Re: [CMake] how to port to cmake a project using gnulib

Sorry, I did not got this hint.Well, you might still use gnulib as an external dependency (https://www.gnu.org/software/gnulib/manual/html_node/POSIX-Substitutes-Library.html#POSIX-Substitutes-Library). Maybe be it worth considering a better separation if the build tool is different.I need to

Re: [CMake] how to port to cmake a project using gnulib

Thanks. However, that's not exactly what I was looking for. The gnulib, by design, is not an external library that you link with, but a collection of modules that are meant to be copied into one's project. I would like to build ttfautohint with cmake (and ninja), not just adding ttfautohint as an

Re: [CMake] how to port to cmake a project using gnulib

Hello,I have some CMake projects that depend on autotools bases libs.I compile them as External project.https://cmake.org/cmake/help/latest/module/ExternalProject.htmlRegards

[CMake] how to port to cmake a project using gnulib

Hello, I'm new to Cmake. I would like to port to cmake a project that is currently built with the Autotools and depends on gnulib, the GNU Portability Library: https://www.gnu.org/software/gnulib/ (The project in question is https://www.freetype.org/ttfautohint/) It appears that gnulib itself

Re: [CMake] configure_file: escaping (single) quotes

OK. Got it to work ! Thanks - Mail original - > De: "Marc CHEVRIER" > À: "Franck Houssen" > Cc: "CMake Mail List" > Envoyé: Mardi 9 Janvier 2018 11:26:55 > Objet: Re: [CMake] configure_file: escaping (single) quotes >

Re: [cmake-developers] Optionally disabling static lib dependencies with COMPILE_DEPENDS

Perhaps keep an eye on the work going on in merge request 1524 , which may allow you to use object libraries in target_link_libraries(). Not sure if it would cut the dependencies in the way you are seeking, but maybe take a look and see.

Re: [CMake] configure_file: escaping (single) quotes

Yes, you have to rewrite your line as: CMD="mpirun -n @MPIEXEC_PREFLAGS@ @MPIEXEC_NUMPROC_FLAG@ @MPIEXEC_MAX_NUMPROCS@ @MPIEXEC_POSTFLAGS@" From: Franck Houssen Date: Tuesday 9 January 2018 at 11:23 To: "CHEVRIER, Marc" Cc: CMake Mail List

Re: [CMake] configure_file: escaping (single) quotes

- Mail original - De: "Marc CHEVRIER" À: "Franck Houssen" , "CMake Mail List" Envoyé: Mardi 9 Janvier 2018 10:29:30 Objet: Re: [CMake] configure_file: escaping (single) quotes The problem comes from CMake

[Cmake-commits] CMake branch, master, updated. v3.10.1-721-g89d1274

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 89d12746306571a323549ad0f8d11284999053d5 (commit) via

Re: [CMake] configure_file: escaping (single) quotes

On Tue, Jan 9, 2018 at 1:29 AM, J Decker wrote: > > > On Tue, Jan 9, 2018 at 1:24 AM, Franck Houssen > wrote: > >> Hello, >> >> I need configure_file to produce a bash file containing this line: >> VAR="${VAR//*'*#*'*/}" >> >> > maybe > > VAR="$"

Re: [CMake] configure_file: escaping (single) quotes

The problem comes from CMake evaluating variable VAR (i.e. expression ${VAR…}) and detect wrong syntax. The solution is to specify option @ONLY to command configure_file to avoid ${} evaluation. From: CMake on behalf of Franck Houssen Date:

Re: [CMake] configure_file: escaping (single) quotes

On Tue, Jan 9, 2018 at 1:24 AM, Franck Houssen wrote: > Hello, > > I need configure_file to produce a bash file containing this line: > VAR="${VAR//*'*#*'*/}" > > maybe VAR="$" "{VAR//*'*#*'*/}" > I tried without success VAR="${VAR//*'*#*'*/}" and

[CMake] configure_file: escaping (single) quotes

Hello, I need configure_file to produce a bash file containing this line: VAR="${VAR// ' # ' /}" I tried without success VAR="${VAR// ' # ' /}" and VAR="${VAR// \' # \' /}" with and without ESCAPE_QUOTES in configure_file : always get an error like "Syntax error in cmake code when parsing