2005/11/3, Alex Ionescu ionucu@videotron.ca:
You should just tell us what kind of information they contain so that we can update the XML file. It will be perfectly auto-generated afterwards.
Well, I don't doubt you would be able to to so. But I think the effort to implement such all the required features into the XML files and rbuild isn't worth it. I will show you what "information" I thought of:
- In the Explorer workspace the source files are organized into a handfull of subfolders, e.g. "utility", "resources", "taskbar", "doc", ...
- In the "doc" folder there are files which are not to be compiled - text files like "changes.txt" merely for documentation purpouse.
- The work space contains more than one project file: Some in VC internal format, some just calling external Makefiles - even a Jamfile.
- The project file contains different configurations: Debug/Release configurations, UNICODE/ANSI configurations. There is also a configuration I am using to build Explorer together with Wine's libraries, such as shell32.dll and comctl32.dll, and link to them instead of Windows' DLLs.
- explorer.xml and the genersated ReactOS Makefiles define different compiler options, like "-D_ROS_" and "-__WINDRES__", which my native VC project files don't need.
Regards,
Martin