I agree. The right approach is to do an integration of Java in the same way as C or C++. But I don’t have currently enough CMake skills to do this work.
Do you have some documentation explaining how language support is done in CMake ? And how specific behaviours of Java/Scala can be supported in CMake: * All sources composing a jar must be compiled all at once * A source file can produce an arbitrary number of binary files (.class) with various (and unpredictable) names. Marc On 18/02/16 16:06, "Brad King" <brad.k...@kitware.com> wrote: >On 02/18/2016 06:28 AM, CHEVRIER, Marc wrote: >> Currently, there is a module UseJava.cmake which mix two aspects: > >This module is not a good example of how to do a language in CMake. >It somehow became the way to do Java in CMake because the builtin >support for enable_language(Java) was never really made to work right. >(It tries to do separate compilation which is not really generally >possible in Java due to circular dependencies of nested classes.) > >If we're starting with support for a new language then we should >add it properly as a first-class language. Eric and Michael (in Cc) >have been working on this for Swift and C# recently. Likely there >is some overlap in design space. > >-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
