The GNU pattern (which is what automake is all about) would be csound5,
csound 5.01, etc. symbolically linked to csound. Windows doesn't have
symbolic links, and it's inconvenient to keep renaming and changing paths,
so that's why I made it csound instead of csound5.

----- Original Message ----- 
From: "steven yi" 
To: "Csound Developers Discussion List" 
Sent: Monday, September 13, 2004 12:26 AM
Subject: [CSOUND-DEV:5307] Re: Sconstruct updated


> Hi John,
>
> Thanks very much for this information.  I think the SConstruct file as I
> have it in the last version pretty much goes along with this directory
> organization.  The one thing I am doing, however, is installing into
> /usr/local/lib/csound and not /usr/local/lib/csound5.  What would
> everyone prefer?
>
> Thanks,
> steven
>
>
>
> John D. Ramsdell wrote:
>
> >For a package with the name csound5, automake generates Makefiles with
> >the following definitions:
> >
> >exec_prefix = ${prefix}
> >
> >bindir = ${exec_prefix}/bin
> >sbindir = ${exec_prefix}/sbin
> >libexecdir = ${exec_prefix}/libexec
> >datadir = ${prefix}/share
> >sysconfdir = ${prefix}/etc
> >sharedstatedir = ${prefix}/com
> >localstatedir = ${prefix}/var
> >libdir = ${exec_prefix}/lib
> >infodir = ${prefix}/info
> >mandir = ${prefix}/man
> >includedir = ${prefix}/include
> >pkgdatadir = $(datadir)/csound5
> >pkglibdir = $(libdir)/csound5
> >pkgincludedir = $(includedir)/csound5
> >
> >With these definitions, you can support multiple architectures by using
> >the definition:
> >
> >exec_prefix = ${prefix}/$(arch)
> >
> >For each arch to be installed.
> >
> >You should put header files in $(pkgincludedir), documentation often
> >goes into $(pkgdatadir), and dynamically loaded opcodes go in
> >$(pkglibdir).  The directory $(libexecdir) is where executable go that
> >are only invoked by library code.  I think I said this directory was a
> >good place for opcodes, but I was wrong.
> >
> >Once again, this is what automake does, but I'm not sure how universal
> >these definitions are.
> >
> >John
> >
> >
> >
> >
> >
>

"Michael Gogins"  writes:

> The GNU pattern (which is what automake is all about) would be csound5,
> csound 5.01, etc. symbolically linked to csound. Windows doesn't have
> symbolic links, and it's inconvenient to keep renaming and changing paths,
> so that's why I made it csound instead of csound5.

If you expect no one to install both Csound 4 and Csound 5 at the same
time, just call your package csound.  The only reason one might
consider using csound5 is to avoid this kind of conflict.

John