14:02
An: Stuermer, Michael SP/HZA-ZSEP; CMake Developers
Betreff: Re: AW: [cmake-developers] Pushing to gitlab.kitware.org from behind a
ssl proxy
On 3/29/19 8:51 AM, Stuermer, Michael SP/HZA-ZSEP wrote:
> - pushing to kitware without 2FA fails
> - pushing to kitware with 2FA fails
Try
, 19. März 2019 13:42
An: Stuermer, Michael SP/HZA-ZSEP; CMake Developers
Betreff: Re: [cmake-developers] Pushing to gitlab.kitware.org from behind a ssl
proxy
On 3/19/19 2:21 AM, Stuermer, Michael SP/HZA-ZSEP wrote:
> remote: HTTP Basic: Access denied
> fatal: Authentication failed for
&g
Hello CMake developers,
It's been some time now and I have tried everything that came into my mind (and
I found on google), but I found no way to push any changes on my CMake fork.
My situation: I am behind a corporate firewall which proxies/breaks all ssl
connections and ssh is blocked
Robert
> Dailey
> Gesendet: Dienstag, 26. Juni 2018 17:34
> An: Brad King
> Cc: Stuermer, Michael SP/HZA-ZSEP; CMake Developers
> Betreff: Re: [cmake-developers] 3.12.0-rc1: C# project outputting as a
> "vcxproj" (C++ project)
>
> I'm happy to do that. I assume you wou
Hello Wouter,
testing CMake code is indeed very important. This is why kitware does it as
well. Did you check the CMake code testing infrastructure in "Tests/RunCMake"
in the sources? It is a very flexible concept which makes adding tests easy
enough for everyone contribute (IMO). At the
> -Ursprüngliche Nachricht-
> Von: CMake [mailto:cmake-boun...@cmake.org] Im Auftrag von Marek
> Vojtko (Firaxis)
> Gesendet: Dienstag, 3. April 2018 23:24
> An: cmake@cmake.org
> Betreff: Re: [CMake] IMPORTED DLL-only Target on MSVC
>
> > > Is it not possible to wrap an external DLL-only
> -Ursprüngliche Nachricht-
> Von: CMake [mailto:cmake-boun...@cmake.org] Im Auftrag von Marek
> Vojtko (Firaxis)
> Gesendet: Dienstag, 3. April 2018 00:49
> An: cmake@cmake.org
> Betreff: [CMake] IMPORTED DLL-only Target on MSVC
>
> Hi,
>
> Is it not possible to wrap an external
%"
Qt patch to fix compiler error:
https://codereview.qt-project.org/#/c/207772/
Maybe this helps someone else trying to do a full static build of CMake for
Windows.
Best regards,
Michael
> -Ursprüngliche Nachricht-
> Von: cmake-developers [mailto:cmake-developers-boun...@cmake.
>
> On 2/16/2018 7:43 AM, Stuermer, Michael SP/HZA-ZSEP wrote:
> > 1) The debug version crashes in
>
> I don't know if we've ever built a debug configuration against this Qt.
>
> > This application failed to start because it could not find or load the
>
l
directory afterwards.
-Ursprüngliche Nachricht-
Von: Brad King [mailto:brad.k...@kitware.com]
Gesendet: Dienstag, 13. Februar 2018 18:11
An: Stuermer, Michael SP/HZA-ZSEP
Cc: cmake-developers@cmake.org
Betreff: Re: [cmake-developers] CMake build with static crt and static QtDialog
not li
I try to do a CMake build with static C runtime and a static Qt 5.10.0 build to
avoid runtime errors when giving the binaries to colleagues. The Visual Studio
version is 2017. AFAIK the official CMake builds already use this
"full-static-build" scheme. However I end up with some linking errors
Hello Nikita,
Brad mentioned a feature freeze for version 3.8 at the end of january. Looking
at the source history for version 3.7, it can take some time until the final
release is done:
3.10.2016: (candidate 1)
19.10.2016: (candidate 2)
4.11.2016: (candidate 3)
11.11.2016: (final release)
Hallo Aaron,
if you’d like to have the full luxury of visual studio with test explorer and
running/debugging tests directly as you can do it with other .NET based tests
etc. you can try these extensions:
- child process debugging power tools
Hello,
To add your mentioned libraries to the executable you have to link against
them. For this the cmake command
target_link_libraries() is used:
https://cmake.org/cmake/help/v3.7/command/target_link_libraries.html
In your case the cmake code should look similar to this:
>From my side access to the web interface as well as repo handling is also
>slower than github. I personally consider this more to be a luxury problem
>than a real issue. Would be great if were faster but it works well for me. On
>the other hand I like the whole workflow, that is great!
I
> -Original Message-
> From: Brad King [mailto:brad.k...@kitware.com]
> Sent: Wednesday, October 26, 2016 5:13 PM
> To: Stuermer, Michael SP/HZA-ZSEP
> Cc: cmake-developers@cmake.org
> Subject: Re: [cmake-developers] gitlab or github? Which should I use for
> contri
I know the cmake repositories on github and gitlab are in sync, so I could base
my work on any of them. Still I don't want to maintain two forks and would
prefer to switch completely to gitlab.kitware instead.
Which should I choose for future contributions? My feeling is I could
completely
Hello Roman,
directories are added automatically to the directories.wxs file if you use the
install() command in cmake and set the DESTINATION to some subfolder:
install(FILES
DESTINATION "my/sufolder/path")
To add completely new directories I'd suggest to use CPACK_WIX_EXTRA_SOURCES
These are some minor changes for native support of C# targets. The remaining
C++ implementation will go into the Visual Studio target 10 generator class.
Best Regards
Michael Stürmer
0001-preparational-patches-for-CSharp-support.patch
Description:
Hi,
check this out, might help: https://github.com/micst/CMake.git
There is a working C# implementation available. I permanently try to keep it
up-to-date with master and mergable so the workload will not become too large
as soon as I find time to prepare patches for upstream. Contribution
> -Original Message-
> From: Nils Gladitz [mailto:nilsglad...@gmail.com]
> Sent: Friday, September 09, 2016 8:33 AM
> To: Stuermer, Michael SP/HZA-ZSEP; CMake Developers
> Subject: Re: [cmake-developers] [Patch 5/5] Improved WIX support
>
> On 09/06/2016 01:26 PM,
> -Original Message-
> From: Nils Gladitz [mailto:nilsglad...@gmail.com]
> Sent: Tuesday, September 06, 2016 4:28 PM
> To: Stuermer, Michael SP/HZA-ZSEP; CMake Developers
> Subject: Re: [cmake-developers] PATCH: Bugfix for WIX support
>
> On 09/06/2016 03:45 P
> -Original Message-
> From: Nils Gladitz [mailto:nilsglad...@gmail.com]
> Sent: Tuesday, September 06, 2016 3:50 PM
> To: Stuermer, Michael SP/HZA-ZSEP; CMake Developers
> Subject: Re: [cmake-developers] PATCH: add custom xmlns namespaces into
> generated .wxs sources
Wow, thanks for the fast answer!
> -Original Message-
> From: Nils Gladitz [mailto:nilsglad...@gmail.com]
> Sent: Tuesday, September 06, 2016 2:29 PM
> To: Stuermer, Michael SP/HZA-ZSEP; CMake Developers
> Subject: Re: [cmake-developers] PATCH: add custom xmlns namespaces i
best regards,
Michael
0002-added-support-for-custom-WIX-namespaces-in-generated.patch
Description: 0002-added-support-for-custom-WIX-namespaces-in-generated.patch
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
The generated guid values where not set correctly everywhere. This could lead
to WIX build errors when using the CPACK_WIX_SKIP_PROGRAM_FOLDER option.
Viele Grüße
Michael Stürmer
SZ. Prozessdatenverarbeitung
SP/HZA-ZSEP Tel. +499132 82-86350 Mobil.: +49(171)6860010
> -Original Message-
> From: Nils Gladitz [mailto:nilsglad...@gmail.com]
> Sent: Tuesday, August 16, 2016 10:54 AM
> To: Stuermer, Michael SP/HZA-ZSEP; CMake Developers
> Subject: Re: [cmake-developers] [Patch 5/5] Improved WIX support
>
> On 08/16/2016 10:15 AM,
> -Original Message-
> From: Nils Gladitz [mailto:nilsglad...@gmail.com]
> Sent: Friday, August 12, 2016 9:42 AM
> To: Stuermer, Michael SP/HZA-ZSEP; CMake Developers
> Subject: Re: [cmake-developers] [Patch 5/5] Improved WIX support
>
> On 07/20/2016 03:58 PM, Stu
> -Original Message-
> From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Patrik
> Lehmann
> Sent: Thursday, August 11, 2016 11:04 AM
> To: cmake@cmake.org
> Subject: [CMake] Use GLOB to generate filelist for install package
>
> Hello,
>
> I try to use GLOB to collect the files
> -Original Message-
> From: Nils Gladitz [mailto:nilsglad...@gmail.com]
> Sent: Tuesday, August 02, 2016 10:47 AM
> To: Stuermer, Michael SP/HZA-ZSEP; CMake Developers
> Subject: Re: [cmake-developers] [Patch 3/5] Improved WIX support
>
> On 07/20/2016 03:58 PM,
> -Original Message-
> From: cmake-developers [mailto:cmake-developers-boun...@cmake.org]
> On Behalf Of Dennis Luehring
> Sent: Friday, July 22, 2016 6:38 AM
> To: cmake-developers@cmake.org
> Subject: [cmake-developers] C# with CMake
>
> any status update for the CMake C# Generator?
>
> -Original Message-
> From: Nils Gladitz [mailto:nilsglad...@gmail.com]
> Sent: Thursday, July 21, 2016 8:56 AM
> To: Stuermer, Michael SP/HZA-ZSEP; CMake Developers
> Subject: Re: [cmake-developers] [Patch 1/5] Improved WIX support
>
> On 07/20/2016 03:58 PM, Stu
> -Original Message-
> From: Nils Gladitz [mailto:nilsglad...@gmail.com]
> Sent: Wednesday, July 20, 2016 12:03 PM
> To: Stuermer, Michael SP/HZA-ZSEP; CMake Developers
> Subject: Re: [cmake-developers] Improved WIX support
>
> On 19.07.2016 17:43, Stuermer, Mich
Hello there,
in short:
I fixed some minor issues with WIX toolset support and added the possibility to
integrate service installation/uninstallation with generated msi packages.
Please review and comment what is missing for integration in upstream.
a bit longer:
When creating a
Hi Niklas,
native support for C# is not available in CMake. There is some work in
progress, but it's not yet integrated:
https://github.com/micst/CMake
Unfortunately I haven't had the time yet to adapt the topic to the new
formatting style, so it doesn't merge well with the current Kitware
ome native C++ libs ?
>
> Thanks !
>
>
> On Mon, Mar 21, 2016 at 8:09 AM, Stuermer, Michael SP/HZA-ZSEP
> <michael.stuer...@schaeffler.com> wrote:
> > Sorry for asking, but do you mean
> >
> > 1. without support for ninja/nmake/make there is no use having C#
> >
todo list until C#
support may reach a mature level.
best regards,
Michael
> -Original Message-
> From: David Cole [mailto:dlrd...@aol.com]
> Sent: Tuesday, March 08, 2016 12:51 AM
> To: Brad King
> Cc: Stuermer, Michael SP/HZA-ZSEP; CMake Developers
> Subject: Re: [c
Thanks for the hints, I will adapt the C# detection.
best regards,
Michael
> -Original Message-
> From: Brad King [mailto:brad.k...@kitware.com]
> Sent: Monday, March 07, 2016 8:12 PM
> To: Stuermer, Michael SP/HZA-ZSEP
> Cc: Gilles Khouzam; CMake Developers
> S
regards,
Michael
> -Original Message-
> From: Robert Goulet [mailto:robert.gou...@autodesk.com]
> Sent: Monday, February 29, 2016 3:16 PM
> To: Stuermer, Michael SP/HZA-ZSEP; Gilles Khouzam; CMake Developers
> Subject: RE: C# support ready for review
>
> As soon as this
You can check for existence of a variable and you can invert the result of the
evaluation:
if(DEFINED )
# called if variable exists, never mind if it's empty or not
endif()
if(NOT DEFINED )
# called if variable is not defined
endif()
if(NOT )
# called if variable is
: Gilles Khouzam [mailto:gilles.khou...@microsoft.com]
Sent: Thursday, February 25, 2016 8:44 AM
To: Stuermer, Michael SP/HZA-ZSEP; CMake Developers
Subject: RE: C# support ready for review
Hi Michael,
Things are looking really good, I've just converted one of my personal projects
to using CMake
ch I need
for local building and usage.
best regards,
Michael
From: cmake-developers [mailto:cmake-developers-boun...@cmake.org] On Behalf Of
Stuermer, Michael SP/HZA-ZSEP
Sent: Wednesday, February 10, 2016 3:03 PM
To: CMake Developers
Subject: [cmake-developers] C# support ready for review
Nati
illes.khou...@microsoft.com]
Sent: Thursday, February 18, 2016 8:17 AM
To: Stuermer, Michael SP/HZA-ZSEP; CMake Developers
Subject: RE: C# support ready for review
Hi Michael,
Great work, this looks really good.
I have a few comments on the changes.
1. You should use the registry to find the in
Native C# support is ready for review. I split the patch in two parts:
part 1:
Some preparational stuff that does not really change or enable anything.
Documentation and Test files as well as the required CMake module is added. The
changes to existing code are small, only few methods in
: Stuermer, Michael SP/HZA-ZSEP<mailto:michael.stuer...@schaeffler.com>
Feladva: 2016.02.04. 16:27
Címzett: Nagy-Egri Máté Ferenc<mailto:csiga.b...@aol.com>;
cmake@cmake.org<mailto:cmake@cmake.org>
Tárgy: RE: CTest integration in Visual Studio TestExplorer
Hi Máté,
thanks for tr
ake files, there is no checking
for platform or bitness done.
Cheers,
Máté
Feladó: Stuermer, Michael SP/HZA-ZSEP<mailto:michael.stuer...@schaeffler.com>
Elküldve: 2016. január 22., péntek 12:37
Címzett: cmake@cmake.org<mailto:cmake@cmake.org>
Tárgy: [CMake] CTest integration in Visua
I would like to move the ALL_BUILD target tot he "CMakePredefinedTargets",
however this seems not be possible straight away. At least even at the very end
of the very last CMakeLists.txt I still cannot call
set_target_properties(ALL_BUILD
PROPERTIES
FOLDER " CMakePredefinedTargets ")
this.
best regards,
Michael
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Stuermer, Michael
SP/HZA-ZSEP
Sent: Friday, January 29, 2016 3:43 PM
To: cmake@cmake.org
Subject: [CMake] Setting target property FOLDER on target ALL_BUILD
I would like to move the ALL_BUILD target tot he "CMa
Hello everyone,
picking up the line from Tobias from around a year ago I changed a few things
in the ctest unittest adapter. It now works for both Visual Studio 2013 and
2015. 2012 is supported in general but I didn't try it (means: I can install
it). Merging and pull request for original
How can I avoid a custom target to be rebuild everytime I build my solution? I
added my target like this:
add_custom_target(CopyNugetPackages
DEPENDS ${depends_list}
COMMENT " copying nuget packages "
VERBATIM
)
set_target_properties(CopyNugetPackages PROPERTIES
> -Original Message-
> From: Kislinskiy, Stefan [mailto:s.kislins...@dkfz-heidelberg.de]
> Sent: Tuesday, November 17, 2015 10:11 AM
> To: Stuermer, Michael SP/HZA-ZSEP; CMake Developers
> Subject: AW: [cmake-developers] Code style auto-formatting
>
> Do you know C
> On 11/16/2015 10:45 AM, Stuermer, Michael SP/HZA-ZSEP wrote:
> > Sphinx does not seem to provide any "default" theme anymore, it's
> > called "classic" now.
>
> Thanks. This was previously discussed here:
>
> https://cmake.org/pipermail/cmake/2015-J
Sphinx does not seem to provide any "default" theme anymore, it's called
"classic" now. I'm not sure if this breaks documentation generation at Kitware,
but the documentation on cmake.org is generated using sphinx 1.4a0+ and I'm
using 1.3.1 here.
It might even be better to make the html_theme
I would like to add a Visual Studio variable such as $(VCInstallDir) to the
include directories of a target.
include_directories() obviously does not work, as cmake thinks the path is
relative and the project path is prepended to my initial value.
Any hints how I can do this?
PS: the same
s electronic
transmission in error, please notify the sender and delete the material from
the computer.
From: Robert Goulet [mailto:robert.gou...@autodesk.com]
Sent: Monday, November 02, 2015 10:25 PM
To: Stuermer, Michael SP/HZA-ZSEP; cmake-developers@cmake.org; Gilles Khouzam
Subject: C# suppo
30, 2015 3:49 PM
To: cmake-developers@cmake.org
Subject: Re: [cmake-developers] C# support?
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
Have a look at cmake_minimum_required() and cmake_policy(). I think with these
both it should be possible to verify you are using a cmake version that
provides all features which are required by your project.
See here:
Did you add the directory where your find script is in to the CMAKE_MODULE_PATH?
To verify your script is called, just add a message(executing my module) or
so on top of your script, this always works very well for me when I'm not sure.
See here for more info about the CMAKE_MODULE_PATH:
, Michael SP/HZA-ZSEP wrote:
Does it have a realistic chance to be accepted for upstream
Yes, so long as it comes with proper tests and is not too intrusive
on
the overall design/implementation of CMake.
In order to enable use of C# sources we should get
enable_language(CSharp
]
Sent: Tuesday, June 30, 2015 10:18 AM
To: Stuermer, Michael SP/HZA-ZSEP
Cc: cmake-developers@cmake.org
Subject: Re: [cmake-developers] C# support?
On Tue, Jun 30, 2015 at 9:21 AM, Stuermer, Michael SP/HZA-ZSEP
michael.stuer...@schaeffler.commailto:michael.stuer...@schaeffler.com wrote:
[...]
About
Hi and sorry for cross-posting this on both lists,
I checked the mailing list history about the C#/.NET support topic and realized
that the interest in C# support seems to have declined a bit.
I am right now in the need of good C# support and adding external project files
is not that much of
Hi and sorry for cross-posting this on both lists,
I checked the mailing list history about the C#/.NET support topic and realized
that the interest in C# support seems to have declined a bit.
I am right now in the need of good C# support and adding external project files
is not that much of
Does anyone have a configuration for astyle which indents my code according to
the CMake coding rules? Would make my life much easier right now.
Directions where I can find a complete set of rules how the code should be
formatted would also suffice.
best regards
Michael Stürmer
--
Powered
Thanks, I think this should be enough for me to configure the visual studio
plugin accordingly.
-Original Message-
From: Brad King [mailto:brad.k...@kitware.com]
Sent: Monday, June 22, 2015 3:43 PM
To: Stuermer, Michael SP/HZA-ZSEP; cmake-developers@cmake.org
Subject: Re: [cmake
-Original Message-
From: Brad King [mailto:brad.k...@kitware.com]
Sent: Monday, June 15, 2015 4:11 PM
To: Stuermer, Michael SP/HZA-ZSEP
Cc: cmake-developers@cmake.org
Subject: Re: [cmake-developers] [PATCH] fixed msvc 64 bit build
On 06/15/2015 07:58 AM, Stuermer, Michael SP/HZA
I have doxygen, gnuplot, html help and the UnxUtils in C:\Program Files
(x86)\ This leads to errors when using one of these tools. I hope putting
some around tool-names does not break anything on linux.
Best Regards
Michael Stürmer
This is just a one-char-bugfix, WIN32 instead of _WIN32 macro was used. Sorry
if I should have opened up a ticket in mantis before posting here. Just didn't
know what would be correct order.
Are there any regular Win64 builds done actually? I'm just curious if there is
anyone else using 64bit
67 matches
Mail list logo
