Re: [jazzplusplus-devel] online help build system update

[Pete S. <pst...@gm...>]

DM = D.B. Moore
PS>> jazzplusplus/trunk/jazz/doc.  On my x86_64 Fedora 8
PS>> box, if I run "make" in the referenced directory, it
PS>> will generate HTML help files you can view with your
PS>> favorite web browser and a jazz.pdf file.
PS>>
PS>> You will need certain tools available to make this
PS>> work.  For the HTML help you will need the tex2rtf
PS>> code that is provided with wxWidgets.

DM> I did forget to mention that 'tex2rtf' doesn't
DM> seem to get built here as part of the wx-2.8.7
DM> build instructions. I have no idea if that's an
DM> expected result (it may well be)....

If you don't have tex2rtf, how did you build the HTML help?

tex2rtf will probably be the topic of a separate thread, but it can be 
generated from the wxWidgets distribution.  Unfortunately, due to the 
way wxWidgets is built for Jazz++, there are some potential problems.

PS>> For PDF generation, you will need a LaTeX
PS>> installation and the pdflatex converter.

DM> Using tetex under linux (which supplies the tool
DM> 'pdftex'), jazz.pdf generation also works fine.
DM> The tool 'pdftex' is also maintained separately
DM> (http://www.pdftex.org) and seems more current
DM> than the version shipping with tetex.
DM>
DM> Both versions work.

Maybe I can check for existence of pdflatex of pdftex in the build system.

PS>> Would you like me to send you the current PDF
PS>> file in a private email?

DM> A kind offer, however I'm eager to checkout
DM> as much of source build process as is possible
DM> here - test, test and test again...

PS>> Since you can build the HTML help using
PS>> "make html" feel free to start editing jazz.tex
PS>> and send me patches.  Replacement screen shots
PS>> are welcome too.  We may end up with different
PS>> sets of screen shots for each platform and I
PS>> can change the Makefile to build the docs for
PS>> different platforms.  I'm going to make one
PS>> commit to jazz.tex before I go to bed, but
PS>> after that it's "open season" for you.

DM> ....now, where did I put my hunting cap?...  (;

PS>> I would prefer many smaller patches than one
PS>> big patch, and please include a note
PS>> summarizing the changes you made.  I'll use
PS>> this in commit message and give you credit.
PS>> The first change you should make is make
PS>> yourself a coauthor.  I changed the original
PS>> author names because they have been out of
PS>> the picture for over 8 years.  The commit
PS>> messages will look like...
PS>>
PS>> "Applied a patch provided by Donald B. Moore.
PS>> Your description here.
PS>> A description of anything I changed here."

DM> All understood, I'll keep my submissions
DM> small and descriptive ...

Thanks.

PS>> I see you signed up for the
PS>> jazzplusplus-updates list.  Excellent!

DM> I try to please.

DM> I just need to clarify something here -- when you say;
DM>
DM> 'in your svn working'
DM>
DM> I construe this as ;
DM>
DM> 'in your svn working directory'
DM>
DM> Is that correct?

Yes.  Sorry about the missing noun an the related confusion.  I just 
committed a fix for this one.  You update your web source tree (i.e. 
your svn web working directory) and svn will merge the changes with any 
you have made.

Pete