Csound Csound-dev Csound-tekno Search About

Re: [Cs-dev] Multi port midi proposal

Date2005-11-18 21:54
FromVictor Lazzarini
SubjectRe: [Cs-dev] Multi port midi proposal
I think we need to put up a list of items that will go in
the distribution. That way we can concentrate on making
the installers.

Victor

>
> Hear, hear!  Let us have a release of 5.0 in days or
> weeks.  Certainly this year.  I would like to see
> concentration on installers.
>
> My interest tends to Csound as a stand-alone, and by
> installer is aimed at that on Linux and Mac.
> ==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_id=7628&alloc_id=16845&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2005-11-19 10:17
Fromjpff@codemist.co.uk
SubjectRe: [Cs-dev] Multi port midi proposal
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

Date2005-11-19 10:26
FromIstvan Varga
SubjectRe: [Cs-dev] Multi port midi proposal
jpff@codemist.co.uk wrote:

> My draft distribution is a standalone system.
> 
> Four sub-versions, for float/double; 32bit/64bit hardware

I assume the 32/64 bit hardware applies only to the x86_64 platform,
so everywhere else there are only two sub-versions ? Also, did you
have a look at the script installer/linux/mkpackage.py that generates
an installable directory structure ?



-------------------------------------------------------
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 11:34
Fromjpff@codemist.co.uk
SubjectRe: [Cs-dev] Multi port midi proposal
>>>>> "Istvan" == Istvan Varga  writes:

 Istvan> jpff@codemist.co.uk wrote:
 >> My draft distribution is a standalone system.
 >> 
 >> Four sub-versions, for float/double; 32bit/64bit hardware

 Istvan> I assume the 32/64 bit hardware applies only to the x86_64
 Istvan> platform,

I was only talking about Linux on Intel/AMD.  Does not the same apply
to OSX/ppc?

 Istvan> so everywhere else there are only two sub-versions ? Also, did you
 Istvan> have a look at the script installer/linux/mkpackage.py that generates
 Istvan> an installable directory structure ?

I glanced at it, but it seemed to be attempting a different task.  I
took it that it was a another way of stopping me contributing, so I
just stopped work on csound.

==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

Date2005-11-19 12:16
FromIstvan Varga
SubjectRe: [Cs-dev] Multi port midi proposal
jpff@codemist.co.uk wrote:

>  Istvan> so everywhere else there are only two sub-versions ? Also, did you
>  Istvan> have a look at the script installer/linux/mkpackage.py that generates
>  Istvan> an installable directory structure ?
> 
> I glanced at it, but it seemed to be attempting a different task.  I
> took it that it was a another way of stopping me contributing, so I
> just stopped work on csound.

OK, I removed the scripts now. There is no reason to stop working
on Csound.


-------------------------------------------------------
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 17:23
FromSteven Yi
SubjectRe: [Cs-dev] Multi port midi proposal
AttachmentsNone  

Date2005-11-19 18:03
FromIstvan Varga
SubjectRe: [Cs-dev] Multi port midi proposal
Steven Yi wrote:

> I like how Istvan's mkpackage.py file organized everything into directories:

I removed mkpackage.py and related files as they seem to duplicate
the functionality of John's installer for Linux (not sure what directory
layout that uses, though).

> bin - binaries
> lib - libraries
> lib/csound/plugins - 32 bit plugins (float)
> lib/csound/plugins64 - 64 bit plugins (double)
> doc - documentation

Here is a more detailed description of the directory structure I
used:

/usr/lib/pd/extra/
   PD object (csoundapi~.pd_linux, links against libcsound.so.5.1)
/usr/lib/python/
   Python wrapper (csnd.py, csnd.pyc, csnd.pyo)
/usr/lib/python/lib-dynload/
   Python wrapper (_csnd.so, symlink to /usr/local/lib/lib_csnd.so)
/usr/local/bin/
   frontends (most of these are simple shell scripts that call
   the binaries in /usr/local/lib/csound/bin/ after setting the
   required environment variables)
/usr/local/include/csound/
   header files
/usr/local/lib/csound/bin/
   the actual binaries (csound and csound64)
/usr/local/lib/csound/lib/
   "private" shared libraries for use by Csound (e.g. FLTK)
/usr/local/lib/csound/plugins/
   single precision plugin libraries
/usr/local/lib/csound/plugins64/
   double precision plugin libraries
/usr/local/lib/csound/xmg/
   string database files
/usr/local/lib/
   Csound API libraries:
     lib_csnd.so (interfaces, links against libcsound64.so.5.1)
     libcsound64.a
     libcsound64.so (symlink to libcsound64.so.5.1)
     libcsound64.so.5.1
     libcsound.a
     libcsound.so (symlink to libcsound.so.5.1)
     libcsound.so.5.1
   Note that the '1' in the shared library version is the API
   major version, i.e. any incompatible API change will result
   in a new library name like libcsound.so.5.2 and so on.
/usr/local/share/doc/csound/
   documentation (the HTML manual could be a subdirectory of this
   as 'manual')

I solved the issue of setting environment variables by creating
simple shell scripts that set up the environment and then run
Csound. For example, /usr/local/bin/cvanal is actually:

   #!/bin/sh

   export OPCODEDIR="/usr/local/lib/csound/plugins"
   export CSSTRNGS="/usr/local/lib/csound/xmg"

   if [ "${LD_LIBRARY_PATH}" == "" ] ; then
       export LD_LIBRARY_PATH="/usr/local/lib/csound/lib"
   else
       export LD_LIBRARY_PATH="/usr/local/lib/csound/lib:${LD_LIBRARY_PATH}"
   fi

   exec "/usr/local/lib/csound/bin/csound" -U cvanal "$@"

However, this still requires the user to set the environment
variables if the extension modules for PD and Python are used,
rather than the standard command line frontends.

Of course, the directory structure may vary depending on platform,
and quite likely also distribution. For example, the libraries
required by Csound (FLTK, PortAudio, etc.) are expected to be
installed to the same directory as the binaries on Windows, and
the Python and PD paths are likely to vary depending on Linux
distribution.


-------------------------------------------------------
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:49
Fromjpff@codemist.co.uk
SubjectRe: [Cs-dev] Installation systems
Another issue: not every user has root access.  that is why the
installer I drafted allowed for a totally different layout under user
control.  I was intending adding a small FLTK frontend to allow for
GUI installation, especially for the non-techy.  I was expecting to
use the same system on OSX.
==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