date:20190218

Re: [CMake] Problems with EnternalProjectAdd

2019-02-18 Thread workbe...@gmx.at


Can't i somehow output the pwd ??

best regards!

On 19.02.19 07:04, workbe...@gmx.at wrote:


Now i'm getting:

 Command failed: No such file or directory

   'cd 
/home/stuv/data/projects/programming/bsUltimate/build/build_env/freetype/src/freetype 
&& ./autogen.sh && ./configure && make'


but when i go to my bsUltimate path and type that command it works...


best regards!

On 19.02.19 06:57, Romain LEGUAY wrote:

Hi,

I think you need to set the variable CONFIGURE_COMMAND to empty like 
this:



ExternalProject_Add(
        freetype
        PREFIX "${BUILD_ENV}/freetype"
        GIT_REPOSITORY "https://github.com/brooklynpacket/freetype2.git;
        GIT_TAG 64bit

CONFIGURE_COMMAND ""
        BUILD_COMMAND "cd ${CMAKE_BUILD_DIR}/freetype/src/freetype 
&& ./autgen.sh && ./configure && make"

        LOG_DOWNLOAD ON
        LOG_INSTALL ON
        LOG_CONFIGURE ON
        LOG_BUILD ON
        LOG_TEST ON
        LOG_INSTALL ON
        )


Envoyé de mon iPad

Le 19 févr. 2019 à 06:51, workbe...@gmx.at  
mailto:workbe...@gmx.at>> a écrit :



I played around a bit a now have the following:

set(BUILD_ENV "${CMAKE_BINARY_DIR}/build_env" CACHE STRING INTERNAL)
set(LIBRARY_DIR "${CMAKE_BINARY_DIR}/lib" CACHE STRING INTERNAL)

    ExternalProject_Add(
        freetype
        PREFIX "${BUILD_ENV}/freetype"
        GIT_REPOSITORY "https://github.com/brooklynpacket/freetype2.git;
        GIT_TAG 64bit
        BUILD_COMMAND "cd ${CMAKE_BUILD_DIR}/freetype/src/freetype 
&& ./autgen.sh && ./configure && make"

        LOG_DOWNLOAD ON
        LOG_INSTALL ON
        LOG_CONFIGURE ON
        LOG_BUILD ON
        LOG_TEST ON
        LOG_INSTALL ON
        )

The logs are telling me: CMake Error: The source directory 
"/home/stuv/data/projects/programming/bsUltimate/build/build_env/freetype/src/freetype" 
does not appear to contain CMakeLists.txt.


Isn't the BUILD_COMMAND there if there is no CMakeLists.txt file 
available for building ? not many project provide cmake build files



best regards!






On 19.02.19 06:43, Michael Ellery wrote:
CMAKE_BUILD_DIR is not a standard variable (did you mean 
CMAKE_BINARY_DIR ?) - and the error seems to indicate that the 
variable is indeed empty so it tries to create the project 
directory at the root level.


-Mike

On Feb 18, 2019, at 8:58 PM, workbe...@gmx.at 
 > wrote:


Hi again,

i try to install my dependencies with ExternalProjectAdd but it 
gives me troubles... what's wrong with



ExternalProject_Add(
freetype
PREFIX "${CMAKE_BUILD_DIR}/freetype"
GIT_REPOSITORY 
"https://github.com/brooklynpacket/freetype2.git;

GIT_TAG 64bit
BUILD_COMMAND "cd ${CMAKE_BUILD_DIR}/freetype/src/freetype 
&& ./autgen.sh && ./configure && make"

LOG_DOWNLOAD ON
LOG_INSTALL ON
LOG_CONFIGURE ON
LOG_BUILD ON
LOG_TEST ON
LOG_INSTALL ON
)

best regards!

--

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 offering, please visit:


CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html


Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake



--

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 offering, please visit:


CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html


Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake


-- 

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Problems with EnternalProjectAdd

2019-02-18 Thread workbe...@gmx.at


Now i'm getting:

 Command failed: No such file or directory

   'cd 
/home/stuv/data/projects/programming/bsUltimate/build/build_env/freetype/src/freetype 
&& ./autogen.sh && ./configure && make'


but when i go to my bsUltimate path and type that command it works...


best regards!

On 19.02.19 06:57, Romain LEGUAY wrote:

Hi,

I think you need to set the variable CONFIGURE_COMMAND to empty like this:


ExternalProject_Add(
        freetype
        PREFIX "${BUILD_ENV}/freetype"
        GIT_REPOSITORY "https://github.com/brooklynpacket/freetype2.git;
        GIT_TAG 64bit

CONFIGURE_COMMAND ""
    BUILD_COMMAND "cd ${CMAKE_BUILD_DIR}/freetype/src/freetype && 
./autgen.sh && ./configure && make"

        LOG_DOWNLOAD ON
        LOG_INSTALL ON
        LOG_CONFIGURE ON
        LOG_BUILD ON
        LOG_TEST ON
        LOG_INSTALL ON
        )


Envoyé de mon iPad

Le 19 févr. 2019 à 06:51, workbe...@gmx.at  
mailto:workbe...@gmx.at>> a écrit :



I played around a bit a now have the following:

set(BUILD_ENV "${CMAKE_BINARY_DIR}/build_env" CACHE STRING INTERNAL)
set(LIBRARY_DIR "${CMAKE_BINARY_DIR}/lib" CACHE STRING INTERNAL)

    ExternalProject_Add(
        freetype
        PREFIX "${BUILD_ENV}/freetype"
        GIT_REPOSITORY "https://github.com/brooklynpacket/freetype2.git;
        GIT_TAG 64bit
        BUILD_COMMAND "cd ${CMAKE_BUILD_DIR}/freetype/src/freetype && 
./autgen.sh && ./configure && make"

        LOG_DOWNLOAD ON
        LOG_INSTALL ON
        LOG_CONFIGURE ON
        LOG_BUILD ON
        LOG_TEST ON
        LOG_INSTALL ON
        )

The logs are telling me: CMake Error: The source directory 
"/home/stuv/data/projects/programming/bsUltimate/build/build_env/freetype/src/freetype" 
does not appear to contain CMakeLists.txt.


Isn't the BUILD_COMMAND there if there is no CMakeLists.txt file 
available for building ? not many project provide cmake build files



best regards!






On 19.02.19 06:43, Michael Ellery wrote:
CMAKE_BUILD_DIR is not a standard variable (did you mean 
CMAKE_BINARY_DIR ?) - and the error seems to indicate that the 
variable is indeed empty so it tries to create the project directory 
at the root level.


-Mike

On Feb 18, 2019, at 8:58 PM, workbe...@gmx.at 
 > wrote:


Hi again,

i try to install my dependencies with ExternalProjectAdd but it 
gives me troubles... what's wrong with



ExternalProject_Add(
freetype
PREFIX "${CMAKE_BUILD_DIR}/freetype"
GIT_REPOSITORY 
"https://github.com/brooklynpacket/freetype2.git;

GIT_TAG 64bit
BUILD_COMMAND "cd ${CMAKE_BUILD_DIR}/freetype/src/freetype 
&& ./autgen.sh && ./configure && make"

LOG_DOWNLOAD ON
LOG_INSTALL ON
LOG_CONFIGURE ON
LOG_BUILD ON
LOG_TEST ON
LOG_INSTALL ON
)

best regards!

--

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 offering, please visit:


CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html


Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake



--

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 offering, please visit:


CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html


Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake
-- 

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Problems with EnternalProjectAdd

2019-02-18 Thread Romain LEGUAY

Hi,

I think you need to set the variable CONFIGURE_COMMAND to empty like this:

> ExternalProject_Add(
> freetype
> PREFIX "${BUILD_ENV}/freetype"
> GIT_REPOSITORY "https://github.com/brooklynpacket/freetype2.git;
> GIT_TAG 64bit
 CONFIGURE_COMMAND ""
> BUILD_COMMAND "cd ${CMAKE_BUILD_DIR}/freetype/src/freetype && 
> ./autgen.sh && ./configure && make"
> LOG_DOWNLOAD ON
> LOG_INSTALL ON
> LOG_CONFIGURE ON
> LOG_BUILD ON
> LOG_TEST ON
> LOG_INSTALL ON
> )

Envoyé de mon iPad

> Le 19 févr. 2019 à 06:51, workbe...@gmx.at  a écrit :
> 
> I played around a bit a now have the following:
> 
> set(BUILD_ENV "${CMAKE_BINARY_DIR}/build_env" CACHE STRING INTERNAL)
> set(LIBRARY_DIR "${CMAKE_BINARY_DIR}/lib" CACHE STRING INTERNAL)
> 
> ExternalProject_Add(
> freetype
> PREFIX "${BUILD_ENV}/freetype"
> GIT_REPOSITORY "https://github.com/brooklynpacket/freetype2.git;
> GIT_TAG 64bit
> BUILD_COMMAND "cd ${CMAKE_BUILD_DIR}/freetype/src/freetype && 
> ./autgen.sh && ./configure && make"
> LOG_DOWNLOAD ON
> LOG_INSTALL ON
> LOG_CONFIGURE ON
> LOG_BUILD ON
> LOG_TEST ON
> LOG_INSTALL ON
> )
> 
> The logs are telling me: CMake Error: The source directory 
> "/home/stuv/data/projects/programming/bsUltimate/build/build_env/freetype/src/freetype"
>  does not appear to contain CMakeLists.txt.
> 
> Isn't the BUILD_COMMAND there if there is no CMakeLists.txt file available 
> for building ? not many project provide cmake build files
> 
> 
> best regards!
> 
> 
> 
> 
> 
> 
>> On 19.02.19 06:43, Michael Ellery wrote:
>> CMAKE_BUILD_DIR is not a standard variable (did you mean CMAKE_BINARY_DIR ?) 
>> - and the error seems to indicate that the variable is indeed empty so it 
>> tries to create the project directory at the root level.
>> 
>> -Mike
>> 
>>> On Feb 18, 2019, at 8:58 PM, workbe...@gmx.at  wrote:
>>> 
>>> Hi again,
>>> 
>>> i try to install my dependencies with ExternalProjectAdd but it gives me 
>>> troubles... what's wrong with
>>> 
>>> 
>>> ExternalProject_Add(
>>> freetype
>>> PREFIX "${CMAKE_BUILD_DIR}/freetype"
>>> GIT_REPOSITORY "https://github.com/brooklynpacket/freetype2.git;
>>> GIT_TAG 64bit
>>> BUILD_COMMAND "cd ${CMAKE_BUILD_DIR}/freetype/src/freetype && 
>>> ./autgen.sh && ./configure && make"
>>> LOG_DOWNLOAD ON
>>> LOG_INSTALL ON
>>> LOG_CONFIGURE ON
>>> LOG_BUILD ON
>>> LOG_TEST ON
>>> LOG_INSTALL ON
>>> )
>>> 
>>> best regards!
>>> 
>>> -- 
>>> 
>>> 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 offering, please visit:
>>> 
>>> CMake Support: http://cmake.org/cmake/help/support.html
>>> CMake Consulting: http://cmake.org/cmake/help/consulting.html
>>> CMake Training Courses: http://cmake.org/cmake/help/training.html
>>> 
>>> Visit other Kitware open-source projects at 
>>> http://www.kitware.com/opensource/opensource.html
>>> 
>>> Follow this link to subscribe/unsubscribe:
>>> https://cmake.org/mailman/listinfo/cmake
>> 
> -- 
> 
> 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 offering, please visit:
> 
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
> 
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
> 
> Follow this link to subscribe/unsubscribe:
> https://cmake.org/mailman/listinfo/cmake
-- 

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Problems with EnternalProjectAdd

2019-02-18 Thread workbe...@gmx.at


I played around a bit a now have the following:

set(BUILD_ENV "${CMAKE_BINARY_DIR}/build_env" CACHE STRING INTERNAL)
set(LIBRARY_DIR "${CMAKE_BINARY_DIR}/lib" CACHE STRING INTERNAL)

    ExternalProject_Add(
        freetype
        PREFIX "${BUILD_ENV}/freetype"
        GIT_REPOSITORY "https://github.com/brooklynpacket/freetype2.git;
        GIT_TAG 64bit
        BUILD_COMMAND "cd ${CMAKE_BUILD_DIR}/freetype/src/freetype && 
./autgen.sh && ./configure && make"

        LOG_DOWNLOAD ON
        LOG_INSTALL ON
        LOG_CONFIGURE ON
        LOG_BUILD ON
        LOG_TEST ON
        LOG_INSTALL ON
        )

The logs are telling me: CMake Error: The source directory 
"/home/stuv/data/projects/programming/bsUltimate/build/build_env/freetype/src/freetype" 
does not appear to contain CMakeLists.txt.


Isn't the BUILD_COMMAND there if there is no CMakeLists.txt file 
available for building ? not many project provide cmake build files



best regards!






On 19.02.19 06:43, Michael Ellery wrote:

CMAKE_BUILD_DIR is not a standard variable (did you mean CMAKE_BINARY_DIR ?) - 
and the error seems to indicate that the variable is indeed empty so it tries 
to create the project directory at the root level.

-Mike


On Feb 18, 2019, at 8:58 PM, workbe...@gmx.at  wrote:

Hi again,

i try to install my dependencies with ExternalProjectAdd but it gives me 
troubles... what's wrong with


 ExternalProject_Add(
 freetype
 PREFIX "${CMAKE_BUILD_DIR}/freetype"
 GIT_REPOSITORY "https://github.com/brooklynpacket/freetype2.git;
 GIT_TAG 64bit
 BUILD_COMMAND "cd ${CMAKE_BUILD_DIR}/freetype/src/freetype && ./autgen.sh && 
./configure && make"
 LOG_DOWNLOAD ON
 LOG_INSTALL ON
 LOG_CONFIGURE ON
 LOG_BUILD ON
 LOG_TEST ON
 LOG_INSTALL ON
 )

best regards!

--

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake



--

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Problems with EnternalProjectAdd

2019-02-18 Thread Michael Ellery

CMAKE_BUILD_DIR is not a standard variable (did you mean CMAKE_BINARY_DIR ?) - 
and the error seems to indicate that the variable is indeed empty so it tries 
to create the project directory at the root level.

-Mike

> On Feb 18, 2019, at 8:58 PM, workbe...@gmx.at  wrote:
> 
> Hi again,
> 
> i try to install my dependencies with ExternalProjectAdd but it gives me 
> troubles... what's wrong with
> 
> 
> ExternalProject_Add(
> freetype
> PREFIX "${CMAKE_BUILD_DIR}/freetype"
> GIT_REPOSITORY "https://github.com/brooklynpacket/freetype2.git;
> GIT_TAG 64bit
> BUILD_COMMAND "cd ${CMAKE_BUILD_DIR}/freetype/src/freetype && 
> ./autgen.sh && ./configure && make"
> LOG_DOWNLOAD ON
> LOG_INSTALL ON
> LOG_CONFIGURE ON
> LOG_BUILD ON
> LOG_TEST ON
> LOG_INSTALL ON
> )
> 
> best regards!
> 
> -- 
> 
> 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 offering, please visit:
> 
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
> 
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
> 
> Follow this link to subscribe/unsubscribe:
> https://cmake.org/mailman/listinfo/cmake

-- 

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Problems with EnternalProjectAdd

2019-02-18 Thread workbe...@gmx.at


I forgot the error message:

CMake Error at 
/usr/local/share/cmake-3.13/Modules/ExternalProject.cmake:1659 (file):

  file problem creating directory: /freetype/src/freetype-stamp
Call Stack (most recent call first):
  /usr/local/share/cmake-3.13/Modules/ExternalProject.cmake:3057 
(_ep_set_directories)

  bin/tools/cmake/modules/BSBasicTests.cmake:24 (ExternalProject_Add)
  CMakeLists.txt:33 (bs_install_dependencies)


CMake Error at 
/usr/local/share/cmake-3.13/Modules/ExternalProject.cmake:1661 (message):

  dir '/freetype/src/freetype-stamp' does not exist after
  file(MAKE_DIRECTORY)
Call Stack (most recent call first):
  /usr/local/share/cmake-3.13/Modules/ExternalProject.cmake:3057 
(_ep_set_directories)

  bin/tools/cmake/modules/BSBasicTests.cmake:24 (ExternalProject_Add)
  CMakeLists.txt:33 (bs_install_dependencies)


-- Configuring incomplete, errors occurred!
See also 
"/home/stuv/data/projects/programming/bsUltimate/build/CMakeFiles/CMakeOutput.log".



On 19.02.19 05:58, workbe...@gmx.at wrote:

Hi again,

i try to install my dependencies with ExternalProjectAdd but it gives 
me troubles... what's wrong with



    ExternalProject_Add(
        freetype
        PREFIX "${CMAKE_BUILD_DIR}/freetype"
        GIT_REPOSITORY "https://github.com/brooklynpacket/freetype2.git;
        GIT_TAG 64bit
        BUILD_COMMAND "cd ${CMAKE_BUILD_DIR}/freetype/src/freetype && 
./autgen.sh && ./configure && make"

        LOG_DOWNLOAD ON
        LOG_INSTALL ON
        LOG_CONFIGURE ON
        LOG_BUILD ON
        LOG_TEST ON
        LOG_INSTALL ON
        )

best regards!


--

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

[Cmake-commits] CMake branch, master, updated. v3.14.0-rc2-119-g2a1f661

2019-02-18 Thread Kitware Robot via Cmake-commits

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  2a1f6617911da55e6563a775c807270a7f566b18 (commit)
  from  75b45956e044701c0ebe6dbc433f629e0558bdb8 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2a1f6617911da55e6563a775c807270a7f566b18
commit 2a1f6617911da55e6563a775c807270a7f566b18
Author: Kitware Robot 
AuthorDate: Tue Feb 19 00:01:06 2019 -0500
Commit: Kitware Robot 
CommitDate: Tue Feb 19 00:01:06 2019 -0500

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 6af2c8e..9c45022 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,5 +1,5 @@
 # CMake version number components.
 set(CMake_VERSION_MAJOR 3)
 set(CMake_VERSION_MINOR 14)
-set(CMake_VERSION_PATCH 20190218)
+set(CMake_VERSION_PATCH 20190219)
 #set(CMake_VERSION_RC 1)

---

Summary of changes:
 Source/CMakeVersion.cmake | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
https://cmake.org/mailman/listinfo/cmake-commits

[CMake] Problems with EnternalProjectAdd

2019-02-18 Thread workbe...@gmx.at


Hi again,

i try to install my dependencies with ExternalProjectAdd but it gives me 
troubles... what's wrong with



    ExternalProject_Add(
        freetype
        PREFIX "${CMAKE_BUILD_DIR}/freetype"
        GIT_REPOSITORY "https://github.com/brooklynpacket/freetype2.git;
        GIT_TAG 64bit
        BUILD_COMMAND "cd ${CMAKE_BUILD_DIR}/freetype/src/freetype && 
./autgen.sh && ./configure && make"

        LOG_DOWNLOAD ON
        LOG_INSTALL ON
        LOG_CONFIGURE ON
        LOG_BUILD ON
        LOG_TEST ON
        LOG_INSTALL ON
        )

best regards!

--

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Question about set

2019-02-18 Thread workbe...@gmx.at

Thank you.

On 18.02.19 21:46, Craig Scott wrote:

On Tue, Feb 19, 2019 at 4:16 AM Kyle Edwards via CMake 
mailto:cmake@cmake.org>> wrote:

On Mon, 2019-02-18 at 17:59 +0100, Andreas Naumann wrote:
> Hey,
>
> I would introduce a list with the allowed values and introduce a
> macro
> "checked_set", which tests the setting or aborts.
>
> Regards,
> Andreas"
>
> Am 18.02.19 um 15:06 schrieb workbe...@gmx.at
:
> >
> > Hi everyone,
> >
> > i've looked the web but found no result. I need a string variable
> > that
> > allows only certain values, like bool variables only allow
> > true/false
> > my string should be either "A" or "B" ...

Is this a cache variable or a regular variable? Cache variables have
this enum-like support in the form of the STRINGS property. Example:

set(MYSTRING "A" CACHE STRING "Documentation for the variable")
set_property(CACHE MYSTRING PROPERTY STRINGS "A;B")

Note that this isn't an enforcing feature, only a convenience for 
CMake GUI and ccmake. It tells those tools what to show as selectable 
options for that cache variable, but you can still set the variable to 
anything you like via the cmake -D command line option or in the 
project itself.

--
Craig Scott
Melbourne, Australia
https://crascit.com

Get the hand-book for every CMake user: Professional CMake: A 
Practical Guide 

-- 

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

[cmake-developers] Using CMake as a package manager vs using a dedicated package management tool (like Conan)

2019-02-18 Thread Timothy Wrona

I have been working on a new C++ project and I am trying to decide whether
I should use CMake as my package management system or if I should use a
dedicated package management tool such as Conan.

For more information on Conan see: https://conan.io/

I am trying to understand the main difference between using Conan to manage
dependencies vs using CMakes "FetchContent" module. Are there any
compelling reasons to prefer something like Conan?
-- 

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake-developers

[CMake] Using CMake as a package manager vs using a dedicated package management tool (like Conan)

2019-02-18 Thread Timothy Wrona

I have been working on a new C++ project and I am trying to decide whether
I should use CMake as my package management system or if I should use a
dedicated package management tool such as Conan.

For more information on Conan see: https://conan.io/

I am trying to understand the main difference between using Conan to manage
dependencies vs using CMakes "FetchContent" module. Are there any
compelling reasons to prefer something like Conan?
-- 

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

[cmake-developers] Dead CMake Redesign Projects

2019-02-18 Thread Taylor Holberton

Hello!

Since about July of 2018, I've been trying to design an interpreter library
for the CMake language, common for the cmake, cpack, and ctest tools. It
was my idea that I could create an extensible library for the CMake
project, that could make it easier to add commands, generators, and
integration into other scripting languages.

Today, I'm calling it quits. It turns out that, even after retrying several
times with fewer requirements, that it's just too much work for one person
(probably too much for two or three people as well.) I've uploaded all the
repositories of the several attempts I've made at doing this.

https://gitlab.kitware.com/tay10r/cmake-interpretation

The cmake-interpretation is probably the furthest I've taken any of the
projects, and was the first attempt I made at the idea. I believe I posted
this project in the mailing list as cmake-lang when I was first starting it
out. See tag 'last-known-working-state' if you try to build it.

https://gitlab.kitware.com/tay10r/cmEngine

The cmEngine project was written once in C++ and then over again in C. The
version I uploaded is the C version. The cmEngine project is neat because
the interpreter can entirely be sandboxed and the testing for it is very
elaborate (80% test coverage.) I would say this project has the best
foundation. It's also got the most documentation.

https://gitlab.kitware.com/tay10r/cmlang

This is the latest attempt at the redesign. This version has the fastest
lexer+parser by far. Rudimentary testing indicated to me that the
lexer+parser beat the one in original CMake project by a decent margin.
This is probably due to the use of memory mapping the source file and fewer
number of calls to malloc. The diagnostics in this project are probably the
best and most expressive.

Feel free to pick apart these projects anyway you choose to. I'm fine with
any of them being relicensed to Apache 2.0, MIT, or BSD (in that order of
preference) if anyone decides to use them.
-- 

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake-developers

Re: [CMake] Question about set

2019-02-18 Thread Craig Scott

On Tue, Feb 19, 2019 at 4:16 AM Kyle Edwards via CMake 
wrote:

> On Mon, 2019-02-18 at 17:59 +0100, Andreas Naumann wrote:
> > Hey,
> >
> > I would introduce a list with the allowed values and introduce a
> > macro
> > "checked_set", which tests the setting or aborts.
> >
> > Regards,
> > Andreas"
> >
> > Am 18.02.19 um 15:06 schrieb workbe...@gmx.at:
> > >
> > > Hi everyone,
> > >
> > > i've looked the web but found no result. I need a string variable
> > > that
> > > allows only certain values, like bool variables only allow
> > > true/false
> > > my string should be either "A" or "B" ...
>
> Is this a cache variable or a regular variable? Cache variables have
> this enum-like support in the form of the STRINGS property. Example:
>
> set(MYSTRING "A" CACHE STRING "Documentation for the variable")
> set_property(CACHE MYSTRING PROPERTY STRINGS "A;B")
>

Note that this isn't an enforcing feature, only a convenience for CMake GUI
and ccmake. It tells those tools what to show as selectable options for
that cache variable, but you can still set the variable to anything you
like via the cmake -D command line option or in the project itself.

-- 
Craig Scott
Melbourne, Australia
https://crascit.com

Get the hand-book for every CMake user: Professional CMake: A Practical
Guide 
-- 

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Question about functions

2019-02-18 Thread Andreas Naumann


Am 18.02.19 um 20:43 schrieb workbe...@gmx.at:

Hi everyone,

i have a function like:

FUNCTION(checksyste_64Bit arg1)

    IF(CMAKE_SIZEOF_VOID_P EQUAL 8)

        SET(${arg1} TRUE PARENT_SCOPE)

ENDFUNCTION()


but when i call it with an INTERNAL variable i've set before with

SET(SYSTEM_64BIT FALSE CACHE INTERNAL)

checksystem_64bit(${SYSTEM_64BIT})

the ${SYSTE_64BIT} variable stays the same, i thought when i use 
PARENT_SCOPE on a variable i can change it's value from inside the 
function ?



best regards!

You should call your function without dollar and braces around the 
variable, i.e.


  checksystem_64bit(SYSTEM_64BIT)

--

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

[CMake] Question about functions

2019-02-18 Thread workbe...@gmx.at


Hi everyone,

i have a function like:

FUNCTION(checksyste_64Bit arg1)

    IF(CMAKE_SIZEOF_VOID_P EQUAL 8)

        SET(${arg1} TRUE PARENT_SCOPE)

ENDFUNCTION()


but when i call it with an INTERNAL variable i've set before with

SET(SYSTEM_64BIT FALSE CACHE INTERNAL)

checksystem_64bit(${SYSTEM_64BIT})

the ${SYSTE_64BIT} variable stays the same, i thought when i use 
PARENT_SCOPE on a variable i can change it's value from inside the 
function ?



best regards!

--

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Question about set

2019-02-18 Thread workbe...@gmx.at

I need it for an INTERNAL variable, for the different android 
architecture types that are supported. so he can only set one of the 
available arch types.



On 18.02.19 18:16, Kyle Edwards wrote:

On Mon, 2019-02-18 at 17:59 +0100, Andreas Naumann wrote:

Hey,

I would introduce a list with the allowed values and introduce a
macro
"checked_set", which tests the setting or aborts.

Regards,
Andreas"

Am 18.02.19 um 15:06 schrieb workbe...@gmx.at:

Hi everyone,

i've looked the web but found no result. I need a string variable
that
allows only certain values, like bool variables only allow
true/false
my string should be either "A" or "B" ...

Is this a cache variable or a regular variable? Cache variables have
this enum-like support in the form of the STRINGS property. Example:

set(MYSTRING "A" CACHE STRING "Documentation for the variable")
set_property(CACHE MYSTRING PROPERTY STRINGS "A;B")

If you need to do this with an ordinary variable, consider using
variable_watch().

Kyle


--

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] fixup-bundle usability

2019-02-18 Thread Andreas Naumann

Thank you very much for your explaination. At the moment, I link only to 
boost and some in-house libraries. When experimenting with CMake and 
reading the docs, I got the same impression as you described. And I 
hoped to miss something obvious.


When I understand you correctly, one have to set the directories from 
hand. Furthermore there are additional variables (in case of VTK), which 
contain the library directories. But modern CMake works with targets and 
properties and let the dependencies propagate.


To test the idea a little bit, I startet with the following function

function(setBundle targetName dest)
  install(TARGETS ${targetName} DESTINATION ${dest})

  get_target_property(targtDeps ${targetName} LINK_LIBRARIES)
  file(TO_CMAKE_PATH "${CMAKE_INSTALL_PREFIX}" instPref)
  set(depDirs )
  foreach(t IN LISTS targtDeps)
    #disable the INTERFACE target due to error later.
    if(TARGET ${t} AND NOT ("${t}" STREQUAL "Boost::disable_autolinking"))
      get_target_property(isImported ${t} IMPORTED)
      if(isImported)
        get_target_property(depFile ${t} IMPORTED_LOCATION_DEBUG)
        if(depFile)
          get_filename_component(cdepDir ${depFile} DIRECTORY)
          list(APPEND depDirs ${cdepDir})
        endif()
      endif()
    endif()
  endforeach()
  install(CODE "include(BundleUtilities)
fixup_bundle(\"${instPref}/${dest}/$\" 
\"\" \"${depDirs}\")")

endfunction()

It is far away from optimal and has some drawbacks, especially the 
detection of interface libraries and the location of the imported target 
should be more fail proof.


How can I ask for feature requests on gitlab? I found the issue tracker, 
but nothing in regard for a feature or improvement.


Andreas

Am 18.02.19 um 15:56 schrieb Francis Giraldeau:
You are right, the fixup bundle is difficult to use. Here are some 
undocumented tips:


Put the install(CODE) with the fixup_bundle() call in a CMakeLists.txt 
in its own directory. In your main CMakeLists.txt file, add this 
directory with add_subdirectory() last. This install(CODE) will run 
after all the other install directive, otherwise the fixup_bundle() 
might run before other targets are installed.


The main thing is to build the library path variable. Yes, this 
information can be recovered from the target itself, but 
fixup_bundle() won't gather that info for you. Here is an example with 
Qt:


get_target_property(QT_CORE_LIBQt5::CoreLOCATION)
get_filename_component(QT_RUNTIME_DIR"${QT_CORE_LIB}"DIRECTORY)
list(APPENDLIBS_PATH"${QT_RUNTIME_DIR}")

If you are using VTK, there is already a variable:
list(APPENDLIBS_PATH"${VTK_RUNTIME_LIBRARY_DIRS}")

You might as well run windeployqt (and similar tool for other 
platforms) inside install(CODE) script if you have a Qt app, such that 
the styles and the plugins and other stuff gets copied.


execute_process(COMMANDwindeployqt.exe--release\"\${MAIN_APP}\")

Workaround wrong tool detection using MinGW on Windows:
if(WIN32ANDNOTMSVC)
set(GP_TOOL"objdump")
endif()
install(CODE "\
...
include(BundleUtilities)
set(gp_tool\"${GP_TOOL}\")
fixup_bundle(\"\${MAIN_APP}\"\"\"\"${LIBS_PATH}\")
...
And there is the escaping... You have to escape quotes inside
the script. Escape the '$' sign if you want to refer to the
variable at install time. Remember that you don't have access
to configure-time variables at install time. Unescaped '$' prefix
will be replaced by its value at configure time, somewhat like
a macro or a template.

To see the generated script, look into ${CMAKE_BINARY_DIR} with
the directory name corresponding to the CMakeLists.txt containing
the install(CODE). Example:
${CMAKE_SOURCE_DIR}/cmake/bundle/CMakeLists.txt
-> ${CMAKE_BINARY_DIR}/cmake/bundle/cmake_install.cmake
You can check the generated script, its very
handy when things go wrong.
Also, it is easier to put all libraries and binaries in their
own directory. I have this near the begining of my project's
CMakeLists.
set(CMAKE_ARCHIVE_OUTPUT_DIRECTORY${CMAKE_BINARY_DIR}/lib)
set(CMAKE_LIBRARY_OUTPUT_DIRECTORY${CMAKE_BINARY_DIR}/lib)
set(CMAKE_RUNTIME_OUTPUT_DIRECTORY${CMAKE_BINARY_DIR}/bin)
If you have some library that you don't want in your bundle,
you might want to disable install for it, for instance,
google test:
add_subdirectory(3rdparty/googletest/EXCLUDE_FROM_ALL)
I'm using "ntldd.exe -R" on Windows to check the dependencies manually
(its very much like ldd on Linux). It is much more handy than
dependency walker.
Fixup_bundle is not magical either. The library dependencies must be
known beforehand. It means that if you do some dlopen() tricks at
runtime, fixup_bundle() cannot know that and you will have to install
these libraries manually yourself. One notable example of this is
Intel MKL using the Single Dynamic Library (mkl_rt). Using this
library entry point simplifies the linking and will load the
best library at runtime depending on the hardware. Fixup_bundle() will
copy only mkl_rt and you have to copy the other mkl libraries to
avoid

Re: [CMake] Question about set

2019-02-18 Thread Kyle Edwards via CMake

On Mon, 2019-02-18 at 17:59 +0100, Andreas Naumann wrote:
> Hey,
> 
> I would introduce a list with the allowed values and introduce a
> macro 
> "checked_set", which tests the setting or aborts.
> 
> Regards,
> Andreas"
> 
> Am 18.02.19 um 15:06 schrieb workbe...@gmx.at:
> > 
> > Hi everyone,
> > 
> > i've looked the web but found no result. I need a string variable
> > that 
> > allows only certain values, like bool variables only allow
> > true/false 
> > my string should be either "A" or "B" ...

Is this a cache variable or a regular variable? Cache variables have
this enum-like support in the form of the STRINGS property. Example:

set(MYSTRING "A" CACHE STRING "Documentation for the variable")
set_property(CACHE MYSTRING PROPERTY STRINGS "A;B")

If you need to do this with an ordinary variable, consider using
variable_watch().

Kyle
-- 

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Question about set

2019-02-18 Thread Andreas Naumann


Hey,

I would introduce a list with the allowed values and introduce a macro 
"checked_set", which tests the setting or aborts.


Regards,
Andreas

Am 18.02.19 um 15:06 schrieb workbe...@gmx.at:

Hi everyone,

i've looked the web but found no result. I need a string variable that 
allows only certain values, like bool variables only allow true/false 
my string should be either "A" or "B" ...



best regards!



--

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Fwd: Re: Question about CMAKE_MODULE_PATH

2019-02-18 Thread workbe...@gmx.at


Thanks alot!

On 18.02.19 17:20, Gonzalo Garramuño wrote:

El 18/2/19 a las 13:15, workbe...@gmx.at escribió:

Thank you, that did the trick. Now my other question is there a 
function in cmake that does abort the build/makefile generation 
process ? for example if i find out the system is not 64bit - is 
there something like quit() ?




message( FATAL_ERROR "your quit message" )


--

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Fwd: Re: Question about CMAKE_MODULE_PATH

2019-02-18 Thread Gonzalo Garramuño


El 18/2/19 a las 13:15, workbe...@gmx.at escribió:

Thank you, that did the trick. Now my other question is there a 
function in cmake that does abort the build/makefile generation 
process ? for example if i find out the system is not 64bit - is there 
something like quit() ?




message( FATAL_ERROR "your quit message" )

--
Gonzalo Garramuño

--

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Fwd: Re: Question about CMAKE_MODULE_PATH

2019-02-18 Thread workbe...@gmx.at

Thank you, that did the trick. Now my other question is there a function 
in cmake that does abort the build/makefile generation process ? for 
example if i find out the system is not 64bit - is there something like 
quit() ?


On 18.02.19 17:04, workbe...@gmx.at wrote:





 Forwarded Message 
Subject:Re: [CMake] Question about CMAKE_MODULE_PATH
Date:   Mon, 18 Feb 2019 16:58:26 +0100
From:   workbe...@gmx.at 
To: Kyle Edwards 



here is my code:


set(MODULE_PATH "compile/tools/cmake/modules")

LIST(APPEND CMAKE_MODULE_PATH ${MODULE_PATH})

now i try to include with

INCLUDE(basic_tests)

and i get an error that the file can't be found when typing cmake ../ 
from within my build path.




On 18.02.19 16:54, Kyle Edwards wrote:

On Mon, 2019-02-18 at 16:50 +0100, workbe...@gmx.at wrote:

Doesn't the content of CMAKE_MODULE_PATH should also include the path
to
the default modules ??

The default modules are automatically checked by CMake, independently
of the contents of CMAKE_MODULE_PATH. They should not normally be
present in CMAKE_MODULE_PATH.


i try to load custom modules. i use


list(append CMAKE_MODULE_PATH "/mypathtomdoules")

The "append" argument should be uppercase:

list(APPEND CMAKE_MODULE_PATH "/mypathtomodules")

Did you receive any warnings about an invalid argument to list()?

Kyle



-- 

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Fwd: Re: Question about CMAKE_MODULE_PATH

2019-02-18 Thread Kyle Edwards via CMake

On Mon, 2019-02-18 at 17:04 +0100, workbe...@gmx.at wrote:
> 
> 
> 
>  Forwarded Message 
> Subject:  Re: [CMake] Question about CMAKE_MODULE_PATH
> Date: Mon, 18 Feb 2019 16:58:26 +0100
> From: workbe...@gmx.at 
> To:   Kyle Edwards 
> 
> here is my code:
> 
> 
> set(MODULE_PATH "compile/tools/cmake/modules")
Try this instead:
set(MODULE_PATH "${CMAKE_SOURCE_DIR}/compile/tools/cmake/modules")
Kyle

-- 

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

[CMake] Fwd: Re: Question about CMAKE_MODULE_PATH

2019-02-18 Thread workbe...@gmx.at

 Forwarded Message 
Subject:Re: [CMake] Question about CMAKE_MODULE_PATH
Date:   Mon, 18 Feb 2019 16:58:26 +0100
From:   workbe...@gmx.at 
To: Kyle Edwards 

here is my code:

set(MODULE_PATH "compile/tools/cmake/modules")

LIST(APPEND CMAKE_MODULE_PATH ${MODULE_PATH})

now i try to include with

INCLUDE(basic_tests)

and i get an error that the file can't be found when typing cmake ../ 
from within my build path.

On 18.02.19 16:54, Kyle Edwards wrote:

On Mon, 2019-02-18 at 16:50 +0100, workbe...@gmx.at wrote:

Doesn't the content of CMAKE_MODULE_PATH should also include the path
to
the default modules ??

The default modules are automatically checked by CMake, independently
of the contents of CMAKE_MODULE_PATH. They should not normally be
present in CMAKE_MODULE_PATH.

i try to load custom modules. i use

list(append CMAKE_MODULE_PATH "/mypathtomdoules")

The "append" argument should be uppercase:

list(APPEND CMAKE_MODULE_PATH "/mypathtomodules")

Did you receive any warnings about an invalid argument to list()?

Kyle

-- 

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Question about CMAKE_MODULE_PATH

2019-02-18 Thread Kyle Edwards via CMake

On Mon, 2019-02-18 at 16:50 +0100, workbe...@gmx.at wrote:
> Doesn't the content of CMAKE_MODULE_PATH should also include the path
> to 
> the default modules ??

The default modules are automatically checked by CMake, independently
of the contents of CMAKE_MODULE_PATH. They should not normally be
present in CMAKE_MODULE_PATH.

> > i try to load custom modules. i use
> > 
> > 
> > list(append CMAKE_MODULE_PATH "/mypathtomdoules")

The "append" argument should be uppercase:

list(APPEND CMAKE_MODULE_PATH "/mypathtomodules")

Did you receive any warnings about an invalid argument to list()?

Kyle
-- 

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Question about CMAKE_MODULE_PATH

2019-02-18 Thread workbe...@gmx.at

Doesn't the content of CMAKE_MODULE_PATH should also include the path to 
the default modules ??


On 18.02.19 16:48, workbe...@gmx.at wrote:

Hi everyone,


i try to load custom modules. i use


list(append CMAKE_MODULE_PATH "/mypathtomdoules")

and then i try to load the module with

include(mymodule)

but he can't find it. now i tried to output the content of 
CMAKE_MODULE_PATH with the cmake_print_variable from the 
CMakePrintHelpers module and the output of


cmake_print_variables(CMAKE_MODULE_PATH) is "" ...


what's going on here ?


best regards!


--

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

[CMake] Question about CMAKE_MODULE_PATH

2019-02-18 Thread workbe...@gmx.at


Hi everyone,


i try to load custom modules. i use


list(append CMAKE_MODULE_PATH "/mypathtomdoules")

and then i try to load the module with

include(mymodule)

but he can't find it. now i tried to output the content of 
CMAKE_MODULE_PATH with the cmake_print_variable from the 
CMakePrintHelpers module and the output of


cmake_print_variables(CMAKE_MODULE_PATH) is "" ...


what's going on here ?


best regards!

--

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

[Cmake-commits] CMake branch, release, updated. v3.14.0-rc2-7-g926a97e

2019-02-18 Thread Kitware Robot via Cmake-commits

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  926a97e97520bcdf509126e03a3d2f40ee20d479 (commit)
   via  0f5a9f7934913935d632fc596ba1b585aa10fa29 (commit)
  from  1f8ed4141979ee4e2f2cc6aab8ad31a4942bd056 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
---

Summary of changes:
 Help/command/file.rst | 46 +++---
 1 file changed, 23 insertions(+), 23 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
https://cmake.org/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, master, updated. v3.14.0-rc2-118-g75b4595

2019-02-18 Thread Kitware Robot via Cmake-commits

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  75b45956e044701c0ebe6dbc433f629e0558bdb8 (commit)
   via  926a97e97520bcdf509126e03a3d2f40ee20d479 (commit)
  from  566652b0c8ffe6896d3d3ae1cafd5834eecd (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=75b45956e044701c0ebe6dbc433f629e0558bdb8
commit 75b45956e044701c0ebe6dbc433f629e0558bdb8
Merge: 566652b 926a97e
Author: Brad King 
AuthorDate: Mon Feb 18 10:22:55 2019 -0500
Commit: Brad King 
CommitDate: Mon Feb 18 10:22:55 2019 -0500

Merge branch 'release-3.14'


---

Summary of changes:


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
https://cmake.org/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, master, updated. v3.14.0-rc2-116-g566652b

2019-02-18 Thread Kitware Robot via Cmake-commits

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  566652b0c8ffe6896d3d3ae1cafd5834eecd (commit)
   via  0f5a9f7934913935d632fc596ba1b585aa10fa29 (commit)
  from  0923246b2e2fb5be0d2fa1b256879a326aeee13b (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=566652b0c8ffe6896d3d3ae1cafd5834eecd
commit 566652b0c8ffe6896d3d3ae1cafd5834eecd
Merge: 0923246 0f5a9f7
Author: Brad King 
AuthorDate: Mon Feb 18 15:22:27 2019 +
Commit: Kitware Robot 
CommitDate: Mon Feb 18 10:22:35 2019 -0500

Merge topic 'file_symlink_docs'

0f5a9f7934 Help: Clarify and improve readability of link-related file 
subcommands

Acked-by: Kitware Robot 
Merge-request: !2974


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=0f5a9f7934913935d632fc596ba1b585aa10fa29
commit 0f5a9f7934913935d632fc596ba1b585aa10fa29
Author: Craig Scott 
AuthorDate: Sat Feb 16 19:32:52 2019 +1100
Commit: Craig Scott 
CommitDate: Sat Feb 16 20:55:49 2019 +1100

Help: Clarify and improve readability of link-related file subcommands

diff --git a/Help/command/file.rst b/Help/command/file.rst
index db4d6fc..465e567 100644
--- a/Help/command/file.rst
+++ b/Help/command/file.rst
@@ -26,8 +26,8 @@ Synopsis
 file(`MAKE_DIRECTORY`_ [...])
 file({`COPY`_ | `INSTALL`_} ... DESTINATION  [...])
 file(`SIZE`_  )
-file(`READ_SYMLINK`_  )
-file(`CREATE_LINK`_   [...])
+file(`READ_SYMLINK`_  )
+file(`CREATE_LINK`_   [...])
 
   `Path Conversion`_
 file(`RELATIVE_PATH`_   )
@@ -350,22 +350,22 @@ pointing to a file and is readable.
 
 .. code-block:: cmake
 
-  file(READ_SYMLINK  )
+  file(READ_SYMLINK  )
 
-Read the symlink at  and put the result in .
-Requires that  is a valid path pointing to a symlink. If
- does not exist, or is not a symlink, an error is thrown.
+This subcommand queries the symlink  and stores the path it
+points to in the result .  If  does not exist or
+is not a symlink, CMake issues a fatal error.
 
 Note that this command returns the raw symlink path and does not resolve
-relative symlinks. If you want to resolve the relative symlink yourself, you
-could do something like this:
+a relative path.  The following is an example of how to ensure that an
+absolute path is obtained:
 
 .. code-block:: cmake
 
-  set(filename "/path/to/foo.sym")
-  file(READ_SYMLINK "${filename}" result)
+  set(linkname "/path/to/foo.sym")
+  file(READ_SYMLINK "${linkname}" result)
   if(NOT IS_ABSOLUTE "${result}")
-get_filename_component(dir "${filename}" DIRECTORY)
+get_filename_component(dir "${linkname}" DIRECTORY)
 set(result "${dir}/${result}")
   endif()
 
@@ -373,23 +373,23 @@ could do something like this:
 
 .. code-block:: cmake
 
-  file(CREATE_LINK  
+  file(CREATE_LINK  
[RESULT ] [COPY_ON_ERROR] [SYMBOLIC])
 
-Create a link to  at .
+Create a link  that points to .
+It will be a hard link by default, but providing the ``SYMBOLIC`` option
+results in a symbolic link instead.  Hard links require that ``original``
+exists and is a file, not a directory.  If  already exists,
+it will be overwritten.
 
-It is a hard link by default. This can be changed to symbolic links by
-using ``SYMBOLIC``.  The original file needs to exist for hard links.
-
-The  variable, if specified, gets the status of the operation.
-It is set to ``0`` in case of success. Otherwise, it contains the error
-generated. In case of failures, if ``RESULT`` is not specified, a fatal error
-is emitted.
+The  variable, if specified, receives the status of the operation.
+It is set to ``0`` upon success or an error message otherwise.  If ``RESULT``
+is not specified and the operation fails, a fatal error is emitted.
 
 Specifying ``COPY_ON_ERROR`` enables copying the file as a fallback if
-creating the link fails.
-
-Overwrites the  if it exists.
+creating the link fails.  It can be useful for handling situations such as
+ and  being on different drives or mount points,
+which would make them unable to support a hard link.
 
 Path Conversion
 ^^^

---

Summary of changes:
 Help/command/file.rst | 46 +++---
 1 file changed, 23 insertions(+), 23 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
https://cmake.org/mailman/listinfo/cmake-commits

Re: [CMake] fixup-bundle usability

2019-02-18 Thread Francis Giraldeau

You are right, the fixup bundle is difficult to use. Here are some
undocumented tips:

Put the install(CODE) with the fixup_bundle() call in a CMakeLists.txt in
its own directory. In your main CMakeLists.txt file, add this directory
with add_subdirectory() last. This install(CODE) will run after all the
other install directive, otherwise the fixup_bundle() might run before
other targets are installed.

The main thing is to build the library path variable. Yes, this information
can be recovered from the target itself, but fixup_bundle() won't gather
that info for you. Here is an example with Qt:

get_target_property(QT_CORE_LIB Qt5::Core LOCATION)

get_filename_component(QT_RUNTIME_DIR "${QT_CORE_LIB}" DIRECTORY)

list(APPEND LIBS_PATH "${QT_RUNTIME_DIR}")


If you are using VTK, there is already a variable:

list(APPEND LIBS_PATH "${VTK_RUNTIME_LIBRARY_DIRS}")


You might as well run windeployqt (and similar tool for other platforms)
inside install(CODE) script if you have a Qt app, such that the styles and
the plugins and other stuff gets copied.

execute_process(COMMAND windeployqt.exe --release \"\${MAIN_APP}\")


Workaround wrong tool detection using MinGW on Windows:

if(WIN32 AND NOT MSVC)

  set(GP_TOOL "objdump")

endif()


install(CODE "\

...

  include(BundleUtilities)

  set(gp_tool \"${GP_TOOL}\")

  fixup_bundle(\"\${MAIN_APP}\" \"\" \"${LIBS_PATH}\")

...


And there is the escaping... You have to escape quotes inside
the script. Escape the '$' sign if you want to refer to the
variable at install time. Remember that you don't have access

to configure-time variables at install time. Unescaped '$' prefix

will be replaced by its value at configure time, somewhat like

a macro or a template.


To see the generated script, look into ${CMAKE_BINARY_DIR} with

the directory name corresponding to the CMakeLists.txt containing

the install(CODE). Example:


${CMAKE_SOURCE_DIR}/cmake/bundle/CMakeLists.txt

-> ${CMAKE_BINARY_DIR}/cmake/bundle/cmake_install.cmake


You can check the generated script, its very

handy when things go wrong.


Also, it is easier to put all libraries and binaries in their

own directory. I have this near the begining of my project's

CMakeLists.


set(CMAKE_ARCHIVE_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/lib)

set(CMAKE_LIBRARY_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/lib)

set(CMAKE_RUNTIME_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/bin)


If you have some library that you don't want in your bundle,

you might want to disable install for it, for instance,

google test:


add_subdirectory(3rdparty/googletest/ EXCLUDE_FROM_ALL)


I'm using "ntldd.exe -R" on Windows to check the dependencies manually

(its very much like ldd on Linux). It is much more handy than

dependency walker.


Fixup_bundle is not magical either. The library dependencies must be

known beforehand. It means that if you do some dlopen() tricks at

runtime, fixup_bundle() cannot know that and you will have to install

these libraries manually yourself. One notable example of this is

Intel MKL using the Single Dynamic Library (mkl_rt). Using this

library entry point simplifies the linking and will load the

best library at runtime depending on the hardware. Fixup_bundle() will

copy only mkl_rt and you have to copy the other mkl libraries to

avoid runtime error.


Fixup bundle is tricky to put in place, but having a fixed list

of libraries to copy is even more cumbersome and flaky. When

supplied with the proper directories, the bundle is right every time.


Francis


Le sam. 16 févr. 2019 à 04:04, Andreas Naumann  a
écrit :

> Dear CMakers,
>
> recently I tried to bundle an application in Windows. From the
> documentation [1] I see that I should provide the directories to the
> non-system libraries.
>
> But these information should be already in the properties of the
> targets, arent they? Is there any extension in cmake, that provides
> these paths?
>
> How do other users handle dependencies to external dlls?
>
>
> [1] https://cmake.org/cmake/help/v3.0/module/BundleUtilities.html
>
> Regards,
> Andreas
>
> --
>
> 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 offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> https://cmake.org/mailman/listinfo/cmake
>
-- 
Francis Giraldeau
-- 

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 offering, please visit:

CMake

[Cmake-commits] CMake branch, master, updated. v3.14.0-rc2-114-g0923246

2019-02-18 Thread Kitware Robot via Cmake-commits

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  0923246b2e2fb5be0d2fa1b256879a326aeee13b (commit)
   via  afb325018ebe7c41933b652732a43e4bb4777588 (commit)
  from  bafd0ffa987bea9216e7722c027478f26d5e8f6a (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=0923246b2e2fb5be0d2fa1b256879a326aeee13b
commit 0923246b2e2fb5be0d2fa1b256879a326aeee13b
Merge: bafd0ff afb3250
Author: Brad King 
AuthorDate: Mon Feb 18 14:20:01 2019 +
Commit: Kitware Robot 
CommitDate: Mon Feb 18 09:20:16 2019 -0500

Merge topic 'require-xcode-5'

afb325018e Xcode: Require at least Xcode 5

Acked-by: Kitware Robot 
Merge-request: !2975


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=afb325018ebe7c41933b652732a43e4bb4777588
commit afb325018ebe7c41933b652732a43e4bb4777588
Author: Gregor Jasny 
AuthorDate: Sun Feb 10 11:22:38 2019 +0100
Commit: Gregor Jasny 
CommitDate: Sat Feb 16 15:20:39 2019 +0100

Xcode: Require at least Xcode 5

diff --git a/CMakeCPack.cmake b/CMakeCPack.cmake
index dc9f0ba..78e22cc 100644
--- a/CMakeCPack.cmake
+++ b/CMakeCPack.cmake
@@ -102,9 +102,6 @@ if(CMake_INSTALL_COMPONENTS)
   if(WIN32 AND NOT CYGWIN)
   list(APPEND _CPACK_IFW_COMPONENTS_ALL cmcldeps)
   endif()
-  if(APPLE)
-list(APPEND _CPACK_IFW_COMPONENTS_ALL cmakexbuild)
-  endif()
   if(CMAKE_INSTALL_DEFAULT_COMPONENT_NAME)
 set(_CPACK_IFW_COMPONENT_UNSPECIFIED_NAME
   ${CMAKE_INSTALL_DEFAULT_COMPONENT_NAME})
diff --git a/CMakeCPackOptions.cmake.in b/CMakeCPackOptions.cmake.in
index a08c97d..2a4bcc5 100644
--- a/CMakeCPackOptions.cmake.in
+++ b/CMakeCPackOptions.cmake.in
@@ -109,16 +109,6 @@ if(CPACK_GENERATOR MATCHES "IFW")
   set(CPACK_IFW_COMPONENT_CMCLDEPS_VERSION
 "@CMake_IFW_ROOT_COMPONENT_VERSION@")
 
-  set(CPACK_COMPONENT_CMAKEXBUILD_DISPLAY_NAME "cmakexbuild")
-  set(CPACK_COMPONENT_CMAKEXBUILD_DESCRIPTION
-"The \"cmakexbuild\" executable is a wrapper program for \"xcodebuild\"")
-  set(CPACK_COMPONENT_CMAKEXBUILD_REQUIRED TRUE)
-  set(CPACK_COMPONENT_CMAKEXBUILD_GROUP Tools)
-  set(CPACK_IFW_COMPONENT_CMAKEXBUILD_NAME "CMakeXBuild")
-  set(CPACK_IFW_COMPONENT_CMAKEXBUILD_PRIORITY 85)
-  set(CPACK_IFW_COMPONENT_CMAKEXBUILD_VERSION
-"@CMake_IFW_ROOT_COMPONENT_VERSION@")
-
   # Dialogs
   set(CPACK_COMPONENT_GROUP_DIALOGS_DISPLAY_NAME "Interactive Dialogs")
   set(CPACK_COMPONENT_GROUP_DIALOGS_DESCRIPTION
diff --git a/Help/generator/Xcode.rst b/Help/generator/Xcode.rst
index 71430c7..d893ac5 100644
--- a/Help/generator/Xcode.rst
+++ b/Help/generator/Xcode.rst
@@ -3,9 +3,7 @@ Xcode
 
 Generate Xcode project files.
 
-This supports Xcode 3.0 and above.  Support for Xcode versions prior
-to Xcode 5 is deprecated and will be dropped in a future version of
-CMake.
+This supports Xcode 5.0 and above.
 
 Toolset Selection
 ^
diff --git a/Help/release/dev/require-xcode-5.rst 
b/Help/release/dev/require-xcode-5.rst
new file mode 100644
index 000..6cfe96a
--- /dev/null
+++ b/Help/release/dev/require-xcode-5.rst
@@ -0,0 +1,4 @@
+require-xcode-5
+---
+
+* The :generator:`Xcode` generator now requires at least Xcode 5.
diff --git a/Help/variable/CMAKE_MAKE_PROGRAM.rst 
b/Help/variable/CMAKE_MAKE_PROGRAM.rst
index 4f5a50f..56df2df 100644
--- a/Help/variable/CMAKE_MAKE_PROGRAM.rst
+++ b/Help/variable/CMAKE_MAKE_PROGRAM.rst
@@ -19,15 +19,11 @@ to configure the project:
   This generator stores ``CMAKE_MAKE_PROGRAM`` in the CMake cache
   so that it may be edited by the user.
 
-* The :generator:`Xcode` generator sets this to ``xcodebuild`` (or possibly an
-  otherwise undocumented ``cmakexbuild`` wrapper implementing some
-  workarounds).
+* The :generator:`Xcode` generator sets this to ``xcodebuild``.
 
   This generator prefers to lookup the build tool at build time
   rather than to store ``CMAKE_MAKE_PROGRAM`` in the CMake cache
-  ahead of time.  This is because ``xcodebuild`` is easy to find,
-  the ``cmakexbuild`` wrapper is needed only for older Xcode versions,
-  and the path to ``cmakexbuild`` may be outdated if CMake itself moves.
+  ahead of time.  This is because ``xcodebuild`` is easy to find.
 
   For compatibility with versions of CMake prior to 3.2, if
   a user or project explicitly adds ``CMAKE_MAKE_PROGRAM`` to
diff --git a/Source/CMakeLists.txt b/Source/CMakeLists.txt
index 1c06052..663d42e 100644
--- a/Source/CMakeLists.txt
+++ b/Source/CMakeLists.txt
@@ -1060,9 +1060,6 @@ if(CPACK_ENABLE_FREEBSD_PKG AND FREEBSD_PKG_INCLUDE_DIRS 
AND FREEBSD_PKG_LIBRARI
 endif()
 
 if(APPLE)
-  add_executable(cmakexbuild

[Cmake-commits] CMake branch, release, updated. v3.14.0-rc2-5-g1f8ed41

2019-02-18 Thread Kitware Robot via Cmake-commits

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  1f8ed4141979ee4e2f2cc6aab8ad31a4942bd056 (commit)
   via  36323162cb1229148cdb8085f282d93f9c8ab244 (commit)
   via  f2072a6554a8ec7969460509f3d05c07680c1f18 (commit)
   via  f2820bce1560ab2ca0c991f16aa5cf5dcfb3d88f (commit)
   via  2cc145928c3f024b99f7af574316caf79768b96c (commit)
  from  e6897c72e7c59f7a0b82ed19c1bdb40d42f7adaa (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
---

Summary of changes:
 Help/command/get_filename_component.rst | 7 +++
 Help/release/3.14.rst   | 2 +-
 Modules/ExternalProject.cmake   | 3 ++-
 3 files changed, 6 insertions(+), 6 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
https://cmake.org/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, master, updated. v3.14.0-rc2-112-gbafd0ff

2019-02-18 Thread Kitware Robot via Cmake-commits

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  bafd0ffa987bea9216e7722c027478f26d5e8f6a (commit)
   via  0f2eb9ac6fff686c999c3058a76ec398c054bc0b (commit)
   via  786edf9ab408c35384a081d9f33ec048b4060f1f (commit)
   via  1f8ed4141979ee4e2f2cc6aab8ad31a4942bd056 (commit)
   via  36323162cb1229148cdb8085f282d93f9c8ab244 (commit)
   via  03e10384ecb779ba6e02028d6833c5e8cd3541c5 (commit)
   via  d2489f2fde0adad51272b83e44957860f7b4c57f (commit)
   via  f2072a6554a8ec7969460509f3d05c07680c1f18 (commit)
   via  f2820bce1560ab2ca0c991f16aa5cf5dcfb3d88f (commit)
   via  2cc145928c3f024b99f7af574316caf79768b96c (commit)
   via  ae5e97a00568d15dedea073b58668e646e3c0d2e (commit)
   via  91344e7a46a9c6a2d20781d889673143bd74d15a (commit)
  from  f1235fd37d101d021ffa2dde1c67f0ea1cf1cc87 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=bafd0ffa987bea9216e7722c027478f26d5e8f6a
commit bafd0ffa987bea9216e7722c027478f26d5e8f6a
Merge: 0f2eb9a 1f8ed41
Author: Brad King 
AuthorDate: Mon Feb 18 09:11:21 2019 -0500
Commit: Brad King 
CommitDate: Mon Feb 18 09:11:21 2019 -0500

Merge branch 'release-3.14'


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=0f2eb9ac6fff686c999c3058a76ec398c054bc0b
commit 0f2eb9ac6fff686c999c3058a76ec398c054bc0b
Merge: 786edf9 2cc1459
Author: Brad King 
AuthorDate: Mon Feb 18 14:08:59 2019 +
Commit: Kitware Robot 
CommitDate: Mon Feb 18 09:09:55 2019 -0500

Merge topic 'get_filename_component_docs'

2cc145928c Help: Remove outdated statement about get_filename_component()

Acked-by: Kitware Robot 
Merge-request: !2973


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=786edf9ab408c35384a081d9f33ec048b4060f1f
commit 786edf9ab408c35384a081d9f33ec048b4060f1f
Merge: 03e1038 f2072a6
Author: Brad King 
AuthorDate: Mon Feb 18 14:08:55 2019 +
Commit: Kitware Robot 
CommitDate: Mon Feb 18 09:09:02 2019 -0500

Merge topic 'externalproject_docs'

f2072a6554 Help: Clarify ExternalProject_Add()'s LOG_MERGED_STDOUTERR 
behavior
f2820bce15 Release notes: Make ExternalProject dot points consistent

Acked-by: Kitware Robot 
Merge-request: !2978


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=03e10384ecb779ba6e02028d6833c5e8cd3541c5
commit 03e10384ecb779ba6e02028d6833c5e8cd3541c5
Merge: d2489f2 ae5e97a
Author: Brad King 
AuthorDate: Mon Feb 18 14:04:51 2019 +
Commit: Kitware Robot 
CommitDate: Mon Feb 18 09:05:30 2019 -0500

Merge topic 'delete_copy_assign'

ae5e97a005 Delete some default constructors and assignment operators

Acked-by: Kitware Robot 
Merge-request: !2968


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=d2489f2fde0adad51272b83e44957860f7b4c57f
commit d2489f2fde0adad51272b83e44957860f7b4c57f
Merge: f1235fd 91344e7
Author: Brad King 
AuthorDate: Mon Feb 18 14:04:41 2019 +
Commit: Kitware Robot 
CommitDate: Mon Feb 18 09:04:47 2019 -0500

Merge topic 'autogen_test_fix'

91344e7a46 Autogen: Fix RerunMocPlugin test for Ninja generator

Acked-by: Kitware Robot 
Merge-request: !2971


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ae5e97a00568d15dedea073b58668e646e3c0d2e
commit ae5e97a00568d15dedea073b58668e646e3c0d2e
Author: Albert Astals Cid 
AuthorDate: Thu Feb 14 17:29:57 2019 +0100
Commit: Brad King 
CommitDate: Fri Feb 15 07:25:47 2019 -0500

Delete some default constructors and assignment operators

They are unused, but if someone used them they would lead to
problems since they would copy the internal raw pointers
and the destructor would cause double delete

diff --git a/Source/CPack/cmCPackGeneratorFactory.h 
b/Source/CPack/cmCPackGeneratorFactory.h
index 7f633e4..972f0f7 100644
--- a/Source/CPack/cmCPackGeneratorFactory.h
+++ b/Source/CPack/cmCPackGeneratorFactory.h
@@ -22,6 +22,9 @@ public:
   cmCPackGeneratorFactory();
   ~cmCPackGeneratorFactory();
 
+  cmCPackGeneratorFactory(const cmCPackGeneratorFactory&) = delete;
+  cmCPackGeneratorFactory& operator=(const cmCPackGeneratorFactory&) = delete;
+
   //! Get the generator
   cmCPackGenerator* NewGenerator(const std::string& name);
   void DeleteGenerator(cmCPackGenerator* gen);
diff --git a/Source/CPack/cmCPackLog.h b/Source/CPack/cmCPackLog.h
index 8e99221..65281e3 100644
--- a/Source/CPack/cmCPackLog.h
+++ b/Source/CPack/cmCPackLog.h
@@ -26,6 +26,9 @@ public:
   cmCPackLog();
   ~cmCPackLog();
 
+  cmCPackLog(const cmCPackLog&) = delete;
+  cmCPackLog& operator=(const cmCPackLog&) =

[CMake] Question about set

2019-02-18 Thread workbe...@gmx.at


Hi everyone,

i've looked the web but found no result. I need a string variable that 
allows only certain values, like bool variables only allow true/false my 
string should be either "A" or "B" ...



best regards!

--

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 offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Problems with EnternalProjectAdd

Re: [CMake] Problems with EnternalProjectAdd

Re: [CMake] Problems with EnternalProjectAdd

Re: [CMake] Problems with EnternalProjectAdd

Re: [CMake] Problems with EnternalProjectAdd

Re: [CMake] Problems with EnternalProjectAdd

[Cmake-commits] CMake branch, master, updated. v3.14.0-rc2-119-g2a1f661

[CMake] Problems with EnternalProjectAdd

Re: [CMake] Question about set

[cmake-developers] Using CMake as a package manager vs using a dedicated package management tool (like Conan)

[CMake] Using CMake as a package manager vs using a dedicated package management tool (like Conan)

[cmake-developers] Dead CMake Redesign Projects

Re: [CMake] Question about set

Re: [CMake] Question about functions

[CMake] Question about functions

Re: [CMake] Question about set

Re: [CMake] fixup-bundle usability

Re: [CMake] Question about set

Re: [CMake] Question about set

Re: [CMake] Fwd: Re: Question about CMAKE_MODULE_PATH

Re: [CMake] Fwd: Re: Question about CMAKE_MODULE_PATH

Re: [CMake] Fwd: Re: Question about CMAKE_MODULE_PATH

Re: [CMake] Fwd: Re: Question about CMAKE_MODULE_PATH

[CMake] Fwd: Re: Question about CMAKE_MODULE_PATH

Re: [CMake] Question about CMAKE_MODULE_PATH

Re: [CMake] Question about CMAKE_MODULE_PATH

[CMake] Question about CMAKE_MODULE_PATH

[Cmake-commits] CMake branch, release, updated. v3.14.0-rc2-7-g926a97e

[Cmake-commits] CMake branch, master, updated. v3.14.0-rc2-118-g75b4595

[Cmake-commits] CMake branch, master, updated. v3.14.0-rc2-116-g566652b

Re: [CMake] fixup-bundle usability

[Cmake-commits] CMake branch, master, updated. v3.14.0-rc2-114-g0923246

[Cmake-commits] CMake branch, release, updated. v3.14.0-rc2-5-g1f8ed41

[Cmake-commits] CMake branch, master, updated. v3.14.0-rc2-112-gbafd0ff

[CMake] Question about set

35 matches

Site Navigation

Mail list logo

Footer information