Menu
▾
▴
jazzplusplus-devel
|
From: Pete S. <pst...@gm...> - 2008-05-18 01:57:50
|
Donald, I guess we (I guess that means you since you are the documentation animal ;-) need to generate build instructions for Tex2RTF. Here is how I do it... Change directory to the jazzplusplus/tex2rtf directory and type autoreconf. I usually checkout the entire svn tree, nit just the trunk, so I can get the web and tex2rtf directories. $ autoreconf Create a directory called BuildTex2rtf in parallel with the jazzplusplus directory. This is also in parallel with my Jazz++ build directory. The one we call Build in the instructions. $ cd ../.. $ mkdir BuildTex2rtf Now I run configure and make in the new directory. $ ../jazzplusplus/texx2rtf/configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p . . . config.status: creating src/Makefile config.status: creating src/config.h config.status: executing depfiles commands [pstieber@maggie BuildTex2rtf]$ make 2>&1 | tee BuildLog Making all in src make[1]: Entering directory `/home/pstieber/Jazz++/BuildTex2rtf/src' make all-am make[2]: Entering directory `/home/pstieber/Jazz++/BuildTex2rtf/src' g++ -DHAVE_CONFIG_H -I. -I../../jazzplusplus/tex2rtf/src -Wall -Wno-unknown-pragmas -I/usr/local/wx287/lib/wx/include/gtk2-ansi-release-static-2.8 -I/usr/local/wx287/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXGTK__ -DNDEBUG -O0 -MT htmlutil.o -MD -MP -MF .deps/htmlutil.Tpo -c -o htmlutil.o ../../jazzplusplus/tex2rtf/src/htmlutil.cpp . . . 0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0 -lXinerama -lXxf86vm -lSM -lpng -ljpeg -ltiff -lexpat -lwxregex-2.8 -lz -ldl -lm make[2]: Leaving directory `/home/pstieber/Jazz++/BuildTex2rtf/src' make[1]: Leaving directory `/home/pstieber/Jazz++/BuildTex2rtf/src' make[1]: Entering directory `/home/pstieber/Jazz++/BuildTex2rtf' make[1]: Nothing to be done for `all-am'. make[1]: Leaving directory `/home/pstieber/Jazz++/BuildTex2rtf' We only use the console or non-GUI version of tex2rtf in our builds so I copy BuildTex2rtf/src/tex2rtf to a bin directory under my wxWidgets installation. To be "normal" we should have the user type "make install" as root, or use "sudo make install" for distributions that prefer sudo. Pete BTW, what time zone are you in (+8, +9, +10, or +11)? I'm in the state of California in the U.S.A or -8. |
|
From: D.B. M. <db...@ho...> - 2008-05-18 03:09:50
|
Greets, Pete wrote; ---------------------------------------- > Date: Sat, 17 May 2008 18:57:46 -0700 > Subject: [jazzplusplus-devel] Tex2RTF build > > Donald, > > I guess we (I guess that means you since you are the documentation > animal ;-) need to generate build instructions for Tex2RTF. Here is how > I do it... > > Change directory to the jazzplusplus/tex2rtf directory and type > autoreconf. I usually checkout the entire svn tree, nit just the trunk, > so I can get the web and tex2rtf directories. > > $ autoreconf > > Create a directory called BuildTex2rtf in parallel with the jazzplusplus > directory. This is also in parallel with my Jazz++ build directory. > The one we call Build in the instructions. > > $ cd ../.. > $ mkdir BuildTex2rtf > > Now I run configure and make in the new directory. > > $ ../jazzplusplus/texx2rtf/configure > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... /bin/mkdir -p > . > . > . > config.status: creating src/Makefile > config.status: creating src/config.h > config.status: executing depfiles commands > [pstieber@maggie BuildTex2rtf]$ make 2>&1 | tee BuildLog > Making all in src > make[1]: Entering directory `/home/pstieber/Jazz++/BuildTex2rtf/src' > make all-am > make[2]: Entering directory `/home/pstieber/Jazz++/BuildTex2rtf/src' > g++ -DHAVE_CONFIG_H -I. -I../../jazzplusplus/tex2rtf/src -Wall > -Wno-unknown-pragmas > -I/usr/local/wx287/lib/wx/include/gtk2-ansi-release-static-2.8 > -I/usr/local/wx287/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES > -D__WXGTK__ -DNDEBUG -O0 -MT htmlutil.o -MD -MP -MF .deps/htmlutil.Tpo > -c -o htmlutil.o ../../jazzplusplus/tex2rtf/src/htmlutil.cpp > . > . > . > 0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0 > -lXinerama -lXxf86vm -lSM -lpng -ljpeg -ltiff -lexpat -lwxregex-2.8 -lz > -ldl -lm > make[2]: Leaving directory `/home/pstieber/Jazz++/BuildTex2rtf/src' > make[1]: Leaving directory `/home/pstieber/Jazz++/BuildTex2rtf/src' > make[1]: Entering directory `/home/pstieber/Jazz++/BuildTex2rtf' > make[1]: Nothing to be done for `all-am'. > make[1]: Leaving directory `/home/pstieber/Jazz++/BuildTex2rtf' > Yep, I'll verify this again (did a similar thing here myself a day or two back) and make sure it's all sane... > We only use the console or non-GUI version of tex2rtf in our builds so I > copy BuildTex2rtf/src/tex2rtf to a bin directory under my wxWidgets > installation. ....where exactly did you copy the file to? Here? (relative to linux) /usr/local/wx287/bin > > To be "normal" we should have the user type "make install" as root, or > use "sudo make install" for distributions that prefer sudo. > If it's going to go system-wide, yes, they'll need root_priv or sudo If it's only going to be used at compile time of Jazz++ buld process, it of course doesn't need to go system-wide... In buildingwx, we use su for install in buildingjazz we avoid root_priv Going by your outlay here, the process should be wx->tex2rtf->jazz++ Is the plan to have a *release* tarball with all this automated? I'll guess yes...do we offer users a switch in release form? I'm thinking --enable-tex2rtf builds and installs tex2rtf system wide no switch = build tex2rtf in tree only for the jazz++ doc conversions None of this matters right now, and *YES* I do recognize the stance might be to put tex2rtf out there into the world and I'm all for that.... ..but whenever that word "normal" stares me in the face...well, I have got to speculate what's normal... ;-) > Pete > > BTW, what time zone are you in (+8, +9, +10, or +11)? I'm in the state > of California in the U.S.A or -8. > I'm in the state of Queensland or +10 (but take that with a grain of salt, as I tend to keep rather peculiar hours) Regards, Donald B _________________________________________________________________ Never miss another e-mail with Hotmail on your mobile. http://www.livelife.ninemsn.com.au/article.aspx?id=343869 |
|
From: Pete S. <pst...@gm...> - 2008-05-18 03:58:39
|
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. DM = D.B. Moore DM> ....where exactly did you copy the file to? DM> DM> Here? (relative to linux) /usr/local/wx287/bin Wherever you have wx-config installed. $ which wx-config /usr/local/wx287/bin/wx-config On one machine I'm using... $ which wx-config /home/pstieber/wxBuilds/wx287/bin/wx-config On another. The which command uses you PATH environment variable like bash would. 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 Correct, but the user would need to specify --prefix=... just like in the Jazz++ build. I guess we could have them use TestInstall, but all of our (actually your ;-)) current instructions assume a jazzplusplus/trunk/jazz checkout instead of a jazzplusplus check out that would be required to obtain tex2rtf. We would always require two separate checkouts to achieve this. DM> Going by your outlay here, the process should DM> be wx->tex2rtf->jazz++ Correct. wx is required for tex2rtf. Both wx and tex2rtf are required for Jazz++. DM> Is the plan to have a *release* tarball with all DM> this automated? The release tarball for Jazz++ will not include any tex2rtf stuff other than the help files it generates. We may want to generate a separate tarball for tex2rtf. Tex2RTF really should be a separate project, but I'm having a difficult time working on Jazz++ not alone Tex2RTF... 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. I think the last section of reply helps explain what I'm thinking. DM> I'm in the state of Queensland or +10 (but take that DM> with a grain of salt, as I tend to keep rather peculiar DM> hours) Understood. Now I can pull up something like http://www.worldtimezone.com/ and figure out how "fresh" you are ;-) It's about 9:00 PM here now. BTW, I can't thank you enough for all of the help!!!!! Pete |
|
From: D.B. M. <db...@ho...> - 2008-05-18 13:27:22
|
Greetings,
----------------------------------------
> Date: Sat, 17 May 2008 20:58:35 -0700
> Subject: Re: [jazzplusplus-devel] Tex2RTF build
>
> 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
>
> Correct, but the user would need to specify --prefix=... just like in
> the Jazz++ build. I guess we could have them use TestInstall, but all
> of our (actually your ;-)) current instructions assume a
> jazzplusplus/trunk/jazz checkout instead of a jazzplusplus check out
> that would be required to obtain tex2rtf. We would always require two
> separate checkouts to achieve this.
>
...hmmm. Altering the docs is something that doesn't bother me.
(sometimes I think it's more preferable than changing other things)
That said, I possibly think of how many people actually try an svn
co & build overall....right now like. That answer doesn't matter - what
I'm saying is, once people get used to one way of doing things, it's
best not to throw'em a curve ball....(so we take our time here and
don't confuse them and come up with....'the plan'...| -)
I believe the current reality is quite sane, in as much as the current
instructions for an svn build of jazz++ have established a 'this is
how we do it, keeping the svn build stuff 'outside' the system tree
as much as we can....
....for now in these pre-release days, tex2rtf
should probably stay in this created 'bubble'. This way, one uses
pretty much the same configuration stage options for all things
coming from jazz++ svn....
....however, you're right when you talk about a separate tarball
release of tex2rtf itself. If this were the case, I would ask ;
Does the svn build *really* need a tex2rtf linked against the
custom-wx build libs to give us the functionality (of tex2rtf)
we need (for the jazz++ build process)?
If not, then for sure a release of tex2rtf should be made
available ASAP. Then it really *is* 'normal'...ie; download,
unpack, ./configure --prefix=/usr ; make ; su make install
et_voila. It'll link against user's system wx-libs, be in $PATH
and become a small dependency of jazz++ itself. Of course,
if we can get binary packages of this happening, then all
the better....
Imagining a time when you had the time to make tex2rtf
a project of it's own, that's no big deal to link across
to (if you ever find that time ;-)...and remember, we do
have the tex2rtf page to assert all this to the world, and
something like "going to be a project of it's own one day
when I get time to work on it more, but for now a
functional tarball of this utility is being released on
the sourceforge download area for jazz++'..blabla, works
for me...
> DM> Going by your outlay here, the process should
> DM> be wx->tex2rtf->jazz++
>
> Correct. wx is required for tex2rtf. Both wx and tex2rtf are required
> for Jazz++.
>
> DM> Is the plan to have a *release* tarball with all
> DM> this automated?
>
> The release tarball for Jazz++ will not include any tex2rtf stuff other
> than the help files it generates. We may want to generate a separate
> tarball for tex2rtf. Tex2RTF really should be a separate project, but
> I'm having a difficult time working on Jazz++ not alone Tex2RTF...
>
....Uh-huh, and release pkgs are likewise...and of course,
the source tarball has everything except possibly tex2rtf,
(which is available separately), right? (this is me lobbying
my own position & requirements ;-)
> 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.
>
> I think the last section of reply helps explain what I'm thinking.
>
> DM> I'm in the state of Queensland or +10 (but take that
> DM> with a grain of salt, as I tend to keep rather peculiar
> DM> hours)
>
> Understood. Now I can pull up something like
>
> http://www.worldtimezone.com/
>
> and figure out how "fresh" you are ;-)
>
> It's about 9:00 PM here now.
>
> BTW, I can't thank you enough for all of the help!!!!!
>
It's my pleasure, I'm glad you like my input...output.. ;-)
Regards,
Donald B
_________________________________________________________________
Are you paid what you're worth? Find out: SEEK Salary Centre
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau%2Fcareer%2Dresources%2Fsalary%2Dcentre%2F%3Ftracking%3Dsk%3Ahet%3Asc%3Anine%3A0%3Ahot%3Atext&_t=764565661&_r=OCT07_endtext_salary&_m=EXT
|
|
From: Pete S. <pst...@gm...> - 2008-05-18 16:30:49
|
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 |
|
From: D.B. M. <db...@ho...> - 2008-05-18 15:15:26
|
Greets, ---------------------------------------- > Date: Sat, 17 May 2008 18:57:46 -0700 > Subject: [jazzplusplus-devel] Tex2RTF build > > Donald, > > I guess we (I guess that means you since you are the documentation > animal ;-) need to generate build instructions for Tex2RTF. Here is how > I do it... > > Change directory to the jazzplusplus/tex2rtf directory and type > autoreconf. I usually checkout the entire svn tree, nit just the trunk, > so I can get the web and tex2rtf directories. > > $ autoreconf > > Create a directory called BuildTex2rtf in parallel with the jazzplusplus > directory. This is also in parallel with my Jazz++ build directory. > The one we call Build in the instructions. > > $ cd ../.. > $ mkdir BuildTex2rtf > > Now I run configure and make in the new directory. > > $ ../jazzplusplus/texx2rtf/configure > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... /bin/mkdir -p > . > . Just confirming the build here on my custom 64bit thing (no 32bit_compat) ....seems to compile and work fine... Also fine on debian-4.0r1 on x86_32 Onwards ever onwards... Regards, Donald B _________________________________________________________________ Are you paid what you're worth? Find out: SEEK Salary Centre http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau%2Fcareer%2Dresources%2Fsalary%2Dcentre%2F%3Ftracking%3Dsk%3Ahet%3Asc%3Anine%3A0%3Ahot%3Atext&_t=764565661&_r=OCT07_endtext_salary&_m=EXT |
|
From: Pete S. <pst...@gm...> - 2008-05-18 16:34:48
|
DM = D.B. Moore PS = Pete Stieber PS>> I guess we (I guess that means you since PS>> you are the documentation animal ;-) need PS>> to generate build instructions for Tex2RTF. PS>> Here is how I do it... <snip> DM> Just confirming the build here on my custom DM> 64bit thing (no 32bit_compat) ....seems to DM> compile and work fine... DM> DM> Also fine on debian-4.0r1 on x86_32 For the record, my successful test was on Fedora 8 with an x86_64 kernel (2.6.24.5-85.fc8.x86_64) using GCC 4.1.2 20070925 (Red Hat 4.1.2-33). Pete |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X