[cmake-developers] 3.12.0-rc1: C# project outputting as a "vcxproj" (C++ project)
Stuermer, Michael SP/HZA-ZSEP
michael.stuermer at schaeffler.com
Wed Jun 27 01:30:09 EDT 2018
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: rcdailey at gmail.com [mailto:rcdailey at gmail.com] Im Auftrag von 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 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 <brad.king at kitware.com>
> wrote:
> > 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 it before. Is this
> >> considered a symptom of a bug? Or is this required behavior? To be
> >> honest, I'm not sure what criteria is used by CMake to deduce the
> >> linker language of targets, especially in the C# case. It appears
> >> that introducing a link-level dependency from a C# project to a
> >> Managed C++ project, forces the parent project to be C++ as well.
> >
> > Please open an issue for that.
> >
> > Thanks,
> > -Brad
More information about the cmake-developers
mailing list