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

[D.B. M. <db...@ho...>]

Greetings,

Pete -- I've posted this reply to jazzplusplus-user as well,
just to help remove any confusion generated there.

----------------------------------------
> Date: Sun, 11 May 2008 13:49:37 -0700

> 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.
>

Sorry, I should have been a bit clearer about this. Here's the detail ;

In your previous posting about this, you signified that the 'tex2rtf'
utility was distributed with the wxwidget tarball. My stock installation
of wx is version 2.8.4, however 'tex2rtf' wasn't in $PATH. I'd only
just updated wx a week or so ago, so I still had the source/build tree
handy. Checking that was when I discovered 'tex'2rtf' hadn't been
built (in my 2.8.4 wx tree) - nor had it been built in the non-stock
wx-2.8.7 build used for jazz++ ; apparently the cause is common.

I chose to sort this on my *stock* wx installation (to make tex2rtf
available systemwide, not just for jazz++). The full path to tex2rtf in
the wx source tree is -- wxGTK-2.8.4/utils/tex2rtf/

Changing to that directory, issuing make && make install was how
I ended up with a working tex2rtf. Strangely, it had all been previously
configured, all the Makefiles were present, but for whatever reason
the build process skips right over the utils section and why is something
I would need look closer at ....if you want me to that is. Let me know...


> 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.
>

Yeah, I think you'll have to. AFAICT 'pdflatex' is not specific to linux -
the equivalence is 'pdftex' to the best of my knowledge. It probably
make sense to include a check in configure for both these tool sets
(including tex2rtf), and like other projects I've seen issue a warning
at the end of configure 'documentation will not be built - please install
<> if you wish to build a local copy of the documentation'
....blabla...

I should also point out, although the 'tetex' distribution does include
it's own (working) version of 'pdftex', the variant downloaded from
http://www.pdftex.org is meant to replace the one distributed in
tetex.


> 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
>

No problem...I guess that's what we're supposed to do though - confuse each
other then clear up that confusion before the user audience finds themselves confused...

I should have patches for the rest of the web docs sorted over the next
few days.

Regards,

Donald B

>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> jazzplusplus-devel mailing list
> jaz...@li...
> https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel

_________________________________________________________________
Never miss another e-mail with Hotmail on your mobile.
http://www.livelife.ninemsn.com.au/article.aspx?id=343869