|
Notes |
|
|
(0028863)
|
|
Nils Gladitz
|
|
2012-03-08 10:03
|
|
The workaround that works for me is creating a file with the source file names like this:
set(_JAVA_SOURCE_FILELIST "${CMAKE_JAVA_CLASS_OUTPUT_PATH}/java_source_filelist_${_TARGET_NAME}")
string(REPLACE ";" "\n" _NEWLINE_SEPARATED_SOURCE_FILES "${_JAVA_COMPILE_FILES}")
file(WRITE ${_JAVA_SOURCE_FILELIST} "${_NEWLINE_SEPARATED_SOURCE_FILES}")
And then replacing "${_JAVA_COMPILE_FILES}" with "@${_JAVA_SOURCE_FILELIST}" in the custom command.
I'm not sure if this still works well with spaces in the source file paths though (my guess would be that it doesn't). |
|
|
|
(0030375)
|
|
David Cole
|
|
2012-08-11 21:09
|
|
Sending old, never assigned issues to the backlog.
(The age of the bug, plus the fact that it's never been assigned to anyone means that nobody is actively working on it...)
If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^]
It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing.
|
|
|
|
(0033556)
|
|
Graham Markall
|
|
2013-07-16 10:44
|
|
I've recently bumped up against this bug and produced the attached patch to fix it locally. I've tested this on OS X 10.8, Windows 7, Debian Wheezy and CentOS 6.4.
I tried to ensure that spaces in paths are dealt with by enclosing each file in quotes, and separating files with a newline, and this appears to work from my testing.
Please let me know if there are any changes/additions to the patch necessary. |
|
|
|
(0033559)
|
|
Brad King
|
|
2013-07-16 13:39
|
|
|
0001-Use-argfile-for-java-files-to-compile.-13028.patch (2,060) 2013-07-16 10:40