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.k...@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
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake-developers
