From: D.B. M. <db...@ho...> - 2008-11-11 07:10:02
|
> Date: Mon, 10 Nov 2008 18:44:01 -0800 > From: pstieber > To: jazzplusplus-devel > Subject: Re: [jazzplusplus-devel] SF.net SVN: jazzplusplus:[620] web/htdocs/buildingtex2rtf/index.php > > <<snip>> > > > Pete said; > I caused the problem by worrying about a potential user that may not > have root access on a machine. I faced this situation at work when a > colleague attempted to install wxWidgets at a user site and didn't have > root access. I copied the instructions from a work web site I generated. > > The autotools and autoconf in particular default to /usr/local as the > installation location. For wxWidgets, I like the idea of specifying > /usr/local/wx{version} so that multiple versions can be loaded and I can > wipe out the entire install by removing that directory. Otherwise I > would have to remove particular files in /usr/local/bin, /usr/local/lib, > /usr/local/include... and this can be a pain if the user has other codes > installed in these directories. I'm not sure in wxWidgets has a "make > uninstall" command, but even if it does, I don't want to rely on it as > the user may erase their build directory. > This is all entirely sane, especially as many distros ship wx standard > > So for now, I think I'll assume everyone that is building Jazz++ is a > developer, or helping me debug problems and change the instructions to... > > 1. Assume the developer has root access and if they don't assume they > are smart enough to deal with the "--prefix=..." configure option. > 2. Use --prefix-/usr/local/wx289 for wxWidgets and have the user build > and install both release and debug versions of the wxWidgets library. > 3. Use the default prefix (/usr/local) for tex2rtf. The only files that > get installed are tex2rtf and tex2rtf_gui in the /usr/local/bin > directory and this is usually included in the users path. This code > will use the release version of wxWidgets. I don't want to deal with > tex2rtf issues at this point. > 4. Give instructions for both a debug and release build of Jazz++ and > the developer can choose. > > Does this sound OK? > Sounds good to me, my only gripe was that the given instructions for tex2rtf placed the binaries outside $PATH and broke the jazz build instructions, nothing more. I also presume (as opposed to assume) that anyone building jazz++ is a developer/tester or helper - what I assume here is someone will prove that presumption to be wrong ;-) > I'd really prefer to work on the code instead of these instructions. I > still don't have it recording MIDI :-( Indeed....if you want me to do anything, just aim me... I haven't checked record functions yet -- I do know the bank/patch selection isn't working for me... Regards, Don _________________________________________________________________ Time for change? Find your ideal job with SEEK. http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau%2F%3Ftracking%3Dsk%3Atl%3Ask%3Anine%3A0%3Ahottag%3Achange&_t=757263783&_r=SEEK_tagline&_m=EXT |