<a href="http://gforge.inria.fr/scm/?group_id=12">here</a>.
You won't find any <tt>configure</tt> and a few other things
-(<tt>Makefile.in</tt>'s, documentation, ...) will be missing as
-well. The reason for that is that all these files have to be
-regenerated using the latest versions of <tt>autoconf</tt>,
-<tt>automake</tt> (1.9) and <tt>doxygen</tt>. To generate the
-<tt>configure</tt> and the <tt>Makefile.in</tt>'s, you just have to
-launch the <tt>bootstrap</tt> command that resides in the top of the
-source tree. Then just follow the instructions of Section
-\ref faq_compiling.
+(<tt>Makefile.in</tt>'s, documentation, ...) will be missing as well. The
+reason for that is that all these files have to be regenerated using the
+latest versions of <tt>autoconf</tt>, <tt>libtool</tt>, <tt>automake</tt>
+(>1.9) and <tt>doxygen</tt> (>1.4). To generate the <tt>configure</tt> and
+the <tt>Makefile.in</tt>'s, you just have to launch the <tt>bootstrap</tt>
+command that resides in the top of the source tree. Then just follow the
+instructions of Section \ref faq_compiling.
We insist on the fact that you really need the latest versions of
autoconf and automake. Doing this step on exotic architectures/systems
- It was really boring to write 25,000 entries in the deployment file, so I wrote
a little script <tt>examples/gras/tokenS/make_deployment.pl</tt>, which you may
- want to adapt to your case.
+ want to adapt to your case. You could also think about hijacking
+ the SURFXML parser (have look at \ref faq_flexml_bypassing).
- The deployment file became quite big, so I had to do what is in the FAQ
entry \ref faq_flexml_limit
