[Cmake-commits] CMake branch, next, updated. v3.2.3-1516-g03230b4

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

[CMake] [ANNOUNCE] CMake 3.3.0-rc1 is now ready!

I am proud to announce the first CMake 3.3 release candidate. Sources and binaries are available at: http://www.cmake.org/download/ Documentation is available at: http://www.cmake.org/cmake/help/v3.3 Release notes appear below and are also published at

[cmake-developers] [ANNOUNCE] CMake 3.3.0-rc1 is now ready!

I am proud to announce the first CMake 3.3 release candidate. Sources and binaries are available at: http://www.cmake.org/download/ Documentation is available at: http://www.cmake.org/cmake/help/v3.3 Release notes appear below and are also published at

[Cmake-commits] CMake branch, master, updated. v3.2.3-1429-g092f153

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

[Cmake-commits] CMake annotated tag, v3.3.0-rc1, created. v3.3.0-rc1

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 annotated tag, v3.3.0-rc1 has been created at 873e8d31d4227bb8b24b34cd7cfc12eefc6bc31a (tag) tagging

Re: [CMake] [ANNOUNCE] CMake 3.3.0-rc1 is now ready!

On Fri, Jun 5, 2015 at 9:03 AM, Robert Maynard robert.mayn...@kitware.com wrote: ... * The Visual Studio 7 generator (.NET 2002) is now deprecated and will be removed in a future version of CMake. * The Visual Studio 6 generator is now deprecated and will be removed in a future version

[Cmake-commits] CMake branch, next, updated. v3.3.0-rc1-133-g24bc47b

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

[CMake] add_custom_command and visual c++ only running first command?

I was using add_custom_command to execute three commands, triggering that rule with add_custom_target, and it worked great with make and ninja on linux and mac. Over on Windows, though, with visual c++ 2013 and cmake 3.0.1, only the first of the three commands was executed. After much

Re: [CMake] Eclipse .cproject Preprocessor Macro Definitions

Am Donnerstag, 4. Juni 2015, 15:53:11 schrieb Ette, Anthony: Ok I've got this installed but can't get it to work. I've selected the Please discuss this on the appropriate mailing list. https://groups.google.com/forum/#!forum/cmake4eclipse-users Martin -- Cd wrttn wtht vwls s mch trsr.

[CMake] Errors trying to cross-compile Icinga2, which uses CMake

Hello, CMake users. I'm running into an error trying to cross-compile Icinga2 for OpenWRT. The root of this issue is that there are helper programs compiled to help complete the compilation (I believe these are called generators). I have understood that I can compile on my native system, then

Re: [CMake] undefined reference to error when use c extension

Or make c++ wrappers that use dlopen/dlsym or loadlibrary/getprocaddress as appropriate and reference the libs through an interface class. On Fri, Jun 5, 2015 at 7:44 PM, J Decker d3c...@gmail.com wrote: it's not the lib, it's the header interface to the lib. On Fri, Jun 5, 2015 at 7:42 PM,

Re: [CMake] undefined reference to error when use c extension

Thanks for your reply. I am aware of extern C {} but this is not an option for me. As I mentioned, there are a lot of lib files (which were not written by me) and I was wondering if lib itself could be untouched. On 06/05/2015 07:33 PM, J Decker wrote: c++ does name mangling on functions... so

Re: [CMake] undefined reference to error when use c extension

c++ does name mangling on functions... so functions like 'f' become a much more complex name (as shown in the xxx not found in your error messages). In order for C++ to not produce a mangled name C functions have to be defined as extern c void f( void ); but 'extern c' is not liked by C... so you

Re: [CMake] undefined reference to error when use c extension

If you are including the .h file for the .c file in your .cpp file and it doesn't already have extern C in it, wrapping it like this when including it in your cpp should help: extern C { #include header.h } Sent from my Verizon Wireless 4G LTE smartphone Original message

Re: [CMake] undefined reference to error when use c extension

it's not the lib, it's the header interface to the lib. On Fri, Jun 5, 2015 at 7:42 PM, Sunrise helios.cor...@gmail.com wrote: Thanks for your reply. I am aware of extern C {} but this is not an option for me. As I mentioned, there are a lot of lib files (which were not written by me) and I