Re: [jazzplusplus-devel] Tex2RTF build

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

D.B. Moore
PS =Pete Stieber
PS>>>> We only use the console or non-GUI version of
PS>>>> tex2rtf in our builds so I copy
PS>>>> BuildTex2rtf/src/tex2rtf to a bin directory
PS>>>> under my wxWidgets installation.

... < snip>...

PS>>>> To be "normal" we should have the user type
PS>>>> "make install" as root, or use "sudo make install"
PS>>>> for distributions that prefer sudo.

DM>>> If it's going to go system-wide, yes, they'll need
DM>>> root_priv or sudo
DM>>>
DM>>> If it's only going to be used at compile time
DM>>> of Jazz++ buld process, it of course doesn't
DM>>> need to go system-wide...
DM>>>
DM>>> In buildingwx, we use su for install
DM>>> in buildingjazz we avoid root_priv

PS>> Correct, but the user would need to specify
PS>> --prefix=... just like in the Jazz++ build.
PS>> I guess we could have them use TestInstall,
PS>> but all of our (actually your ;-)) current
PS>> instructions assume a jazzplusplus/trunk/jazz
PS>> checkout instead of a jazzplusplus check out
PS>> that would be required to obtain tex2rtf.
PS>>  We would always require two separate checkouts
PS>> to achieve this.

DM> ...hmmm. Altering the docs is something that
DM> doesn't bother me. (sometimes I think it's more
DM> preferable than changing other things)
DM>
DM> That said, I possibly think of how many people
DM> actually try an svn co & build overall....right
DM> now like. That answer doesn't matter - what
DM> I'm saying is, once people get used to one way
DM> of doing things, it's best not to throw'em a
DM> curve ball....(so we take our time here and
DM> don't confuse them and come up with....'the plan'...| -)
DM>
DM> I believe the current reality is quite sane,
DM> in as much as the current instructions for an
DM> svn build of jazz++ have established a 'this is
DM> how we do it, keeping the svn build stuff
DM> 'outside' the system tree as much as we can....
DM>      ....for now in these pre-release days, tex2rtf
DM> should probably stay in this created 'bubble'.
DM> This way, one uses pretty much the same
DM> configuration stage options for all things
DM> coming from jazz++ svn....
DM>
DM> ....however, you're right when you talk about
DM> a separate tarball release of tex2rtf itself.
DM> If this were the case, I would ask ;
DM>
DM> Does the svn build *really* need a tex2rtf linked
DM> against the custom-wx build libs to give us the
DM> functionality (of tex2rtf) we need (for the jazz++
DM> build process)?

Any working tex2rtf will do.  If it is the version currently in the 
wxWidgets svn tree built against a stock wxWidgets build, it will work too.

DM> If not, then for sure a release of tex2rtf
DM> should be made available ASAP.
DM> Then it really *is* 'normal'...ie; download,
DM> unpack, ./configure --prefix=/usr ; make ; su make install
DM> et_voila. It'll link against user's system wx-libs, be in $PATH
DM> and become a small dependency of jazz++ itself. Of course,
DM> if we can get binary packages of this happening, then all
DM> the better....
DM>
DM> Imagining a time when you had the time to make tex2rtf
DM> a project of it's own, that's no big deal to link across
DM> to (if you ever find that time ;-)...and remember, we do
DM> have the tex2rtf page to assert all this to the world, and
DM> something like "going to be a project of it's own one day
DM> when I get time to work on it more, but for now a
DM> functional tarball of this utility is being released on
DM> the sourceforge download area for jazz++'..blabla, works
DM> for me...

DM>>> Going by your outlay here, the process should
DM>>> be wx->tex2rtf->jazz++

PS>> Correct.  wx is required for tex2rtf.  Both wx
PS>> and tex2rtf are required for Jazz++.

DM> Is the plan to have a *release* tarball with all
DM> this automated?

Hey Kevin,

Are you interested in making a tex2rtf distribution for us?  It would be 
a good test prior to attempting this for Jazz++.  I can learn from your 
expertise in this arena.

PS>> The release tarball for Jazz++ will not include
PS>> any tex2rtf stuff other than the help files it
PS>> generates.  We may want to generate a separate
PS>> tarball for tex2rtf.  Tex2RTF really should be
PS>> a separate project, but I'm having a difficult
PS>> time working on Jazz++ not alone Tex2RTF...

DM> ....Uh-huh, and release pkgs are likewise...and
DM> of course, the source tarball has everything except
DM> possibly tex2rtf, (which is available separately),
DM> right? (this is me lobbying my own position &
DM> requirements  ;-)

Correct.

DM>>> I'll guess yes...do we offer users a switch in release
DM>>> form? I'm thinking --enable-tex2rtf builds and installs
DM>>> tex2rtf system wide.

PS>> I think the last section of reply helps explain what I'm thinking.

Pete