Uhm, I have to admit that I have not experience in unity development at all so this is not that much of a simple question for me. But my main motivation for native C# support in CMake was to be able to mix native C++, managed C++ and C# binaries within one solution and to build them all together. If this is what you would like to do: yes this works well for me.
best regards, Michael > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Jean-Michaël Celerier > Sent: Monday, March 21, 2016 9:26 AM > To: Stuermer, Michael SP/HZA-ZSEP > Cc: CMake Developers > Subject: Re: [cmake-developers] C# support ready for review > > Simple question : do you think that this would be useable in order to have a > single build pipeline based on CMake for a Unity3D project that also requires > some native C++ libs ? > > Thanks ! > > > On Mon, Mar 21, 2016 at 8:09 AM, Stuermer, Michael SP/HZA-ZSEP > <[email protected]> wrote: > > Sorry for asking, but do you mean > > > > 1. without support for ninja/nmake/make there is no use having C# > > support in cmake > > > > or > > > > 2. using the current approach this could also work with the other > > generators without too much additional work > > > > ? > > > > I'm just a little confused and try to find out what's on my todo list until > > C# > support may reach a mature level. > > > > best regards, > > Michael > > > >> -----Original Message----- > >> From: David Cole [mailto:[email protected]] > >> Sent: Tuesday, March 08, 2016 12:51 AM > >> To: Brad King > >> Cc: Stuermer, Michael SP/HZA-ZSEP; CMake Developers > >> Subject: Re: [cmake-developers] C# support ready for review > >> > >> Seems to me like C# support should work just fine with other generators: > >> ninja, nmake, and UNIX Makefiles included. Especially with mono on > >> Linux/Mac. > >> > >> > >> David > >> > >> > On Mar 7, 2016, at 2:12 PM, Brad King <[email protected]> wrote: > >> > > >> >> On 02/25/2016 05:51 AM, Stuermer, Michael SP/HZA-ZSEP wrote: > >> >> The part that probably needs most additional work is all the C# > >> >> detection and configuration part in the module scripts. > >> > > >> > In your branch Modules/CMakeDetermineCSharpCompiler.cmake > >> currently > >> > has a lot of logic and environment checks for this. It shouldn't > >> > need to be that complicated. Anything requiring deep introspection > >> > of the system (especially the registry) should be something done in > >> > the C++ generator implementation and provided to CMake platform > >> > files as a variable. > >> > > >> > For example, the VS generators always provide msbuild: > >> > > >> > > >> > https://cmake.org/cmake/help/v3.5/variable/CMAKE_VS_MSBUILD_COMM > >> AND.ht > >> > ml > >> > > >> > For the path to the compiler tool, take a look at > >> > > >> > Modules/CompilerId/VS-10.vcxproj.in > >> > > >> > and use of it by Modules/CMakeDetermineCompilerId.cmake. That all > >> > runs while detecting the compiler id using a small test project. > >> > It has a custom command that searches the PATH in the IDE project > >> > build environment to print out the path to the compiler. You > >> > should create one like this for CSharp too. > >> > > >> > We'll also need to define behavior when CSharp is enabled by > >> > projects under a non-VS generator. Other generators should reject > >> > any such attempt with an error message. > >> > > >> > 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: > >> > http://public.kitware.com/mailman/listinfo/cmake-developers > > -- > > > > 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: > > http://public.kitware.com/mailman/listinfo/cmake-developers -- 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: http://public.kitware.com/mailman/listinfo/cmake-developers
