Re: [CMake] Finding 32bit libs on 64bit Ubuntu install

On 2016-04-22 14:59-0400 Nick Deubert wrote: Hey everyone, I am trying to build and link some 32bit binaries on Ubuntu 15.10 64bit, but no matter what combination of arguments I give FIND_LIBRARY I cannot get it to use the 32bit libs. I have been scouring the mailing lists and came up with all

Re: [CMake] Using Clang + Ninja on Windows?

On 4/22/2016 4:51 AM, Mueller-Roemer, Johannes Sebastian wrote: It is true that there is no official bundled installer with both, but the official installer works just fine with mingw as long as you pass in the correct target to clang(++) For example clang++ --target=x86_64-w64-mingw32

Re: [CMake] Using Clang + Ninja on Windows?

On Fri, Apr 22, 2016 at 8:59 AM, Mueller-Roemer, Johannes Sebastian < johannes.sebastian.mueller-roe...@igd.fraunhofer.de> wrote: > You are mistaken, Clang absolutely also works with MinGW. Or it did at > least up to 3.7 (didn’t get around to trying 3.8 yet) > > > Clang works fine with libstdc++

Re: [CMake] Using Clang + Ninja on Windows?

It is true that there is no official bundled installer with both, but the official installer works just fine with mingw as long as you pass in the correct target to clang(++) For example clang++ --target=x86_64-w64-mingw32 test.cpp However, it assumes that mingw64 is installed under C:/mingw64

Re: [CMake] Using Clang + Ninja on Windows?

You are mistaken, Clang absolutely also works with MinGW. Or it did at least up to 3.7 (didn’t get around to trying 3.8 yet) From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Cristian Adam Sent: Thursday, April 21, 2016 23:30 To: Johan Holmberg Cc: cmake@cmake.org

Re: [CMake] CMake:question of the time when the command will happen in add_custom_command(...)

Hi, the reason is that the post-build command is actually a part of building "main the target." Once you introduce custom commands into a target, building it includes them all, and not just compiling the object files and linking the binary. You will notice that the "Linking C exectuable main"

Re: [CMake] CMake:question of the time when the command will happen in add_custom_command(...)

No, it is indeed compiled and linked just fine. What I meant is: Without any custom commands, the build process conceptually looks like this: buildMain() { compile_object_files(); link_main_binary(); message("Built target main"); } With a post-build custom command: buildMain() {

Re: [CMake] CMake:question of the time when the command will happen in add_custom_command(...)

Sorry for i just know reply by email and thinks for your help again. :-) Petr Kmoch wrote > No, it is indeed compiled and linked just fine. What I meant is: > > Without any custom commands, the build process conceptually looks like > this: > > buildMain() { > compile_object_files(); >

Re: [CMake] How to check if Eclipse CDT4 generated project is set up correctly?

Hi Alex, thanks for the details. I managed to add the header files as intended and do have the targets you described, but the virtual directories "CMake Rules", "Object Files" and "Ressources" of each Target subdirectory are still empty. What is the intention of these virtual directories?

Re: [CMake] CMake:question of the time when the command will happen in add_custom_command(...)

Hi Chao, You can see this more clearly if you do a "make VERBOSE=1" : [chuck.atkins@hal9000 build]$ make VERBOSE=1 ... [ 50%] Building C object CMakeFiles/main.dir/main.c.o /usr/bin/cc -o CMakeFiles/main.dir/main.c.o -c /home/chuck.atkins/Code/tmp/source/main.c [100%] Linking C executable

Re: [CMake] How to check if Eclipse CDT4 generated project is set up correctly?

Am Freitag, 22. April 2016, 13:28:33 schrieb Nils Rathmann: > Hi Alex, > thanks for the details. I managed to add the header files as intended > and do have the targets you described, but the virtual directories > "CMake Rules", "Object Files" and "Ressources" of each Target > subdirectory are

[CMake] Finding 32bit libs on 64bit Ubuntu install

Hey everyone, I am trying to build and link some 32bit binaries on Ubuntu 15.10 64bit, but no matter what combination of arguments I give FIND_LIBRARY I cannot get it to use the 32bit libs. I have been scouring the mailing lists and came up with all these things to try but nothing has worked so

Re: [cmake-developers] CMake API for warnings

On 22-Apr-16 20:36, Brad King wrote: On 04/20/2016 09:50 AM, Ruslan Baratov wrote: 1) add_compile_warnings * similar to add_definitions, add_compile_options * modify COMPILE_WARNINGS directory property (append) 2) target_compile_warnings * similar to target_compile_options,

[Cmake-commits] CMake branch, master, updated. v3.5.2-506-g38d1c67

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

[cmake-developers] [CMake 0016075]: Play jeopardy theme during compilation

The following issue has been SUBMITTED. == https://cmake.org/Bug/view.php?id=16075 == Reported By:Richard Wiedenhöft Assigned To:

[Cmake-commits] CMake branch, next, updated. v3.5.2-1066-gb58bed8

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

[Cmake-commits] CMake branch, master, updated. v3.5.2-501-g76e793b

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

[Cmake-commits] CMake branch, master, updated. v3.5.2-505-geadc6db

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

Re: [cmake-developers] Autogen subdirectories patches

On 04/21/2016 03:14 AM, Sebastian Holtermann wrote: >> Thanks! I've applied them locally and merged the cleanup/refactoring >> commits to 'next' for testing first. Once those test cleanly I'll move >> on to the rest. > > It is good too see the patches made it into the next branch. The rest of

[Cmake-commits] CMake branch, next, updated. v3.5.2-1076-g824dc08

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

[Cmake-commits] CMake branch, next, updated. v3.5.2-1069-g3cd8011

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

[Cmake-commits] CMake branch, master, updated. v3.5.2-488-ge5a9a43

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

[Cmake-commits] CMake branch, master, updated. v3.5.2-493-geb87407

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

Re: [cmake-developers] CMake API for warnings

On 04/20/2016 09:50 AM, Ruslan Baratov wrote: > 1) add_compile_warnings >* similar to add_definitions, add_compile_options >* modify COMPILE_WARNINGS directory property (append) > 2) target_compile_warnings >* similar to target_compile_options, target_compile_definitions >* modify

[cmake-developers] [CMake 0016076]: bin install directory configuration

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

[cmake-developers] [CMake 0016077]: FindProtobuf.cmake doesn't have required flexibility to configure protoc usage for all use cases

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