Re: [jazzplusplus-devel] Any thoughts on this ?

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

RV = Robert Vogel
RV> Thank you for your excellent directions.
RV> wxwidgets downloaded and compiled clean
RV> (the log is huge, but a quick scan shows
RV> no apparent problems.)

Glad to hear that was a success.

RV> Also I configured, compiled, and installed
RV> Jazz++. It can open screens, it talks to
RV> alsa. it drives a softsynth, and displays
RV> are looking reaonable.

Excellent!

RV> For me it is not configured quite right
RV> though. I put in a path for install of
RV> /usr/local/bin,

So does this mean you added --prefix=/usr/local/bin to you configure line?

If you did, you don't need to do this.  The default installation 
location is /usr/local and any binary files will automatically be placed 
in /usr/local/bin.  If you specify --prefix, this is considered the 
top-level installation directory for all architecture independent files, 
and subdirectories will be created under this directory.

You can specify a particular location for the executable files, but that 
configure option is --bindir.  If you want them in /usr/local/bin, you 
don't have to specify anything because this is the default.  To see all 
of the options available to you when running configure, type

$ ./configure --help

This is standard operating procedure for the configure file generated by 
the autotools, so you can use what you are learning here for any package 
that uses the autotools.

Since the code "isn't ready for prime time" I usually install the code 
in a build directory that is in parallel with my source tree.  Under my 
home directory I create a subdirectory called Jazz++.  Under that 
directory I checkout the entire subversion repository.  This creates a 
jazzplusplus directory under Jazz++.  In parallel to (at the same level 
as) the jazzplusplus directory I create a directory called "Build".

I run configure and make from the Build directory.  This allows me to 
remove everything under the Build directory without worrying that I have 
removed something vital.

My configure command usually looks like the following:

../jazzplusplus/trunk/jazz/configure 
--prefix=/home/pstieber/Jazz++/TestInstall --enable-alsa --enable-sequencer2

That should all be on one line.  Also note that if you only check out 
the trunk, the path to configure would be shorter...

../jazz/configure --prefix=/home/pstieber/Jazz++/TestInstall 
--enable-alsa --enable-sequencer2

Notice the --prefix option.  Instead of using the default value 
(/usr/local) I let the installer create yet another directory in 
parallel with Build and the source directory.  If you do the same, you 
can run "make install" without root privilege and it will install the 
code under your home directory.  The binary (jazz) should end up in 
$HOME/Jazz++/TestInstall/bin.  If not, something is wrong.

You will also notice a directory called $HOME/Jazz++/TestInstall/share 
that contains the configuration files.  If my guess is correct and you 
you set the prefix option to /usr/local/bin you may also have a 
/usr/local/bin/share directory that should be in /usr/local/share.

Since this install is under your directory structure, you have 
permission to remove it, making an uninstall a snap.  Simply add the bin 
directory to your PATH and you can you it from it from any directory.

RV> but it actually put a
RV> binary in /usr/local/bin/bin.

I hope my guess above and explanation will help you with this.

RV> I copied the binary into /usr/local/bin and ran it.
RV> It seems to have a problem locating its own
RV> configuration file.

I haven't put much effort into this yet, but I thought I had some code 
in Jazz++ to prompt you for the location of the configuration file. 
This information is stored in a Jazz++ rc file that should find the 
configuration information on successive invocations (if it hasn't moved).

RV> (A  couple of screen shots attached. Don't know if
RV> they'll get through on this list.)

I administer the list and approved your post so they should have ;-)

RV> Looks like a good start.

Thanks and thanks for trying the build.  Look for more subversion updates.

Pete