Also, this ticket seems to be very similar to what you are seeing if you
dig down a bit:
https://gitlab.kitware.com/cmake/cmake/issues/17678
But again, I do this exact same thing with Shared instead of Module
libraries and it works. I would think that modules shouldn’t even be
allowed for C# targ
FWIW: I do almost this exact thing currently and have no issues (even mix
in Managed C++ wrappers around naive code). The only difference is that I
don’t compile any C# modules, only Shared libs. Not sure if that could be a
problem or not.
I’m using CMake 3.11 and VS 2015.
-Caleb
On Thu, Aug 16,
Philip, thanks for the concise description of the problem. Would you be
willing to report this in CMake's gitlab as an issue so we can better track
it and refer to it in merge requests, etc.? You can report a new issue here:
https://gitlab.kitware.com/cmake/cmake/issues/new
Thanks
On Fri, Aug 1
> Can't that be set by passing the toolset with a -T
That is what I was trying to say with my last sentence. You will need
to use CMake 3.12 to have support for specifying the minor toolset
version though.
On Thu, Aug 16, 2018 at 3:31 PM J Decker wrote:
>
>
> On Thu, Aug 16, 2018 at 9:18 AM Brian
On Thu, Aug 16, 2018 at 9:18 AM Brian Davis wrote:
>
>
> On Wed, Aug 15, 2018 at 11:58 AM, Robert Maynard <
> robert.mayn...@kitware.com> wrote:
>
>> The MSVC / CUDA support recently has been very challenging to keep track
>> of. In general CUDA will only support a single patch release of MSVC, a
Thanks, Cyril
I did try find_package_handle_standard_args but it failed. It didn't occur
to me that I needed to set Hi Sebastiàn,
>
> Your question got me thinking and I also figured that way of doing it
> works:
>
> set(_CONFIG ${CMAKE_CURRENT_LIST_FILE})
> find_package_handle_standard_args( CON
On Wed, Aug 15, 2018 at 11:58 AM, Robert Maynard wrote:
> The MSVC / CUDA support recently has been very challenging to keep track
> of. In general CUDA will only support a single patch release of MSVC, and
> given how MSVC 2017 doesn't easily allow rollbacks and has a pretty
> aggressive update
All,
Thank you in advance,
I'm an experienced CMake user, in the C++ realm. I'm presently working outside
that realm, porting a 200-project solution from Visual Studio (.vcxproj,
.csproj) files to CMake. I'm very pleased that CMake has adopted CSharp! Thank
you!
I seem to have uncovered a b
Hi all,
In our ctest script, we used a cmake files generated from building
third-party libraries, i.e.:
cmake -C"/path/to/third-parties/share/cmake/amanzi-tpl-config.cmake" [other
options]
Is there a way to pass all those configurations (i.e.
PATH/LD_LIBRARY_PATH/CPATH) into the ctest environmen
On Thu, Jun 28, 2018 at 4:07 PM Stephan Menzel
wrote:
> I am observing a strange problem regarding dependencies to static libs in
> executables. I am not entirely sure but it seems this started since I
> upgraded to the 3.11 line. I am using Windows and MSVC14.
>
> Basically, my code base contain
Hi Sebastiàn,
Your question got me thinking and I also figured that way of doing it works:
set(_CONFIG ${CMAKE_CURRENT_LIST_FILE})
find_package_handle_standard_args( CONFIG_MODE)
This allows you to keep most of the nice logic inside
FindPackageHandleStandardArgs.
Best regards,
Cyril
2018-08-15
Hello,
I use CPack and productbuild on Mac OS. When I run the Installer after
creation, then the welcome message in the Installer is German, but I do not
find a translation for the original english document. Where do the translation
come from?
Thanks in advance
Regards
Roman
--
Powered by w
12 matches
Mail list logo
