If you have never heard of Phing before, I suggest you visit the getting started page.

The phplint task will syntax check one or more files containing php source code. All it requires is a list of files.

Here is the sample build.xml file:

<?xml version="1.0"?>
<project name="MyPhpProject" basedir="." default="lint">
    <target name="lint">
        <phplint>
            <fileset dir=".">
                <include name="*.php" />
                <include name="**/*.php" />
            </fileset>
        </phplint>
    </target>
</project>

We created a target called "lint". This will allow us to call lint from the command line. In that target we specify a single task: phplint. The phplint task will call "php -l" on each filename provided. Within that task we specify a fileset type. The fileset type is what provides the phplint task with files to syntax check.

The fileset type can get pretty complex. I have intentionally kept it simple. The dir attribute on the fileset type specifies the current directory. The first include element will match any file with a ".php" extension in the current directory. The second include element will match any file with a ".php" extension in a sub-directory.

Here is a visualization of how the fileset is working:

app/
    build.xml <-- will not match
    foo.php <-- will match
    bar.php <-- will match
    includes/
        baz.php <-- will match
        special/
            special1.php <-- will match
            special2.inc <-- will not match
    sql/
        schema.sql <-- will not match

Place the build.xml file at the root of your applications directory structure. You can move it to another folder after you get more comfortable with phing.

From the command line run: phing lint