[CMake] How to build CMake so it works on an older Linux?

2018-04-04 Thread Eric Wing
I just discovered that CMake no longer builds on my Ubuntu 12.04. I need to build binaries that are compatible with that ABI. I see that your binary distribution of CMake 3.11 still works on Ubuntu 12.04. Can you tell me what you do to achieve this? What are you doing for your official builds?

[CMake] Why isn't target_link_libraries not enough in some cases?

2018-04-04 Thread Saad Khattak
Hi, I am fetching and building SDL2 using FetchContent and then using target_link_libraries(MyExe SDL2) in the hopes that the required include directories and libraries will be added populated properly. The example project can be found here: https://github.com/samaursa/cmake_fetch_content_SDL2

Re: [CMake] How to build CMake so it works on an older Linux?

2018-04-04 Thread Bo Zhou
The latest CMake requires C++11 compiler, so what you need is just a newer GCC which supports C++11 at your platform, that's it. Usually the ABI is not the problem but the libstdc++, you can use a old Ubuntu with old libstdc++ but build CMake with new compiler and make sure it links with old

Re: [CMake] [FYI] clang-3.4 vs cmake-3.11.0 (How to build CMake so it works on an older Linux?)

2018-04-04 Thread Bo Zhou
The emplace() is new API from C++11. Be aware that GCC suite actually is independent from the libstdc++, so if you have a newer compiler, the compiler might still pick the older libstdc++ without the new API. This issue doesn't exist at Windows, since Visual Studio is a complete sytem. This

Re: [CMake] [FYI] clang-3.4 vs cmake-3.11.0 (How to build CMake so it works on an older Linux?)

2018-04-04 Thread suzuki toshiya
Dear Bo Zhou, Thank you for prompt reply. > Be aware that GCC suite actually is independent from the libstdc++, so if you > have a newer compiler, the compiler might still pick the older libstdc++ > without the new API. Oh, so, even if I installed clang-3.4, still it uses older (maybe C++03)

Re: [CMake] [FYI] clang-3.4 vs cmake-3.11.0 (How to build CMake so it works on an older Linux?)

2018-04-04 Thread suzuki toshiya
Sorry for bothering subscribers for posting about C++11 environment instead of cmake itself. Now I understand building gcc >= 4.8.5 manually might be easier, in comparison with the quest of libc++ for clang-3.4. https://stackoverflow.com/questions/39332406/install-libc-on-ubuntu Regards,

Re: [CMake] How to build CMake so it works on an older Linux?

2018-04-04 Thread suzuki toshiya
Dear Bo Zhou, Thank you for the info! Now I'm checking Ubuntu 12.04 in LXC. So, gcc-4.8.5 or later would be needed for C++11, it seems that the last version of gcc officially provided for Ubuntu-12 was 4.7. oh. According to https://clang.llvm.org/cxx_status.html , clang-3.3 supports C++11, and

Re: [CMake] [FYI] clang-3.4 vs cmake-3.11.0 (How to build CMake so it works on an older Linux?)

2018-04-04 Thread suzuki toshiya
Dear Bo Zhou, Sorry, I've confirmed by myself. By default, clang-3.4 for Ubuntu prioritizes old g++ header files, and clang header files are searched as a fallback. I can customize the searching order by -nostdinc++... Regards, mpsuzuki suzuki toshiya wrote: > Dear Bo Zhou, > > Thank you for

[CMake] Overloading/shadowing/redefining CMake intrinsic commands

2018-04-04 Thread Zaak Beekman
I have been moving towards modern CMake where includes/compiler-flags/libraries/etc. are using target properties and transitive usage requirements which has greatly simplified setting up Modern Fortran build systems. In addition, if you're going to vendor all/most of your package's dependencies

Re: [CMake] Overloading/shadowing/redefining CMake intrinsic commands

2018-04-04 Thread Robert Maynard
See https://cmake.org/pipermail/cmake/2011-March/043320.html for a discussion on overloading functions and the dangers that can occur. On Wed, Apr 4, 2018 at 11:38 AM, Zaak Beekman wrote: > I have been moving towards modern CMake where >

[CMake] (no subject)

2018-04-04 Thread Anthony Zukaitis
On windows I found an issue with Visual studio where intel fortran was attempting to preprocess lowercase .f90 files. Intel's documentation states that it does not preprocess these files. Looking into the cmake source code I found: in Modules/Platform/Windows-Intel-Fortran line 3:

Re: [CMake] Overloading/shadowing/redefining CMake intrinsic commands

2018-04-04 Thread Zaak Beekman
Hi Robert, Thanks so much for the speedy response. That is certainly dangerous looking. I'm sure everyone will want to buy me a beer/coffee after I crash their machines during configuration. I almost wish you had responded "impossible" because now I have the temptation of trying it out! Thanks,

[Cmake-commits] CMake branch, master, updated. v3.11.0-409-gaae2bcf

2018-04-04 Thread Kitware Robot
VERSION_MINOR 11) -set(CMake_VERSION_PATCH 20180404) +set(CMake_VERSION_PATCH 20180405) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

Re: [cmake-developers] execute_process on windows uses CreateProcess

2018-04-04 Thread Brad King
On 04/04/2018 03:30 AM, Mathieu Westphal wrote: > Is there a way, using cmake, to start a gui command on windows > and have the gui shows up ? ``` execute_process(COMMAND cmd /c notepad) ``` > If not, is this intended? Yes. Otherwise console windows appear for everything. CreateProcessW is

[Cmake-commits] CMake branch, master, updated. v3.11.0-387-g74005a1

2018-04-04 Thread Kitware Robot
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 74005a136ca0f6ffa1619982d2a4c947335d7254 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.11.0-408-g3201e4c

2018-04-04 Thread Kitware Robot
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 3201e4c156fcf79a7c29a73430e72b1bcd43cedc (commit) via

[Cmake-commits] CMake branch, release, updated. v3.11.0-8-gb1aa90f

2018-04-04 Thread Kitware Robot
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 b1aa90f057985d51773dadfe9e69bac45b061a50 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.11.0-396-g8496d11

2018-04-04 Thread Kitware Robot
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 8496d11ef8a5c4a14a13c7df5e7f214028c35f5c (commit) via

[cmake-developers] Is the "cmake_policy (VERSION 3.11)" statement in the latest UseSWIG.cmake correct?

2018-04-04 Thread Alan W. Irwin
According to , an important side effect of "cmake_policy (VERSION 3.11)" is that no user with cmake version less than 3.11.0 can use the latest version of UseSWIG.cmake. Was that change intended (i.e., does the latest version of

[cmake-developers] execute_process on windows uses CreateProcess

2018-04-04 Thread Mathieu Westphal
Hello CMake developpers. We are using execute_process in some of our tests for a Qt based application (ParaView) However, on windows, the GUI does not show up and that caused some problems for rendering. We have investigated the problem, and it looks like execute_process on windows is based on