561
edits
Difference between revisions of "TODO"
→Build System: We got a tool which creates MSVC project files out of configure / module.mk now (not in perl though ;-).
Eriktorbjorn (talk | contribs) (Clarified Broken Sword 2 issue a bit.) |
(→Build System: We got a tool which creates MSVC project files out of configure / module.mk now (not in perl though ;-).) |
||
| Line 84: | Line 84: | ||
* Add test(s) for backend usability in the configure script. | * Add test(s) for backend usability in the configure script. | ||
* Add an install target to the Makefile - Copy binary, install manpage, add menu items, install README. See also patch #891909 (Gnome/KDE .desktop file) | * Add an install target to the Makefile - Copy binary, install manpage, add menu items, install README. See also patch #891909 (Gnome/KDE .desktop file) | ||
* Investigate whether switching to [http://www.cmake.org CMake] or [http://www.scons.org SCons] or some other cross platform configuration environment would work for us. Potential advantage: Less effort to maintain and extend the build system, automatic generation of various kinds of project files (Makefiles, and project files for MSVC, XCode, Eclipse, KDevelop ...). Potential drawback: Problems with the customized build systems of our various ports. However, the latter might actually be improved by using CMake or SCons -- hard to say without tests. | * Investigate whether switching to [http://www.cmake.org CMake] or [http://www.scons.org SCons] or some other cross platform configuration environment would work for us. Potential advantage: Less effort to maintain and extend the build system, automatic generation of various kinds of project files (Makefiles, and project files for MSVC, XCode, Eclipse, KDevelop ...). Potential drawback: Problems with the customized build systems of our various ports. However, the latter might actually be improved by using CMake or SCons -- hard to say without tests. | ||