What do people think of this addition to the format of filesets? Look at
the <sources> element of the <build> task. The <build> task is my own
private task. I thought it would be better to include the entire buildfile
in full so that if people could come up with a better syntax they could edit
the file.
Basically I'm trying to make this file as human readable as possible so
people that aren't familiar with XML can see what is going on and add/remove
some files from a project for a specific platform.
The files are delimited by whitespace. If your file has a space character
you should use the <includes name="xxx"/> format. Another option is to
delimit the filesnames by \n so that spaces could occur in the filename (or
path if the full path was used to include the file).
-- included build file --
<?xml version="1.0"?>
<project>
<target name="build">
<build type="Library" name="system">
<includepath>
${platform}
cmn
</includepath>
<sources>
<!-- include platform dependent code -->
<includes name="${platform}/*.cpp"/>
<!-- depending on the platform include shared common source
files -->
<includes if="${platform} == win">
win/*.cpp
cmn/detectself.cpp
cmn/emms.cpp
cmn/lowtimer.cpp
cmn/setenv.cpp
cmn/startup.cpp
cmn/systemlock.cpp
</includes>
<includes if="${platform} == ps2">
ps2/*.cpp
cmn/setkbdstate.cpp
cmn/startup.cpp
cmn/systemlock.cpp
</includes>
<includes if="${platform} == xbox">
xbox/*.cpp
cmn/setenv.cpp
cmn/setkbdstate.cpp
cmn/startup.cpp
cmn/systemlock.cpp
</includes>
</sources>
</build>
</target>
</project>
-------------------------------------------------------
In remembrance
www.osdn.com/911/
_______________________________________________
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
