[CMake] C++/CLI Wrapper with C#

2017-09-20 Thread J. Caleb Wherry
All, I recently upgraded to CMake 3.8 to get support for C# as a first class language and it works nicely. However, I am seeking clarification on something: I currently compile my C++/CLI wrapper as a SHARED lib. This produces a linking lib which I didn't expect and don't want (using the lib

Re: [CMake] VC2015 and Windows 7 compatibility

2017-09-20 Thread Gonzalo Garramuño
El 20/09/2017 a las 04:44, Elvis Stansvik escribió: 2017-09-20 7:53 GMT+02:00 Elvis Stansvik : 2017-09-19 23:22 GMT+02:00 Gonzalo Garramuño : El 19/09/2017 a las 15:19, J Decker escribió: you can just install the runtime redistributuable

Re: [cmake-developers] GCC x cmake

2017-09-20 Thread Petr Kmoch
On Tue, Sep 19, 2017 at 11:34 AM, Ivam Pretti wrote: > I would like to know what are the advantages or difference when compared >> to GCC compiler. >> >> > I understand from the topic you mean compared to cmake; but the two are > two different things > gcc is a compiler >

[Cmake-commits] CMake branch, master, updated. v3.9.3-883-g95df03a

2017-09-20 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 95df03a1d44d48b5407dd0ddc9e618ce2f17762b (commit) via

Re: [cmake-developers] Adding compile and build type tests to CMake/CTest

2017-09-20 Thread Edward Diener
On 9/18/2017 8:16 AM, Brad King wrote: On 09/15/2017 09:22 AM, Edward Diener wrote: A gui environment like Visual Studio does provide functionality to just compile one or more source files, and it also provides functionality to just build an executable from one or more source files without

[cmake-developers] CMake 3.9.3 available for download

2017-09-20 Thread Robert Maynard
We are pleased to announce that CMake 3.9.3 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.9.3 since 3.9.2: Brad

[Cmake-commits] CMake branch, master, updated. v3.9.3-884-g1cf9437

2017-09-20 Thread Kitware Robot
_VERSION_MINOR 9) -set(CMake_VERSION_PATCH 20170920) +set(CMake_VERSION_PATCH 20170921) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

[Cmake-commits] CMake branch, release, updated. v3.9.2-13-g8dae0ab

2017-09-20 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 8dae0ab6d1a5607ba03dbfff1c6458efd02bd5e3 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.9.2-878-g28cbfe1

2017-09-20 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 28cbfe151944a85a227ea5c41b76fa0621ac707b (commit) via

[cmake-developers] Custom script invocation from imported target

2017-09-20 Thread Nagy-Egri Máté Ferenc via cmake-developers
Hi! I am trying to improve the developer experience of SYCL users for both those using triSYCL and ComputeCpp alike. (TL;DR: SYCL is CUDA of OpenCL, triSYCL being a non-conforming playground implementation built atop OpenMP, while ComputeCpp is the first (and only) conforming GPU-accelerated

Re: [cmake-developers] Custom script invocation from imported target

2017-09-20 Thread Robert Maynard
Hi, You are correct that as it stands it is challenging to add custom linking / compilation steps in CMake for moc The challenge with these approaches is that you 1. The unfortunate truth is that a cmake configure time script lacks the required information. Numerous things such as the location

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

2017-09-20 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 annotated tag, v3.9.3 has been created at 12b6fd9001adb6ffb511b4811a354b75c42baa98 (tag) tagging

[Cmake-commits] CMake branch, release, updated. v3.9.2-14-g7486607

2017-09-20 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 7486607c874de3e44d33f152775fd073de2ba2c0 (commit) from

[Cmake-commits] CMake branch, master, updated. v3.9.2-880-g821b54f

2017-09-20 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 821b54f4a6e1cebfc8d5c9b061c45683a4a5c6ba (commit) via

Re: [cmake-developers] Proposal: Support more protoc options in FindProtobuf

2017-09-20 Thread Brad King
On 09/19/2017 07:50 PM, Peter Mitrano wrote: > Does this sound reasonable? Would this be something I could contribute? Yes, see: https://gitlab.kitware.com/cmake/cmake/blob/master/CONTRIBUTING.rst for instructions. Thanks, -Brad -- Powered by www.kitware.com Please keep messages on-topic