Hi Charles,
> A.
>
> > I think you're missing the tools/build/v2/tools/types directory.
> > Can you go to tools/build/v2 and run "cvs update -d"? Or, if you're using
>
> graphical CVS client, find an option which causes it to create directories
> during update.
>
> I thought that my WinCVS client always had the -d option enabled but I was
> wrong. It has to be set before every pass.
Wow. Nice UI design, I believe ;-)
> I now have the types directory
> (and a lot more that I was missing).
>
> B.
> The fop.html page, Configuring Apache FOP for PostScript/PDF Output, should
> specify the file for which bjam is looking. If I just give it my root
> directory, c:/fop-0.20.5rc2/, it complains. It seems to be satisfied with
> C:/fop-0.20.5rc2/build, which holds only the fop.jar file. Is that
> correct?
Does not seem so. You need to specify the full path to the fop.bat script.
Here's my version of the docs:
<title>Configuring PDF and PostScript Output</title>
<para>The be able to generate PDF and PostScript output, you have to
install two tools:
<itemizedlist>
<listitem><simpara>A Java interpreter, available at <ulink
url="http://java.sun.com"/>.</simpara></listitem>
<listitem><simpara>Apache FOP, available at <ulink
url="http://xml.apache.org/fop/download.html"/>. Version 0.20.4 seems to be
most stable.</simpara></listitem>
</itemizedlist>
</para>
<para>Install the Java interpreter and then unpack Apache FOP
directory. Top level directory of the FOP tool should contain a main
script called <filename>fop.sh</filename> on Unix and
<filename>fop.bat</filename> on Windows. You need to specify the
location of that script and Java location to Boost.Build. Add the
following to your <filename>user-config.jam</filename> or
<filename>site-config.jam</filename>:
<programlisting>using fop :
FOP_COMMAND : JAVA_HOME ;</programlisting>
replacing
<code>FOP_COMMAND</code> with the full path to the FOP main script, and
replacing <code>JAVA_HOME</code> with the directory where Java is
installed. If the <envar>JAVA_HOME</envar> environment variable is
already set, you don't need to specify it above.
Doug, OK to commit this?
BTW, the PostScript generations was broken -- it generated PDF instead. I've
fixed this.
> C.
> Now I can get a little farther with bjam. I invoke it from my Boost CVS
> root directory as follows:
>
> bjam --v2 -d5 >bjlog
>
> I added the -d5 to generate more diagnostics. I think there's a problem
> with date_time/build. Here are the last 20 lines of the bjlog file (out of
> a total of 32,100 lines):
>
> C:/boostcvs/tools/build/v2/util\regex.jam:22:>>>>|>>>>|>>>>|>>>>|>>>>|>>>>|
>>>>> MATCH ^(.*)(/)(.*) : libs
> C:/boostcvs/tools/build/v2/util\regex.jam:22:>>>>|>>>>|>>>>|>>>>|>>>>|>>>>|
>>>>> set match =
> C:/boostcvs/tools/build/v2/util\path.jam:418:>>>>|>>>>|>>>>|>>>>|>>>>|>>>>|
>>> sequence.join libs date_time build : \
> C:/boostcvs/tools/build/v2/util\sequence.jam:137:>>>>|>>>>|>>>>|>>>>|>>>>|>
>>>>|>
>
> >>> set joint ?=
>
> C:/boostcvs/tools/build/v2/util\path.jam:418:>>>>|>>>>|>>>>|>>>>|>>>>|>>>>|
>>> set result = libs\date_time\build
> C:/boostcvs/tools/build/v2/build\targets.jam:794:>>>>|>>>>|>>>>|>>>>|>>>>|>
>>> CHECK_IF_FILE libs\date_time\build
> C:/boostcvs/tools/build/v2/build\targets.jam:794: in
> object(file-reference)@1.exists
> rule CHECK_IF_FILE unknown in module object(file-reference)@1.
This mean you have to rebuild bjam from the most up-to-date sources and use
the rebuilt version. CHECK_IF_FILE is a recently introduced function in bjam.
- Volodya
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Boost-docs mailing list
[email protected]
Unsubscribe and other administrative requests:
https://lists.sourceforge.net/lists/listinfo/boost-docs
