Hi and thanks for all your answers,
Let me give you some information how things are implemented so far and where my
constraints in implementing C# support are:
At the moment I have only Visual Studio 2013 available, which makes it hard for
me to test any other generators. NMake is not a
On Tue, Jun 30, 2015 at 9:21 AM, Stuermer, Michael SP/HZA-ZSEP
michael.stuer...@schaeffler.com wrote:
[...]
About the language:
Would it be ok to name the language in CMake CS instead of CSharp? I
did everything as CS so far...
If I may provide an outsider's comment on this point, I
On 30/06/2015 22:28, Stephen Kelly wrote:
Hi Steve,
thanks for looking at this.
Bill Somerville wrote:
Any ideas how I can control the ordering or reorder the
TARGET_INCLUDE_DIRECTORIES property?
add_executable(hello main.cpp)
target_link_libraries(hello Qt5::Widgets)
20150630)
+set(CMake_VERSION_PATCH 20150701)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
Yes, please do spell it out as CSharp. CS could mean about a billion things...
On Tue, Jun 30, 2015 at 5:19 AM, Stuermer, Michael SP/HZA-ZSEP
michael.stuer...@schaeffler.com wrote:
Sounds reasonable,
my choice was motivated by the file extension of the C# source files (.cs)
and that it is
I am getting the error in the subject. The code I have looks like this:
if (PRE_COMPILED_HEADERS_FOUND)
ADD_PRECOMPILED_HEADER(${header_pch} ${source_pch} sources systemc)
endif()
add_library(systemc ${sources} ${sources_no_pch} ${headers})
where the call to add_dependency
Sounds reasonable,
my choice was motivated by the file extension of the C# source files (.cs) and
that it is shorter. But as Fortran seems to use the longer “Fortran”
description it might be a good idea to switch to “CSharp” as well …
Michael
From: Petr Kmoch [mailto:petr.km...@gmail.com]
On 06/30/2015 03:21 AM, Stuermer, Michael SP/HZA-ZSEP wrote:
it would be great if some people could step forward once
everything is running from my side to help get makefile and linux
support (and test other Visual Studio versions).
Once you have it working in VS 2013 the other VS = 2010
On 06/29/2015 09:41 PM, Mark Moll wrote:
I have attached an alternative module that replaces the two current
modules for finding python-related info. With the current modules
it is easy to end up in a situation where the interpreter’s version
and the library version do not match, which
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 585e9da0e2262c11b7be1a728f88dddb31c2ed0b (commit)
via
Brad,
Thanks for the detailed explanation. I figured there were use cases not handled
by my module. For instance, I hadn’t thought of cross-compilation. Since in my
own project these unhandled cases haven't come up, I’ll stick with own module
for now.
With the existing modules it might be
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 333b0bc7055efb1369fa6cda0586e68553c8ebe3 (commit)
via
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 fe09e6f9165d594c1a455f99f99c2700237957b6 (commit)
via
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 5da2e18f384f4a748eb0e440b482a444deede5d5 (commit)
via
I just want to add that I also saw a colleague running in the issue
described in the beginning of the thread and that the version reported by
the Python module and the PythonLibs one were different strings, even
though the version was actually the same. It happened on latest Debian I
think.
How I
I’ve run into similar problems, but I think this is by design: CMake isn’t
going to let you do anything to a target until that target exists. For me, it
was pretty straightforward to adjust my CMakeLists to satisfy the requirement.
If you don’t want to split apart your macro, one thing you
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 d2e9ccbc7f3de688d3ec187ab093607eab8d82d7 (commit)
via
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 7e3ac12df45fa42b590971accaf1db89b1a0ffb6 (commit)
via
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 2beb245b57e47bf41ef2a7a469f74cfd16420748 (commit)
via
-Original Message-
From: cmake-developers [mailto:cmake-developers-boun...@cmake.org]
On Behalf Of Brad King
Sent: Tuesday, June 30, 2015 13:49
To: cmake-developers@cmake.org
Subject: Re: [cmake-developers] C# support?
On 06/30/2015 03:21 AM, Stuermer, Michael SP/HZA-ZSEP wrote:
I have a small C++ project for which the source code is distributed in a
small directory hierarchy. I have a master CMakeLists.txt file at the
project root as well as one for each source subdirectory. How would I
configure the CMakeLists.txt files so that the build produces a single
library file
Michael, this is great. Thank you for doing this. I will gladly help with the
other versions of Visual Studio and can provide some help if you need. Feel
free to reach out.
~Gilles Khouzam
-Original Message-
From: cmake-developers [mailto:cmake-developers-boun...@cmake.org] On Behalf
Patrick Griffiths wrote:
I'm trying to add the /PDBSTRIPPED option LINK_FLAGS_RELWITHDEBINFO config
(Visual Studio generator, obviously):
set_target_properties(target PROPERTIES
LINK_FLAGS_RELWITHDEBINFO
/PDBSTRIPPED:
$TARGET_FILE_DIR:target/stripped/$TARGET_FILE_NAME:target.pdb)
Bill Somerville wrote:
Any ideas how I can control the ordering or reorder the
TARGET_INCLUDE_DIRECTORIES property?
add_executable(hello main.cpp)
target_link_libraries(hello Qt5::Widgets)
target_include_directories(
$TARGET_PROPERTY:Qt5::Widgets,INTERFACE_INCLUDE_DIRECTORIES
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 fe3cbb78721dc84d01ab030422a67013d1595f3d (commit)
via
Stephen Kelly wrote:
Any suggestions on how I might accomplish this in a reasonable way?
Add the flag with target_link_libraries instead.
Ah, I see you tried that, sorry for the noise.
Thanks,
Steve.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ
Michael Scott wrote:
Thanks for the comments, here is the previous patch, with the suggested
amendments.
Thanks for working on this.
I'm wondering how these new command line options relate to the existing
options -Wdev and -Wno-dev. Is there any reason not to make those existing
options set
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 352ef3970ebc3f30bb2bb04502d7db8206955da8 (commit)
via
Glenn Coombs wrote:
I am getting the error in the subject. The code I have looks like this:
if (PRE_COMPILED_HEADERS_FOUND)
ADD_PRECOMPILED_HEADER(${header_pch} ${source_pch} sources
systemc)
endif()
add_library(systemc ${sources} ${sources_no_pch}
29 matches
Mail list logo
