Csound Csound-dev Csound-tekno Search About

Re: [Cs-dev] Multi port midi proposal

Date2005-11-19 17:43
FromVictor Lazzarini
SubjectRe: [Cs-dev] Multi port midi proposal
In relation to environment variables, mainly OPCODEDIR and
OPCODEDIR64, I am thinking that on OSX, I will probably
suggest a hardcoding of these directories. The reason is
that,
unlik on Windows and lInux, there is no way of setting a
system-wide
environment variable. It is possible to do it for the
terminal, but not
for Apps launched by Finder/Acqua. Is there any problem with
doing this?

Victor


>
> Besides what needs to be distributed, we need to agree on
> where they get installed, and how they binaries for the
> different binaries subversions are labelled.  I do not
> think that distributing csound5 like csound4 (all binaries
> in top dir) will be sufficient because of all the plugins.
>
> I like how Istvan's mkpackage.py file organized everything
> into directories:
>
> bin - binaries
> lib - libraries
> lib/csound/plugins - 32 bit plugins (float)
> lib/csound/plugins64 - 64 bit plugins (double)
> doc - documentation
>
> As it follows Linux conventions.  (Not sure where doc
> above should be installed; for linux should be
> /usr/share/csound ?).
>
> Now, pd's installation follows a very similar structure
> but usually keeps it all in a pd root directory (i.e.
> pd/bin, pd/lib, etc.).  On Linux, I think it follows that
> everything is installed into /usr/lib/pd and symlinks for
> binaries to /usr/bin (not on Linux now to check).  This
> format is maintained for Windows too.
>
> I think the directory structure is very important so that
> setting environment variables across platforms will look
> very similar for the distribution, which could help cut
> down new user mistakes.  The above structure should be
> satisfactory for all platforms as far as I can see.
>
> I think that binaires for x86_64 should be separated into
> a separate package. I see no reason for one person to want
> both unless they're testing something, and they could just
> install the two packages if they want both.  I think this
> matches how binaries for the 32bit and 64bit processors
> are normally distributed for Linux (please correct me if
> I'm incorrect).
>
> steven
>
>
> On 11/19/05, jpff@codemist.co.uk 
> > wrote: My draft distribution is a standalone system.
> >
> > Four sub-versions, for float/double; 32bit/64bit
> hardware >
> > Binaries:
> >         brkpt,cs,csb64enc,cscore,csound,cvanal,dnoise
> >         ,envext,extract,extractor, het_export,het_import
> >         ,hetro,linseg,lpanal,lpc_export,lpc_import
> ,makecsd, mixer,pvanal,pvlook,scale,scot,scsort,sdif2ad
> ,srconv,tabdes >
> > Opcodes+Modules: (all lib*.so files)
> >
> > Libraries:
> >         libcsound, liblo, libportaudio, libsndfile
> >
> > Manual in HTML:
> >
> > This is aimed at exactly the csound4 distributions so we
> > can start the migration of existing use-styles to
> csound5. >
> >
> > ==John ffitch
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by the JBoss Inc.  Get
> > Certified Today Register for a JBoss Training Course.
> > Free Certification Exam for All Training Attendees
> > Through End of 2005. For more info visit:
> >
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
> > _______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> >
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.  Get
> Certified Today Register for a JBoss Training Course.
> Free Certification Exam for All Training Attendees Through
> End of 2005. For more info visit:
> http://ads.osdn.com/?ad_idv28&alloc_id845&opclick
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2005-11-19 18:15
FromDavid Akbari
SubjectRe: [Cs-dev] Multi port midi proposal
On Nov 19, 2005, at 12:43 PM, Victor Lazzarini wrote:

> In relation to environment variables, mainly OPCODEDIR and
> OPCODEDIR64, I am thinking that on OSX, I will probably
> suggest a hardcoding of these directories. The reason is
> that,
> unlik on Windows and lInux, there is no way of setting a
> system-wide
> environment variable. It is possible to do it for the
> terminal, but not
> for Apps launched by Finder/Acqua. Is there any problem with
> doing this?
>
> Victor

By manually altering a relevant .cshrc file in addition to copying this 
to a file named ~/.MacOSX/environment.plist





     OPCODEDIR
     /Users/daveakbari/CVS/csound5
     OPCODEDIR64
     /Users/daveakbari/CVS/csound5
     INCDIR
     /Users/daveakbari/CODE/_UDO
     SFDIR
     /loops



users should be able to set environment variables for the Terminal and 
the Aqua environment separately. In doing so it almost seems like a 
system wide environment variable, but I have yet to find documentation 
on this technique as implemented in Mac OS 10.4 Tiger (I don't use this 
OS at present but it's sitting in my drawer.) I find this to be the 
standard practice for setting the environment variables for the 
csoundapi~ object for Pd.

What is the equivalent for ~/.MacOSX/environment.plist in Tiger ?? Is 
it ~/.profile ?


-David



-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2005-11-19 18:24
FromIstvan Varga
SubjectRe: [Cs-dev] Multi port midi proposal
Victor Lazzarini wrote:

> In relation to environment variables, mainly OPCODEDIR and
> OPCODEDIR64, I am thinking that on OSX, I will probably
> suggest a hardcoding of these directories. The reason is
> that, unlik on Windows and lInux, there is no way of setting a
> system-wide environment variable. It is possible to do it for the
> terminal, but not for Apps launched by Finder/Acqua. Is there any
 > problem with doing this?

Do you mean ignoring OPCODEDIR/OPCODEDIR64 completely on OS X,
or having an absolute path instead of "." as the default ?
Also, what directories do you suggest ?


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net