This is weird: there is a test case called CSharpLinkToCxx which should cover
the
mentioned error.
@rcdailey: could you check if this example works for you?
best regards,
Michael
> -Ursprüngliche Nachricht-
> Von: rcdai...@gmail.com [mailto:rcdai...@gmail.com] Im Auftrag von Robert
> Da
Le 26/06/2018 à 17:18, Brad King a écrit :
On 06/25/2018 01:56 PM, Raffi Enficiaud wrote:
would it be possible to add the following to the release notes?
* FindMatlab now supports the Matlab Runtime Compiler (MCR) for
compiling and linking matlab extensions. The MCR does not
consume any
On 06/26/2018 11:34 AM, Robert Dailey wrote:
> I'm happy to do that. I assume you would require an MCVE for that bug?
> If so it will take me considerably longer, as I don't have a lot of
> time to build a reproducible example from scratch. I'll do my best,
> though.
Even without a MCVE it's worth
I'm happy to do that. I assume you would require an MCVE for that bug?
If so it will take me considerably longer, as I don't have a lot of
time to build a reproducible example from scratch. I'll do my best,
though.
On Tue, Jun 26, 2018 at 10:06 AM, Brad King wrote:
> On 06/26/2018 10:25 AM, Rober
On 06/25/2018 01:56 PM, Raffi Enficiaud wrote:
> would it be possible to add the following to the release notes?
>
> * FindMatlab now supports the Matlab Runtime Compiler (MCR) for
>compiling and linking matlab extensions. The MCR does not
>consume any license and is free to download.
Add
On 06/26/2018 10:25 AM, Robert Dailey wrote:
> To fix this issue for now I had to do this:
>
> set_property( TARGET ${project_name} PROPERTY LINKER_LANGUAGE CSharp )
>
> I don't remember having to explicitly tell CMake that the project is
> CSharp in the past; it was always able to deduce
To fix this issue for now I had to do this:
set_property( TARGET ${project_name} PROPERTY LINKER_LANGUAGE CSharp )
I don't remember having to explicitly tell CMake that the project is
CSharp in the past; it was always able to deduce it before. Is this
considered a symptom of a bug? Or is
Using 3.12.0-rc1, if I create a C# project, but use
`target_link_libraries` on it to pull in a dependency to a managed C++
target, the C# project turns into a "vcxproj" after generation,
whereas if I remove the "target_link_libraries()" call, it outputs as
a "csproj" as I expect.
Is this a known i