Re: [CMake] find_library

Hi Vania, find_library(SYSC_LIB systemc PATHS "${SYSTEMC_PATH}" > PATH_SUFFIXES lib-linux64 lib64-linux lib64-linux64) > In this first call, SYSTEMC_PATH is being dereferenced as a CMake variable. This works because in your invocation of CMake: cmake -G "Unix Makefiles"

Re: [cmake-developers] CMake alternative language

I think this problem already exists. When "projects build elaborate macro/function systems in the CMake language", you have to understand the build system program. And in my experience, those systems are widely different from one another. I have seen a system where you defined lots of variables,

Re: [CMake] Update/Set _expectedTargets inside exports-release.cmake.

Hello Stephen, On Tue, Jan 12, 2016 at 8:58 PM, Stephen Kelly wrote: > Rashad Kanavath wrote: > > > I am having this when I build packages for debian where I split > components > > into separate packages project1-core, project1-gui etc.. > > I think you need to patch the

Re: [CMake] using macros

Hi Owen. As a sanity check, the definition of the macro in the toplevel CMakeList comes *before* the add_subdirectory() command for the one which errors out, right? Petr On Thu, Jan 14, 2016 at 8:25 AM, Owen Hogarth II wrote: > I am trying to use a macro to enable c99 in

[CMake] find_library

I am running cmake 3.2.2 on Linux 64 bits I run cmake with cmake -G "Unix Makefiles" -DSYSTEMC_PATH=$HOME/systemc-2.3.1/ In my CMakeLists.txt, If I put find_library(SYSC_LIB systemc PATHS "${SYSTEMC_PATH}" PATH_SUFFIXES lib-linux64 lib64-linux lib64-linux64) it works. If I

Re: [CMake] find_library

Defining a variable using -D option does not put this one in the environment (i.e. system environment) so using ENV will fails... On 14/01/16 10:28, "CMake on behalf of Vania Joloboff" wrote: >I am running cmake 3.2.2 on Linux

[CMake] Fwd: FILE(UPLOAD) doesn't seem to respect custom CA settings while DOWNLOAD does

Hello, I'm trying to get CMake to talk to an SSL server using a self-signed certificate. It works just fine with downloads. The certificate path appears in the LOG: successfully set certificate verify locations: CAfile: /path/to/my/certificate.pem CApath: /etc/ssl/certs and the TLS

Re: [cmake-developers] CMake alternative language

On Wed, Jan 13, 2016 at 10:21 PM, Alexander Neundorf wrote: > > My personal opinion: if the full power of python would be available, the > build > scripts would quickly turn into real programs, because programmers would be > tempted to do so if all of python would be available.

Re: [cmake-developers] CMake alternative language

As long as CMake embeds everything that is required, I don't see the additional pain (since this is what it already does with the CMake language). Le jeu. 14 janv. 2016 à 13:35, Jean-Michaël Celerier < jeanmichael.celer...@gmail.com> a écrit : > > On Wed, Jan 13, 2016 at 10:21 PM, Alexander

Re: [cmake-developers] CMake alternative language

I am hesitant to add more fuel to the fire for this discussion because it has been discussed many times before through the years and my sense is that this isn’t what Brad is really interested in pursuing. I encourage you search the mailing list history. I’ll try to summarize (off the top of my

Re: [cmake-developers] fixup_bundle with @loader_path

On 01/13/2016 01:38 AM, Simon Wells wrote: > it kept saying that @loader_path/libboost_chrono-mt.dylib was not found It looks like this was now reported here with a patch: https://cmake.org/Bug/view.php?id=15918 We already handle @executable_path, so @loader_path should be handled in a similar

Re: [cmake-developers] CMake alternative language

Maybe just implement the python syntax (or a t lease a subset) in the cmake core , so no need extern dep and provide a clean/defined interface to be able to call complex external script is whatever languages. 2016-01-13 14:27 GMT+01:00 Saša Janiška : > On Sri, 2016-01-13 at

Re: [cmake-developers] CMake alternative language

Thanks for the insight ! I started going towards python because I am more familiar with it, but Lua seems to be a better fit for CMake now that I think about the constraints you listed. The main point I am getting from your mail is that Kitware may not want to go down this route, even if

[Cmake-commits] CMake branch, next, updated. v3.4.1-1958-ge584aa9

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, next has been updated via e584aa916a85ec45a19e751e2c224b97231ff02e (commit) via

Re: [CMake] finding if feature is supported by host

Hi Vania. A quick look a CMake docs will show you CMake's try_compile() command: https://cmake.org/cmake/help/latest/command/try_compile.html (There is also a try_run(), if required). I believe that's precisely what you want. Petr On Thu, Jan 14, 2016 at 5:44 PM, Vania Joloboff

[Cmake-commits] CMake branch, master, updated. v3.4.1-837-g6e1a3df

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 6e1a3df0c7d570ae560fc39fae17de839fe2f3e6 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.4.1-835-g9cf6388

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 9cf63886985f39bb364e620e4459252b9ba8072a (commit) via

[Cmake-commits] CMake branch, master, updated. v3.4.1-839-gf3fd50a

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 f3fd50ad4b4252c42de55657074ca0b84f97a83c (commit) via

[Cmake-commits] CMake branch, next, updated. v3.4.1-1963-g358f772

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, next has been updated via 358f7727f9b30ab91b65905ed7812e216b172466 (commit) via

Re: [cmake-developers] Git for windows patch

Hi, Shawn! I am using CMake and Git on the Windows. As an IDE I use Qt Creator. My experience is that on Windows you need to use: "C:\Program Files [(x86)]\Git\cmd\git.exe" If you use your proposed way, I'm having problems work with Git in my project. It seems to me that this decision is

Re: [cmake-developers] CMake alternative language

The problem is doing : list(LENGTH MyList NumList) math(EXPR MaxItList ${NumList}-1) foreach(i RANGE ${MaxItList}) list(GET MyOtherListOfSameSizeThanMyList ${i} Element) foobazify(${Element}) endforeach() instead of : for i in range(0, MyList.size):

Re: [cmake-developers] CMake alternative language

On Thu, Jan 14, 2016 at 3:09 PM, Jean-Michaël Celerier wrote: > The problem is doing : > > list(LENGTH MyList NumList) > math(EXPR MaxItList ${NumList}-1) > > foreach(i RANGE ${MaxItList}) > list(GET MyOtherListOfSameSizeThanMyList ${i} Element)

Re: [cmake-developers] [Qt-creator] CMake daemon for user tools

Brad King wrote: > I think the responses in this thread have indicated there is interest > in working toward the full daemon approach. Perhaps discussion should > now proceed on the daemon protocol design over in the thread Tobias > started on cmake-developers: > > cmake daemon mode protocol >

Re: [cmake-developers] cmake daemon mode protocol

Tobias Hunger wrote: > Hi Stephen, > > I have successfully build and run your cmake server mode changes and > the python client script does work as advertised. Thanks for doing that! > I do have a couple of remarks about it. This is more intended as a > starting point for discussion as a real

[cmake-developers] Git for windows patch

Hi, Recently I had to build a project on windows whose build required git. And even though I had installed git from here [1] in the default location, I had to tell CMake where to find it every time I did a build in a clean build tree. So here is a patch that tells CMake to look in the default

[Cmake-commits] CMake branch, next, updated. v3.4.1-1967-g24fcf2e

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, next has been updated via 24fcf2ef037e50eb375f8e0d5e49a7658273f230 (commit) via

Re: [cmake-developers] fixup_bundle with @loader_path

- On Jan 14, 2016, at 6:48 AM, Brad King brad.k...@kitware.com wrote: > On 01/13/2016 01:38 AM, Simon Wells wrote: >> it kept saying that @loader_path/libboost_chrono-mt.dylib was not found > > It looks like this was now reported here with a patch: > >

[CMake] Interesting behavior of MAIN_DEPENDENCY in makefiles

Say you have a simple cpp file: cat > test.cpp int main() { return 0; } Then you have this as your CMakeLists.txt file: set(input_file test.cpp) set(generated_file ${CMAKE_CURRENT_BINARY_DIR}/${input_file}.blah${CMAKE_CXX_OUTPUT_EXTENSION}) add_custom_command( OUTPUT ${generated_file}

[CMake] Last Call for Papers: GCIRE2016 - Philippines

The Second International Conference on Green Computing, Intelligent and Renewable Energies (GCIRE2016) University of Perpetual Help System DALTA Las Piñas-Manila, Philippines February 24-26, 2016 http://sdiwc.net/conferences/gcire2016/ gcir...@sdiwc.net ===

[Cmake-commits] CMake branch, master, updated. v3.4.1-847-gb8d002a

_VERSION_MINOR 4) -set(CMake_VERSION_PATCH 20160114) +set(CMake_VERSION_PATCH 20160115) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

Re: [cmake-developers] CMake alternative language

Charles Huet wrote: > When the configure step takes > about 30 seconds, and all you can do is use MESSAGE() to find what > happens, this is no walk in the park. A real debugger would do a world of > good to CMake. This is one of the things that I address with the daemon work - a 'recording' is

Re: [CMake] Changing the the current generator in CMake GUI

I was able to edit CMakeCache.txt and CPackConfig.cmake (with CMake GUI closed) I changed CMAKE_GENERATOR:INTERNAL=Visual Studio 10 2010 Win64 to CMAKE_GENERATOR:INTERNAL=Visual Studio 10 2010 and then in general looked for the string "64" and made appropriate changes. I then started CMake

[cmake-developers] install(EXPORT) with PRIVATE dependency: possible bug

It seems that the names of the PRIVATE dependencies of a library are not affected by either the NAMESPACE option or the EXPORT_NAME property. A minimal example: add_library(one STATIC ...) add_library(two STATIC ...) target_link_libraries(two PRIVATE one) install(TARGETS one two

Re: [CMake] Changing the the current generator in CMake GUI

On 1/14/2016 3:02 PM, mozzis wrote: I was able to edit CMakeCache.txt and CPackConfig.cmake (with CMake GUI closed) I changed CMAKE_GENERATOR:INTERNAL=Visual Studio 10 2010 Win64 to CMAKE_GENERATOR:INTERNAL=Visual Studio 10 2010 and then in general looked for the string "64" and made

Re: [cmake-developers] Assertion hit in CMake for KDevelop on Ubuntu

On 01/14/2016 03:38 PM, Alexander Neundorf wrote: > On Thursday, January 14, 2016 21:31:51 Kevin Funk wrote: >> +1 from my side, KDevelop 3 is super ancient (last release around 2008 >> according to the interwebs). Get rid off the generator. > > Brad, what's your opinion on this ? > Removing

Re: [cmake-developers] CMake alternative language

Looking at what kind of mistakes the newcomers make, I think it's rather the global workflow and the roles of certain key variables/properties they don't get. At first their problem is not that they can't make a for-loop or increment a variable. It's that they don't understand how the build and

[CMake] How do I create targets first and add sources later?

I often find it more convenient to call add_library() and add_executable() first, apply properties to them etc., and then later add the sources to them with target_sources() (usually in other CMake files via add_subdirectory). Obviously, all my targets will eventually have sources added. However,

[Cmake-commits] CMake branch, next, updated. v3.4.1-1965-g8810997

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, next has been updated via 8810997b9bcabc895f99f0b68e5a96515831189e (commit) via

[Cmake-commits] CMake branch, master, updated. v3.4.1-846-g43a32bd

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 43a32bdff6b452016a9b59224cd83e3c79c58e28 (commit) via

Re: [cmake-developers] Assertion hit in CMake for KDevelop on Ubuntu

On Wednesday, January 13, 2016 10:16:44 PM Alexander Neundorf wrote: > On Wednesday, January 13, 2016 10:16:23 Robert Dailey wrote: > > Running version 3.2.2 on Ubuntu 15. I run the following command: > > > > $ cmake .. -G"KDevelop3" -DCMAKE_C_COMPILER=gcc-4.9 > > -DCMAKE_CXX_COMPILER=g++-4.9

Re: [cmake-developers] Assertion hit in CMake for KDevelop on Ubuntu

On Thursday, January 14, 2016 21:31:51 Kevin Funk wrote: > On Wednesday, January 13, 2016 10:16:44 PM Alexander Neundorf wrote: > > On Wednesday, January 13, 2016 10:16:23 Robert Dailey wrote: > > > Running version 3.2.2 on Ubuntu 15. I run the following command: > > > > > > $ cmake ..

[Cmake-commits] CMake branch, next, updated. v3.4.1-1969-gaea52d2

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, next has been updated via aea52d2033f3e17ba11af70fb6d264e8637a8deb (commit) via

Re: [cmake-developers] Adding Swift support to CMake for Linux/Makefiles

On 01/13/2016 06:17 PM, Eric Wing wrote: > Under the hood, I think the LLVM linker can handle all of these > through ld. But I think the thing that is tripping me up is that Swift > seems to need to link against some additional libraries which are not > needed in the pure C case. The swiftc

[cmake-developers] [CMake 0015919]: Building CUDA files fails when source path contains parenthesis

The following issue has been SUBMITTED. == https://cmake.org/Bug/view.php?id=15919 == Reported By:qiv Assigned To:

[cmake-developers] [CMake 0015920]: Tests fail

The following issue has been SUBMITTED. == https://cmake.org/Bug/view.php?id=15920 == Reported By:R Jones Assigned To:

Re: [cmake-developers] Assertion hit in CMake for KDevelop on Ubuntu

On Wed, Jan 13, 2016 at 3:16 PM, Alexander Neundorf wrote: > On Wednesday, January 13, 2016 10:16:23 Robert Dailey wrote: >> Running version 3.2.2 on Ubuntu 15. I run the following command: >> >> $ cmake .. -G"KDevelop3" -DCMAKE_C_COMPILER=gcc-4.9 >> -DCMAKE_CXX_COMPILER=g++-4.9

[CMake] finding if feature is supported by host

Hi I can find if an include file exists with CHECK_INCLUDE_FILE But I want to know if a particular feature is supported in our case we need to know if the mmap call exists and whether it supports the MAP_ANONYMOUS feature With autoconf, I can use AC_TRY_COMPILE to try compiling a program using

[CMake] cdash/ctest question

Apologies for posting a cdash question question to the cmake list… CDash plots the run-time of tests, which is very useful indeed, but it would be even more useful if one could output a performance related ‘time’ from a test where a specific feature was being benchmarked and one could see how

[CMake] Create both Windows UWP project and old Win32 console project in same solution.

Hello, Is there a way to create both a Windows UWP project and an old Win32 console project in same solution? I have a toolchain file that sets CMAKE_SYSTEM_NAME to WindowsStore in order to create the UWP project, but then any other add_executable call will also create a Windows 10 project. I

Re: [cmake-developers] CMake alternative language

My stumbling blocks are the use of keywords instead of operators... if( Something == ${SomeOtherThing} ) vs if( Something STREQUAL ${SomeOtherTHing} ) It might be nice if the operator '=' could be used in addition to the function SET() SET( a something ) becomes A = something Was gong to say

Re: [CMake] cdash/ctest question

On Thursday, January 14, 2016 21:51:23 Biddiscombe, John A. wrote: > Apologies for posting a cdash question question to the cmake list… > > CDash plots the run-time of tests, which is very useful indeed, but it would > be even more useful if one could output a performance related ‘time’ from a >