FpcExt provides modified content for the FPC/compiler directory. So you must have a working FPC installation first (snapshot, SVN checkout...).
Using GitGUI you invoke it from the FPC directory and select Clone Existing Repository. Then specify the FpcExt repository and the target directory, e.g. for the docs:
Source Location: git://fpcext.git.sourceforge.net/gitroot/fpcext/docs
Target Directory: docs
Then click on Clone to create and download the documentation to the new FPC/docs directory.
This procedure only works for new or empty target directories, so you'll have to delete or rename the FPC/compiler directory before cloning the ...fpcext/compiler repository into directory compiler.
Using the commandline (GitBash on Windows), cd into the FPC directory and
$ git clone git://fpcext.git.sourceforge.net/gitroot/fpcext/compiler compiler
It may be possible to create the clone somewhere else, and then copy or move the .git folder into the FPC/compiler directory (untested, at your own risk).
Make sure that the FPC/compiler directory contains files, or checkout one of the branches. The master branch is intended to hold the unmodified SVN revisions of FPC, so this branch should always be usable.
Since only the compiler directory is affected by FpcExt, the usual build procedures for FPC apply. E.g. cd into the FPC directory and invoke
$ make clean all
Before playing with the compiler sources, you should create (and checkout) your own branch.
It may happen that newer FPC versions are not fully compatible with the FpcExt compiler version. In this case either the FpcExt compiler must be updated, or an older FPC version should be used as the base installation.
The compiler documentation in FPDoc format requires that all documented units are part of a project or package. For that purpose a newparser.lpk package has been create in the docs directory. For this package the docs folder must reside in the compiler directory, i.e. FPC/compiler/docs. This will most probably change in the next version.
Anonymous