Re: [CMake] CMake and a simple java example

Hi, You didn’t specify nothing in variable JAVA_SOURCE_DIRECTORY, so java source path is effectively /HelloWorld.java. By the way, you can specify relative paths to the CMakeLists.txt directory for java sources, so: set(JAVA_SOURCE_FILES HelloWorld.java) add_jar(${JAR_NAME}

Re: [CMake] Problems with transitive dependencies

You are evaluating those properties at the wrong time. Transitive properties are not passed on at configure time (they can’t be), but at generation time. Therefore to debug those values you will have to use generator expressions (except they don’t work for link_libraries). Or just look at the

Re: [CMake] 3.4.1 installer overwrites Windows PATH system var

On 12/04/2015 02:12 AM, Vasily Vladimirovich Vylkov wrote: > Thanks all -- that worked. The key: > regedit.exe --> HKLM\SYSTEM\ControlSet001\Control\Environment\Path > > had a backup of the path var before the CMake install nuked it. > >> How long was your PATH before? > > Just my luck, it

[Cmake-commits] CMake branch, master, updated. v3.4.1-647-g8cc5e2c

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

[Cmake-commits] CMake branch, master, updated. v3.4.1-649-gd9bbc8f

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

[Cmake-commits] CMake branch, master, updated. v3.4.1-651-g128d569

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

[Cmake-commits] CMake branch, master, updated. v3.4.1-639-gc3bb76d

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

[Cmake-commits] CMake branch, master, updated. v3.4.1-637-g335314e

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

[Cmake-commits] CMake branch, next, updated. v3.4.1-1635-g279b421

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

[Cmake-commits] CMake branch, master, updated. v3.4.1-644-g939792f

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

[Cmake-commits] CMake branch, next, updated. v3.4.1-1640-g270a1ae

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

[Cmake-commits] CMake branch, next, updated. v3.4.1-1624-g2dd7af2

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

Re: [CMake] MPI wrappers vs FindMPI

Thanks for the insight Brad. Another advantage may be that the FindMPI module knows about what `mpirun` or `mpiexec` is called, as well as some common flags, like number of ranks to execute. Since OpenCoarrays writes an MPI compiler wrapper script and a script to run the executable, `caf` and

Re: [CMake] Control the build target's external dependencies

Just to answer myself: After looking at the source code, I now understand that the regular expression set by include_regular_expression(...) is not compared against the full path name of the included file, but just what's in the source file after #include. So this machinery is non too useful

[CMake] Making CMake *not* use -isystem at all

Dear All, I'm still debugging the performance problems of our build. But now I bumped into another surprising thing. Our "highest level" packages can depend on a *lot* of low level packages. The one I'm testing now depends on more than 180 of them. This generates >180 -isystem flags for the

Re: [CMake] MPI wrappers vs FindMPI

On 12/04/2015 05:51 PM, Zaak Beekman wrote: > What are the pros and cons of using FindMPI over passing FC=mpif90 and > CC=mpicc? It shouldn't matter much if all the code in the project is meant to be build for MPI. Using plain FindMPI with the CC/CXX/FC set to the system compilers is cleaner

[Cmake-commits] CMake branch, next, updated. v3.4.1-1644-g8890311

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

Re: [cmake-developers] [PATCH] Add support for multiple parameters in cmake -E copy_directory command

On 12/06/2015 02:40 PM, Bartosz Kosiorek wrote: > added support for multiple source directories into copy_directory Thanks. Applied with minor tweaks: cmake: Refine -E chdir documentation https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=0903812b cmake: Refine -E copy_if_different

[cmake-developers] [CMake 0015873]: CMake hangs indefinitely after executing other tools (e.g., gmake, getconf, file)

The following issue has been SUBMITTED. == https://public.kitware.com/Bug/view.php?id=15873 == Reported By:Ralf Mitschke Assigned To:

[CMake] Control the build target's external dependencies

Dear All, I'm struggling since a few days with the following issue. Our development setup is such that we build large software projects in a nightly build system, which puts these projects onto a network drive. The developers then set up these nightly projects, and build their own code against

Re: [CMake] Shared library from sources in several subdirectories

On 12/04/2015 03:05 PM, Bruce Stephens wrote: Any suggestions on how to organise that? Presumably there are lots of examples in (for example) KDE, but I'm not familiar enough with that codebase to be able to find them easily. Currently our GNU Make build builds static libraries in the

Re: [CMake] [CDash] CTEST_CUSTOM_WARNING_EXECPTION

Hello David, It didn't worked. I end up passing -wno-cpp to the cmake flags to finally get over this issue. I don't get how CTEST_CUSTOM_WARNING_EXCEPTION works. How does this compare the regex when it gets a warning? How do I disable all warnings from a directory? eg:

Re: [CMake] Control the build target's external dependencies

Dear All, Maybe I should've google-d better. So now I started experimenting with include_regular_expression(...). https://cmake.org/cmake/help/v3.0/command/include_regular_expression.html But now I'm having a problem with expressing my intent with a regular expression. In principle I'd like

[CMake] Problems with transitive dependencies

Dear CMake users, I'm trying to use CMake to replace the complex hand-built Visual Studio configuration of our open source project, Box Backup. And I'm having trouble making it generate the correct transitive dependencies between modules, particularly for include directories. We have a lot of

[CMake] Set tests to "not-run" in CDash

Hello, We sometimes have tests that are failing and want to disable them temporarily, but still be reminded of them in the CDash dashboard. To accomplish this, we sometimes map the test name to a non existing executable. CTest then can't find the executable and marks the test as "not run" in

Re: [CMake] Making CMake *not* use -isystem at all

On Monday, December 07, 2015 15:39:40 Attila Krasznahorkay wrote: > Dear All, > > I'm still debugging the performance problems of our build. But now I bumped > into another surprising thing. > > Our "highest level" packages can depend on a *lot* of low level packages. > The one I'm testing now

Re: [CMake] Making CMake *not* use -isystem at all

Hi Alex, From what I could see, if the base CMake code decides that internally CMAKE_INCLUDE_SYSTEM_FLAG_CXX needs to be set to “-isystem “, then I can’t influence this decision from the outside. But the reason that the decision between using -I and -isystem seemed so inexplainable to me was

[CMake] CMake and a simple java example

Dear All, I am learning CMake, and one of my personal lessons is combine Java and CMake. I made a small example (HelloWorld.java): == public class HelloWorld { public static void main(String[] args) { System.out.println("Hey :)"); } } == And a CMakeLists.txt

Re: [CMake] Copying directories as post build events without losing parent directory

$ cmake -E copy_directory foo bar/foo ? On Mon, Dec 7, 2015 at 4:53 PM, Robert Dailey wrote: > I have a custom target which runs a command similar to this: > > $ cmake -E copy_directory foo bar > > The problem is that the contents of "foo" are copied inside of "bar",

Re: [CMake] Copying directories as post build events without losing parent directory

On Mon, Dec 7, 2015 at 3:59 PM, David Cole wrote: > $ cmake -E copy_directory foo bar/foo > > ? > > > On Mon, Dec 7, 2015 at 4:53 PM, Robert Dailey > wrote: >> I have a custom target which runs a command similar to this: >> >> $ cmake -E copy_directory

Re: [CMake] Copying directories as post build events without losing parent directory

On Mon, Dec 7, 2015 at 4:15 PM, Robert Dailey wrote: > On Mon, Dec 7, 2015 at 3:59 PM, David Cole wrote: >> $ cmake -E copy_directory foo bar/foo >> >> ? >> >> >> On Mon, Dec 7, 2015 at 4:53 PM, Robert Dailey >> wrote: >>> I

Re: [CMake] Shared library from sources in several subdirectories

On Mon, Dec 7, 2015 at 9:08 AM, Nils Gladitz wrote: > I would avoid creating these single use, per directory libraries entirely. > > Well, creating the static libraries is obviously just an artifact of our current build scheme, so it makes sense to ditch it. Creating

[Cmake-commits] CMake branch, next, updated. v3.4.1-1647-g8b8a03f

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

Re: [cmake-developers] [CPackRPM] Configure RPM package group and name per component

2015-11-17 9:18 GMT+01:00 Domen Vrankar : > 2015-11-15 20:32 GMT+01:00 Markus Rickert : >> Hi, >> >> similar to the previous patch for CPackDeb, the attached patch adds >> component-specific settings for group and name of an RPM package. >> >>

Re: [cmake-developers] Add command line options for deprecation message control

I noticed one glitch. I built against Qt 5.5.1 on Linux and the option dialog seems to truncate the labels. I think I've fixed it, by using vertical layouts rather than form layouts and setting the size policy to expanding for the widgets, if that doesn't fix I'll need to look into QT in more

[CMake] CMake not finding boost headers

I'm stuck on what seems like a rather simple problem. I've got this in my CMakeLists.txt set(BOOST_INCLUDEDIR ${CMAKE_CURRENT_LIST_DIR}/boost_1_59_0) set(Boost_DEBUG 1) find_package(Boost 1.59.0 EXACT REQUIRED) The boost_1_59_0 I'm pointing it to contains the Boost source straight

Re: [CMake] CMake not finding boost headers

It turns out I missed some important information. I am cross compiling, and my toolchain file sets CMAKE_FIND_ROOT_PATH_MODE_INCLUDE to ONLY. If I change ONLY to BOTH, CMake succesfully locates the Boost headers. I'm not sure if this is the correct solution though. Why would setting this to

Re: [CMake] CMake not finding boost headers

The reason is that ONLY really does mean: “only look in the CMAKE_FIND_ROOT_PATH, and don’t look anywhere else”. This can be useful when cross-compiling, as it ensures that you can strictly control the location(s) where system headers are found, and not accidentally find them on the host

[cmake-developers] Static Bootstrap: CCMake & GPM

Hi, I did build a static version of CMake today successfully via LDFLAGS="-static-libstdc++ -static-libgcc -static" \ CFLAGS="-fPIC" \ CXXFLAGS="-fPIC" \ ./bootstrap make -j make install (the -fPIC could also be superfluous, I just realized later that I need to build my gcc via -fPIC,

[Cmake-commits] CMake branch, master, updated. v3.4.1-652-gc6eacfd

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