Thanks to the developers for this bold new step in Csound, with arrays,
parallelization and, in the future, I understand, user-definable data
types!  I guess that the arrays are of floats, not arrays of arrays -
although two dimensional arrays are supported.

I downloaded:

http://sourceforge.net/projects/csound/files/csound6/Csound6.00/Csound6.00.tar.gz

and found this documentation of the new features for version 6:

  Release_Notes/Version_6.00
  readme-csound6.txt
  readme-csound6-complete.txt

Is there any other documentation I should be reading?

I haven't attempted to build it on Linux (Debian 8.0 64 bit).  Are there
any instructions for this?

I imagine there are a large number of options for what facilities to
build into Csound, which version of Csound to build in terms of creating
a VST plugin or whatever.  I just want a command-line non-real-time
Linux executable.

There is a "How_to_Build_Csound_on_Windows.doc" and
/android/BUILDING_ON_ANDROID.txt , neither of which I haven't looked at.

 - Robin

Hi Robin,

In the past on Debian, I built like so:

1. sudo apt-get build-dep csound
2. sudo apt-get install cmake
3. cd /dir/where/csound6/folder/is
4. mkdir cs6make
5. cd cs6make
6. cmake ../csound6
7. make -j6
8. sudo make install

I'm working from memory so if you try it and have any problems, please
feel free to reply and I'm sure myself or others will be happy to
assist.

Thanks!
steven


On Fri, Jul 12, 2013 at 11:58 PM, Robin Whittle  wrote:
> Thanks to the developers for this bold new step in Csound, with arrays,
> parallelization and, in the future, I understand, user-definable data
> types!  I guess that the arrays are of floats, not arrays of arrays -
> although two dimensional arrays are supported.
>
> I downloaded:
>
> http://sourceforge.net/projects/csound/files/csound6/Csound6.00/Csound6.00.tar.gz
>
> and found this documentation of the new features for version 6:
>
>   Release_Notes/Version_6.00
>   readme-csound6.txt
>   readme-csound6-complete.txt
>
> Is there any other documentation I should be reading?
>
> I haven't attempted to build it on Linux (Debian 8.0 64 bit).  Are there
> any instructions for this?
>
> I imagine there are a large number of options for what facilities to
> build into Csound, which version of Csound to build in terms of creating
> a VST plugin or whatever.  I just want a command-line non-real-time
> Linux executable.
>
> There is a "How_to_Build_Csound_on_Windows.doc" and
> /android/BUILDING_ON_ANDROID.txt , neither of which I haven't looked at.
>
>  - Robin
>
>
>
>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>

Hi Steven,

Thanks for your reply.  I did this on a directory which I created by
un-targzipping the "Csound6.00.tar.gz" file as a mortal user.  Doing so
as root creates directories which the mortal user can't write to.

> In the past on Debian, I built like so:
> 
> 1. sudo apt-get build-dep csound
> 2. sudo apt-get install cmake
> 3. cd /dir/where/csound6/folder/is
> 4. mkdir cs6make
> 5. cd cs6make

All was well until this step:

> 6. cmake ../csound6

    CMake Error: The source directory "/x/y/z/Csound6.00/csound6" does
    not exist.

I looked around and tried this instead:

  cmake ../CMakeLists.txt

This produced signs of intelligent life and no errors.  The final line was:

-- Build files have been written to: /x/y/z/Csound6.00

The file which is created is:

  /x/y/z/Csound6.00/Makefile

I am not sure what purpose there is in changing to this new directory
"csmake", since nothing is written there.

This step needs to be done from /x/y/z/Csound6.00/ :

> 7. make -j6

This produced a lot of happy looking results.  There is an executable:

  /x/y/z/Csound6.00/csound

> 8. sudo make install

This generates a bunch of lines, including the destination of the plain
Csound binary I am interested in:

-- Installing: /usr/local/bin/csound

The text of this can be found in /x/y/z/Csound6.00/install_manifest.txt

Now I think I should be able to run it, at least to get some help text.
 From the /examples directory I run "csound" - and get:

   csound: error while loading shared libraries: libcsound64.so.6.0:
   cannot open shared object file: No such file or directory

Yet the first line of install_manifest.txt is:

  /usr/local/lib/libcsound64.so.6.0

and indeed there is such a file there.  After some Googling I found this
mailing list thread:

  http://csound.1045644.n5.nabble.com/5-19-for-Ubuntu-td5720035.html

from 2013-02-11 in which David Seidel wrote (regarding Ubuntu - I am
using Debian on which Ubuntu is in some way based):

> So I had to add /usr/local/lib to /etc/ld.so.conf and run
> "sudo ldconfig". Problem solved.

My file "/etc/ld.so.conf" contains just:

  include /etc/ld.so.conf.d/*.conf

and my directory /etc/ld.so.conf.d/ contained two files with the
following contents:

  libc.conf

     # libc default configuration
     /usr/local/lib

  x86_64-linux-gnu.conf

     # Multiarch support
     /lib/x86_64-linux-gnu
     /usr/lib/x86_64-linux-gnu

My /usr/local/lib contained only:

/csound/
/python2.6/
/python2.7/
 _csnd6.so
 csnd6.jar
 csnd6.py
 csoundapi~.pd_linux
 lib_jcsound6.so
 libcsnd.so -> libcsnd.so.6.0
 libcsnd.so.6.0
 libcsound64.so -> libcsound64.so.6.0
 libcsound64.so.6.0
 luaCsnd6.so

This all looks good to me, but I only rarely think about library paths.
 All I had to do was run "sudo ldconfig" and then I could run the
command "csound".

I am not sure why this is the case.  It is a fresh install of 64 bit
Debian 8.0 on a Core 2 Duo machine.  The abovementioned files are not at
all related to Csound.  Perhaps this command should have been run as
part of the installation, but wasn't.

Now, from the examples directory, I ran:

  csound xanadu

and it produced a xanadu.wav file which Wavelab (Windows) recognized as
a stereo 44.1kHz 32 bit floating point file and played fine.

It never ceases to amaze me how Csound can turn a few kbytes of text
into an intriguing piece of music - in this case a minute, calculated in
8.5 seconds (Core 2 Duo E6750 2.67MHz 65nm 4MB cache).   But this is
with ksmps = 100, meaning krate is 441Hz.  There was some rattly high
distortion, mainly in the first few seconds and 45 to 47 seconds.

I create a copy of this as xanadu-k-14700.csd and changed the ksmps line
to "3".  This took 22 seconds to cook and sounds perfect to me.

I made a similarly modified version of "hommage.csd" with two lines changed:

kr = 14700
ksmps = 3

This took 39 seconds to produce test.wav, 2 minutes 25 seconds, which
sounded fine to me.

I haven't investigated any further, but the build has clearly been
successful.  Thanks!

   - Robin

Hi Robin,

I should have clarified about step 3: cmake in general promotes using
out-of-source builds, so that the build is done completely outside of
the src root.  This is not mandatory though.  I tend to do have
folders like:

/x/y/z/csound/csound6
/x/y/z/csound/cs6make
/x/y/z/csound/cs6xcode
/x/y/z/csound/cs6ninja

etc. for different build generators. (The default is Makefile, but you
can generate builds for other build systems.) So that step was meant
to go into the /x/y/z/csound folder and create cs6make.

As for /usr/local/lib not being on the ld path by default, I'm not
really sure why that didn't happen. I've seen that happen on occasion
of the years with various Linux installations, but I haven't come
across it in a while.

I'm very glad though that you have a working Csound6 system, built from source!

All best,
steven



On Mon, Jul 15, 2013 at 10:57 AM, Robin Whittle  wrote:
> Hi Steven,
>
> Thanks for your reply.  I did this on a directory which I created by
> un-targzipping the "Csound6.00.tar.gz" file as a mortal user.  Doing so
> as root creates directories which the mortal user can't write to.
>
>> In the past on Debian, I built like so:
>>
>> 1. sudo apt-get build-dep csound
>> 2. sudo apt-get install cmake
>> 3. cd /dir/where/csound6/folder/is
>> 4. mkdir cs6make
>> 5. cd cs6make
>
> All was well until this step:
>
>> 6. cmake ../csound6
>
>     CMake Error: The source directory "/x/y/z/Csound6.00/csound6" does
>     not exist.
>
> I looked around and tried this instead:
>
>   cmake ../CMakeLists.txt
>
> This produced signs of intelligent life and no errors.  The final line was:
>
> -- Build files have been written to: /x/y/z/Csound6.00
>
> The file which is created is:
>
>   /x/y/z/Csound6.00/Makefile
>
> I am not sure what purpose there is in changing to this new directory
> "csmake", since nothing is written there.
>
> This step needs to be done from /x/y/z/Csound6.00/ :
>
>> 7. make -j6
>
> This produced a lot of happy looking results.  There is an executable:
>
>   /x/y/z/Csound6.00/csound
>
>> 8. sudo make install
>
> This generates a bunch of lines, including the destination of the plain
> Csound binary I am interested in:
>
> -- Installing: /usr/local/bin/csound
>
> The text of this can be found in /x/y/z/Csound6.00/install_manifest.txt
>
> Now I think I should be able to run it, at least to get some help text.
>  From the /examples directory I run "csound" - and get:
>
>    csound: error while loading shared libraries: libcsound64.so.6.0:
>    cannot open shared object file: No such file or directory
>
> Yet the first line of install_manifest.txt is:
>
>   /usr/local/lib/libcsound64.so.6.0
>
> and indeed there is such a file there.  After some Googling I found this
> mailing list thread:
>
>   http://csound.1045644.n5.nabble.com/5-19-for-Ubuntu-td5720035.html
>
> from 2013-02-11 in which David Seidel wrote (regarding Ubuntu - I am
> using Debian on which Ubuntu is in some way based):
>
>> So I had to add /usr/local/lib to /etc/ld.so.conf and run
>> "sudo ldconfig". Problem solved.
>
> My file "/etc/ld.so.conf" contains just:
>
>   include /etc/ld.so.conf.d/*.conf
>
> and my directory /etc/ld.so.conf.d/ contained two files with the
> following contents:
>
>   libc.conf
>
>      # libc default configuration
>      /usr/local/lib
>
>   x86_64-linux-gnu.conf
>
>      # Multiarch support
>      /lib/x86_64-linux-gnu
>      /usr/lib/x86_64-linux-gnu
>
> My /usr/local/lib contained only:
>
> /csound/
> /python2.6/
> /python2.7/
>  _csnd6.so
>  csnd6.jar
>  csnd6.py
>  csoundapi~.pd_linux
>  lib_jcsound6.so
>  libcsnd.so -> libcsnd.so.6.0
>  libcsnd.so.6.0
>  libcsound64.so -> libcsound64.so.6.0
>  libcsound64.so.6.0
>  luaCsnd6.so
>
> This all looks good to me, but I only rarely think about library paths.
>  All I had to do was run "sudo ldconfig" and then I could run the
> command "csound".
>
> I am not sure why this is the case.  It is a fresh install of 64 bit
> Debian 8.0 on a Core 2 Duo machine.  The abovementioned files are not at
> all related to Csound.  Perhaps this command should have been run as
> part of the installation, but wasn't.
>
> Now, from the examples directory, I ran:
>
>   csound xanadu
>
> and it produced a xanadu.wav file which Wavelab (Windows) recognized as
> a stereo 44.1kHz 32 bit floating point file and played fine.
>
> It never ceases to amaze me how Csound can turn a few kbytes of text
> into an intriguing piece of music - in this case a minute, calculated in
> 8.5 seconds (Core 2 Duo E6750 2.67MHz 65nm 4MB cache).   But this is
> with ksmps = 100, meaning krate is 441Hz.  There was some rattly high
> distortion, mainly in the first few seconds and 45 to 47 seconds.
>
> I create a copy of this as xanadu-k-14700.csd and changed the ksmps line
> to "3".  This took 22 seconds to cook and sounds perfect to me.
>
> I made a similarly modified version of "hommage.csd" with two lines changed:
>
> kr = 14700
> ksmps = 3
>
> This took 39 seconds to produce test.wav, 2 minutes 25 seconds, which
> sounded fine to me.
>
> I haven't investigated any further, but the build has clearly been
> successful.  Thanks!
>
>    - Robin
>

hi steven -

i am wondering how we can put an instruction of this together, to which 
we can point people? this would be very necessary and useful.

i suggest to put this in the media wiki. there are already some for 
csound5 in
http://sourceforge.net/apps/mediawiki/csound/index.php?title=Csound_development

i personally think that "Csound development" is not the best title for 
instructions like this. i suggest to create a new chapter "Building Csound".

best -

	joachim



Am 15.07.2013 17:46, schrieb Steven Yi:
> Hi Robin,
>
> I should have clarified about step 3: cmake in general promotes using
> out-of-source builds, so that the build is done completely outside of
> the src root.  This is not mandatory though.  I tend to do have
> folders like:
>
> /x/y/z/csound/csound6
> /x/y/z/csound/cs6make
> /x/y/z/csound/cs6xcode
> /x/y/z/csound/cs6ninja
>
> etc. for different build generators. (The default is Makefile, but you
> can generate builds for other build systems.) So that step was meant
> to go into the /x/y/z/csound folder and create cs6make.
>
> As for /usr/local/lib not being on the ld path by default, I'm not
> really sure why that didn't happen. I've seen that happen on occasion
> of the years with various Linux installations, but I haven't come
> across it in a while.
>
> I'm very glad though that you have a working Csound6 system, built from source!
>
> All best,
> steven
>
>
>
> On Mon, Jul 15, 2013 at 10:57 AM, Robin Whittle  wrote:
>> Hi Steven,
>>
>> Thanks for your reply.  I did this on a directory which I created by
>> un-targzipping the "Csound6.00.tar.gz" file as a mortal user.  Doing so
>> as root creates directories which the mortal user can't write to.
>>
>>> In the past on Debian, I built like so:
>>>
>>> 1. sudo apt-get build-dep csound
>>> 2. sudo apt-get install cmake
>>> 3. cd /dir/where/csound6/folder/is
>>> 4. mkdir cs6make
>>> 5. cd cs6make
>>
>> All was well until this step:
>>
>>> 6. cmake ../csound6
>>
>>      CMake Error: The source directory "/x/y/z/Csound6.00/csound6" does
>>      not exist.
>>
>> I looked around and tried this instead:
>>
>>    cmake ../CMakeLists.txt
>>
>> This produced signs of intelligent life and no errors.  The final line was:
>>
>> -- Build files have been written to: /x/y/z/Csound6.00
>>
>> The file which is created is:
>>
>>    /x/y/z/Csound6.00/Makefile
>>
>> I am not sure what purpose there is in changing to this new directory
>> "csmake", since nothing is written there.
>>
>> This step needs to be done from /x/y/z/Csound6.00/ :
>>
>>> 7. make -j6
>>
>> This produced a lot of happy looking results.  There is an executable:
>>
>>    /x/y/z/Csound6.00/csound
>>
>>> 8. sudo make install
>>
>> This generates a bunch of lines, including the destination of the plain
>> Csound binary I am interested in:
>>
>> -- Installing: /usr/local/bin/csound
>>
>> The text of this can be found in /x/y/z/Csound6.00/install_manifest.txt
>>
>> Now I think I should be able to run it, at least to get some help text.
>>   From the /examples directory I run "csound" - and get:
>>
>>     csound: error while loading shared libraries: libcsound64.so.6.0:
>>     cannot open shared object file: No such file or directory
>>
>> Yet the first line of install_manifest.txt is:
>>
>>    /usr/local/lib/libcsound64.so.6.0
>>
>> and indeed there is such a file there.  After some Googling I found this
>> mailing list thread:
>>
>>    http://csound.1045644.n5.nabble.com/5-19-for-Ubuntu-td5720035.html
>>
>> from 2013-02-11 in which David Seidel wrote (regarding Ubuntu - I am
>> using Debian on which Ubuntu is in some way based):
>>
>>> So I had to add /usr/local/lib to /etc/ld.so.conf and run
>>> "sudo ldconfig". Problem solved.
>>
>> My file "/etc/ld.so.conf" contains just:
>>
>>    include /etc/ld.so.conf.d/*.conf
>>
>> and my directory /etc/ld.so.conf.d/ contained two files with the
>> following contents:
>>
>>    libc.conf
>>
>>       # libc default configuration
>>       /usr/local/lib
>>
>>    x86_64-linux-gnu.conf
>>
>>       # Multiarch support
>>       /lib/x86_64-linux-gnu
>>       /usr/lib/x86_64-linux-gnu
>>
>> My /usr/local/lib contained only:
>>
>> /csound/
>> /python2.6/
>> /python2.7/
>>   _csnd6.so
>>   csnd6.jar
>>   csnd6.py
>>   csoundapi~.pd_linux
>>   lib_jcsound6.so
>>   libcsnd.so -> libcsnd.so.6.0
>>   libcsnd.so.6.0
>>   libcsound64.so -> libcsound64.so.6.0
>>   libcsound64.so.6.0
>>   luaCsnd6.so
>>
>> This all looks good to me, but I only rarely think about library paths.
>>   All I had to do was run "sudo ldconfig" and then I could run the
>> command "csound".
>>
>> I am not sure why this is the case.  It is a fresh install of 64 bit
>> Debian 8.0 on a Core 2 Duo machine.  The abovementioned files are not at
>> all related to Csound.  Perhaps this command should have been run as
>> part of the installation, but wasn't.
>>
>> Now, from the examples directory, I ran:
>>
>>    csound xanadu
>>
>> and it produced a xanadu.wav file which Wavelab (Windows) recognized as
>> a stereo 44.1kHz 32 bit floating point file and played fine.
>>
>> It never ceases to amaze me how Csound can turn a few kbytes of text
>> into an intriguing piece of music - in this case a minute, calculated in
>> 8.5 seconds (Core 2 Duo E6750 2.67MHz 65nm 4MB cache).   But this is
>> with ksmps = 100, meaning krate is 441Hz.  There was some rattly high
>> distortion, mainly in the first few seconds and 45 to 47 seconds.
>>
>> I create a copy of this as xanadu-k-14700.csd and changed the ksmps line
>> to "3".  This took 22 seconds to cook and sounds perfect to me.
>>
>> I made a similarly modified version of "hommage.csd" with two lines changed:
>>
>> kr = 14700
>> ksmps = 3
>>
>> This took 39 seconds to produce test.wav, 2 minutes 25 seconds, which
>> sounded fine to me.
>>
>> I haven't investigated any further, but the build has clearly been
>> successful.  Thanks!
>>
>>     - Robin
>>
>
>
> Send bugs reports to the Sourceforge bug tracker
>              https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>

Hi Joachim,

Using a Wiki sounds good to me.  The issue now is that Sourceforge
used to offer Mediawiki as a separate package you could install. I
think now it is only available if you had already installed it, and a
number of times they had mentioned discontinuing the wiki in favor of
their new built-in one.

There's a support ticket here that has further information:

https://sourceforge.net/p/forge/site-support/4238/

There was some chatter on the dev list about which wiki to use a while
back.  I ended up writing the information for how to use Homebrew to
install Csound on OSX, and had put it on the built-in wiki.  The main
page for the built-in wiki is at:

https://sourceforge.net/p/csound/wiki/Home/

If you select "Browse Pages" in the left hand bar, it will show a
linke to the Homebrew OSX page:

https://sourceforge.net/p/csound/wiki/Homebrew%20OSX/

I think we should migrate our wiki information from Mediawiki to the
built-in platform. Perhaps we should put this Debian building
information there?

Thanks!
steven

On Mon, Jul 15, 2013 at 12:46 PM, joachim heintz  wrote:
> hi steven -
>
> i am wondering how we can put an instruction of this together, to which we
> can point people? this would be very necessary and useful.
>
> i suggest to put this in the media wiki. there are already some for csound5
> in
> http://sourceforge.net/apps/mediawiki/csound/index.php?title=Csound_development
>
> i personally think that "Csound development" is not the best title for
> instructions like this. i suggest to create a new chapter "Building Csound".
>
> best -
>
>         joachim
>
>
>
> Am 15.07.2013 17:46, schrieb Steven Yi:
>>
>> Hi Robin,
>>
>> I should have clarified about step 3: cmake in general promotes using
>> out-of-source builds, so that the build is done completely outside of
>> the src root.  This is not mandatory though.  I tend to do have
>> folders like:
>>
>> /x/y/z/csound/csound6
>> /x/y/z/csound/cs6make
>> /x/y/z/csound/cs6xcode
>> /x/y/z/csound/cs6ninja
>>
>> etc. for different build generators. (The default is Makefile, but you
>> can generate builds for other build systems.) So that step was meant
>> to go into the /x/y/z/csound folder and create cs6make.
>>
>> As for /usr/local/lib not being on the ld path by default, I'm not
>> really sure why that didn't happen. I've seen that happen on occasion
>> of the years with various Linux installations, but I haven't come
>> across it in a while.
>>
>> I'm very glad though that you have a working Csound6 system, built from
>> source!
>>
>> All best,
>> steven
>>
>>
>>
>> On Mon, Jul 15, 2013 at 10:57 AM, Robin Whittle  wrote:
>>>
>>> Hi Steven,
>>>
>>> Thanks for your reply.  I did this on a directory which I created by
>>> un-targzipping the "Csound6.00.tar.gz" file as a mortal user.  Doing so
>>> as root creates directories which the mortal user can't write to.
>>>
>>>> In the past on Debian, I built like so:
>>>>
>>>> 1. sudo apt-get build-dep csound
>>>> 2. sudo apt-get install cmake
>>>> 3. cd /dir/where/csound6/folder/is
>>>> 4. mkdir cs6make
>>>> 5. cd cs6make
>>>
>>>
>>> All was well until this step:
>>>
>>>> 6. cmake ../csound6
>>>
>>>
>>>      CMake Error: The source directory "/x/y/z/Csound6.00/csound6" does
>>>      not exist.
>>>
>>> I looked around and tried this instead:
>>>
>>>    cmake ../CMakeLists.txt
>>>
>>> This produced signs of intelligent life and no errors.  The final line
>>> was:
>>>
>>> -- Build files have been written to: /x/y/z/Csound6.00
>>>
>>> The file which is created is:
>>>
>>>    /x/y/z/Csound6.00/Makefile
>>>
>>> I am not sure what purpose there is in changing to this new directory
>>> "csmake", since nothing is written there.
>>>
>>> This step needs to be done from /x/y/z/Csound6.00/ :
>>>
>>>> 7. make -j6
>>>
>>>
>>> This produced a lot of happy looking results.  There is an executable:
>>>
>>>    /x/y/z/Csound6.00/csound
>>>
>>>> 8. sudo make install
>>>
>>>
>>> This generates a bunch of lines, including the destination of the plain
>>> Csound binary I am interested in:
>>>
>>> -- Installing: /usr/local/bin/csound
>>>
>>> The text of this can be found in /x/y/z/Csound6.00/install_manifest.txt
>>>
>>> Now I think I should be able to run it, at least to get some help text.
>>>   From the /examples directory I run "csound" - and get:
>>>
>>>     csound: error while loading shared libraries: libcsound64.so.6.0:
>>>     cannot open shared object file: No such file or directory
>>>
>>> Yet the first line of install_manifest.txt is:
>>>
>>>    /usr/local/lib/libcsound64.so.6.0
>>>
>>> and indeed there is such a file there.  After some Googling I found this
>>> mailing list thread:
>>>
>>>    http://csound.1045644.n5.nabble.com/5-19-for-Ubuntu-td5720035.html
>>>
>>> from 2013-02-11 in which David Seidel wrote (regarding Ubuntu - I am
>>> using Debian on which Ubuntu is in some way based):
>>>
>>>> So I had to add /usr/local/lib to /etc/ld.so.conf and run
>>>> "sudo ldconfig". Problem solved.
>>>
>>>
>>> My file "/etc/ld.so.conf" contains just:
>>>
>>>    include /etc/ld.so.conf.d/*.conf
>>>
>>> and my directory /etc/ld.so.conf.d/ contained two files with the
>>> following contents:
>>>
>>>    libc.conf
>>>
>>>       # libc default configuration
>>>       /usr/local/lib
>>>
>>>    x86_64-linux-gnu.conf
>>>
>>>       # Multiarch support
>>>       /lib/x86_64-linux-gnu
>>>       /usr/lib/x86_64-linux-gnu
>>>
>>> My /usr/local/lib contained only:
>>>
>>> /csound/
>>> /python2.6/
>>> /python2.7/
>>>   _csnd6.so
>>>   csnd6.jar
>>>   csnd6.py
>>>   csoundapi~.pd_linux
>>>   lib_jcsound6.so
>>>   libcsnd.so -> libcsnd.so.6.0
>>>   libcsnd.so.6.0
>>>   libcsound64.so -> libcsound64.so.6.0
>>>   libcsound64.so.6.0
>>>   luaCsnd6.so
>>>
>>> This all looks good to me, but I only rarely think about library paths.
>>>   All I had to do was run "sudo ldconfig" and then I could run the
>>> command "csound".
>>>
>>> I am not sure why this is the case.  It is a fresh install of 64 bit
>>> Debian 8.0 on a Core 2 Duo machine.  The abovementioned files are not at
>>> all related to Csound.  Perhaps this command should have been run as
>>> part of the installation, but wasn't.
>>>
>>> Now, from the examples directory, I ran:
>>>
>>>    csound xanadu
>>>
>>> and it produced a xanadu.wav file which Wavelab (Windows) recognized as
>>> a stereo 44.1kHz 32 bit floating point file and played fine.
>>>
>>> It never ceases to amaze me how Csound can turn a few kbytes of text
>>> into an intriguing piece of music - in this case a minute, calculated in
>>> 8.5 seconds (Core 2 Duo E6750 2.67MHz 65nm 4MB cache).   But this is
>>> with ksmps = 100, meaning krate is 441Hz.  There was some rattly high
>>> distortion, mainly in the first few seconds and 45 to 47 seconds.
>>>
>>> I create a copy of this as xanadu-k-14700.csd and changed the ksmps line
>>> to "3".  This took 22 seconds to cook and sounds perfect to me.
>>>
>>> I made a similarly modified version of "hommage.csd" with two lines
>>> changed:
>>>
>>> kr = 14700
>>> ksmps = 3
>>>
>>> This took 39 seconds to produce test.wav, 2 minutes 25 seconds, which
>>> sounded fine to me.
>>>
>>> I haven't investigated any further, but the build has clearly been
>>> successful.  Thanks!
>>>
>>>     - Robin
>>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>              https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>

hi steven -

thanks for the detailed info. i actually did not know this, and a agree 
it should be the best to use sf's own wiki. we should definitely try to 
collect here usable build instructions, and invite people to update them 
by themselves.

best -

	joachim


Am 15.07.2013 20:56, schrieb Steven Yi:
> Hi Joachim,
>
> Using a Wiki sounds good to me.  The issue now is that Sourceforge
> used to offer Mediawiki as a separate package you could install. I
> think now it is only available if you had already installed it, and a
> number of times they had mentioned discontinuing the wiki in favor of
> their new built-in one.
>
> There's a support ticket here that has further information:
>
> https://sourceforge.net/p/forge/site-support/4238/
>
> There was some chatter on the dev list about which wiki to use a while
> back.  I ended up writing the information for how to use Homebrew to
> install Csound on OSX, and had put it on the built-in wiki.  The main
> page for the built-in wiki is at:
>
> https://sourceforge.net/p/csound/wiki/Home/
>
> If you select "Browse Pages" in the left hand bar, it will show a
> linke to the Homebrew OSX page:
>
> https://sourceforge.net/p/csound/wiki/Homebrew%20OSX/
>
> I think we should migrate our wiki information from Mediawiki to the
> built-in platform. Perhaps we should put this Debian building
> information there?
>
> Thanks!
> steven
>
> On Mon, Jul 15, 2013 at 12:46 PM, joachim heintz  wrote:
>> hi steven -
>>
>> i am wondering how we can put an instruction of this together, to which we
>> can point people? this would be very necessary and useful.
>>
>> i suggest to put this in the media wiki. there are already some for csound5
>> in
>> http://sourceforge.net/apps/mediawiki/csound/index.php?title=Csound_development
>>
>> i personally think that "Csound development" is not the best title for
>> instructions like this. i suggest to create a new chapter "Building Csound".
>>
>> best -
>>
>>          joachim
>>
>>
>>
>> Am 15.07.2013 17:46, schrieb Steven Yi:
>>>
>>> Hi Robin,
>>>
>>> I should have clarified about step 3: cmake in general promotes using
>>> out-of-source builds, so that the build is done completely outside of
>>> the src root.  This is not mandatory though.  I tend to do have
>>> folders like:
>>>
>>> /x/y/z/csound/csound6
>>> /x/y/z/csound/cs6make
>>> /x/y/z/csound/cs6xcode
>>> /x/y/z/csound/cs6ninja
>>>
>>> etc. for different build generators. (The default is Makefile, but you
>>> can generate builds for other build systems.) So that step was meant
>>> to go into the /x/y/z/csound folder and create cs6make.
>>>
>>> As for /usr/local/lib not being on the ld path by default, I'm not
>>> really sure why that didn't happen. I've seen that happen on occasion
>>> of the years with various Linux installations, but I haven't come
>>> across it in a while.
>>>
>>> I'm very glad though that you have a working Csound6 system, built from
>>> source!
>>>
>>> All best,
>>> steven
>>>
>>>
>>>
>>> On Mon, Jul 15, 2013 at 10:57 AM, Robin Whittle  wrote:
>>>>
>>>> Hi Steven,
>>>>
>>>> Thanks for your reply.  I did this on a directory which I created by
>>>> un-targzipping the "Csound6.00.tar.gz" file as a mortal user.  Doing so
>>>> as root creates directories which the mortal user can't write to.
>>>>
>>>>> In the past on Debian, I built like so:
>>>>>
>>>>> 1. sudo apt-get build-dep csound
>>>>> 2. sudo apt-get install cmake
>>>>> 3. cd /dir/where/csound6/folder/is
>>>>> 4. mkdir cs6make
>>>>> 5. cd cs6make
>>>>
>>>>
>>>> All was well until this step:
>>>>
>>>>> 6. cmake ../csound6
>>>>
>>>>
>>>>       CMake Error: The source directory "/x/y/z/Csound6.00/csound6" does
>>>>       not exist.
>>>>
>>>> I looked around and tried this instead:
>>>>
>>>>     cmake ../CMakeLists.txt
>>>>
>>>> This produced signs of intelligent life and no errors.  The final line
>>>> was:
>>>>
>>>> -- Build files have been written to: /x/y/z/Csound6.00
>>>>
>>>> The file which is created is:
>>>>
>>>>     /x/y/z/Csound6.00/Makefile
>>>>
>>>> I am not sure what purpose there is in changing to this new directory
>>>> "csmake", since nothing is written there.
>>>>
>>>> This step needs to be done from /x/y/z/Csound6.00/ :
>>>>
>>>>> 7. make -j6
>>>>
>>>>
>>>> This produced a lot of happy looking results.  There is an executable:
>>>>
>>>>     /x/y/z/Csound6.00/csound
>>>>
>>>>> 8. sudo make install
>>>>
>>>>
>>>> This generates a bunch of lines, including the destination of the plain
>>>> Csound binary I am interested in:
>>>>
>>>> -- Installing: /usr/local/bin/csound
>>>>
>>>> The text of this can be found in /x/y/z/Csound6.00/install_manifest.txt
>>>>
>>>> Now I think I should be able to run it, at least to get some help text.
>>>>    From the /examples directory I run "csound" - and get:
>>>>
>>>>      csound: error while loading shared libraries: libcsound64.so.6.0:
>>>>      cannot open shared object file: No such file or directory
>>>>
>>>> Yet the first line of install_manifest.txt is:
>>>>
>>>>     /usr/local/lib/libcsound64.so.6.0
>>>>
>>>> and indeed there is such a file there.  After some Googling I found this
>>>> mailing list thread:
>>>>
>>>>     http://csound.1045644.n5.nabble.com/5-19-for-Ubuntu-td5720035.html
>>>>
>>>> from 2013-02-11 in which David Seidel wrote (regarding Ubuntu - I am
>>>> using Debian on which Ubuntu is in some way based):
>>>>
>>>>> So I had to add /usr/local/lib to /etc/ld.so.conf and run
>>>>> "sudo ldconfig". Problem solved.
>>>>
>>>>
>>>> My file "/etc/ld.so.conf" contains just:
>>>>
>>>>     include /etc/ld.so.conf.d/*.conf
>>>>
>>>> and my directory /etc/ld.so.conf.d/ contained two files with the
>>>> following contents:
>>>>
>>>>     libc.conf
>>>>
>>>>        # libc default configuration
>>>>        /usr/local/lib
>>>>
>>>>     x86_64-linux-gnu.conf
>>>>
>>>>        # Multiarch support
>>>>        /lib/x86_64-linux-gnu
>>>>        /usr/lib/x86_64-linux-gnu
>>>>
>>>> My /usr/local/lib contained only:
>>>>
>>>> /csound/
>>>> /python2.6/
>>>> /python2.7/
>>>>    _csnd6.so
>>>>    csnd6.jar
>>>>    csnd6.py
>>>>    csoundapi~.pd_linux
>>>>    lib_jcsound6.so
>>>>    libcsnd.so -> libcsnd.so.6.0
>>>>    libcsnd.so.6.0
>>>>    libcsound64.so -> libcsound64.so.6.0
>>>>    libcsound64.so.6.0
>>>>    luaCsnd6.so
>>>>
>>>> This all looks good to me, but I only rarely think about library paths.
>>>>    All I had to do was run "sudo ldconfig" and then I could run the
>>>> command "csound".
>>>>
>>>> I am not sure why this is the case.  It is a fresh install of 64 bit
>>>> Debian 8.0 on a Core 2 Duo machine.  The abovementioned files are not at
>>>> all related to Csound.  Perhaps this command should have been run as
>>>> part of the installation, but wasn't.
>>>>
>>>> Now, from the examples directory, I ran:
>>>>
>>>>     csound xanadu
>>>>
>>>> and it produced a xanadu.wav file which Wavelab (Windows) recognized as
>>>> a stereo 44.1kHz 32 bit floating point file and played fine.
>>>>
>>>> It never ceases to amaze me how Csound can turn a few kbytes of text
>>>> into an intriguing piece of music - in this case a minute, calculated in
>>>> 8.5 seconds (Core 2 Duo E6750 2.67MHz 65nm 4MB cache).   But this is
>>>> with ksmps = 100, meaning krate is 441Hz.  There was some rattly high
>>>> distortion, mainly in the first few seconds and 45 to 47 seconds.
>>>>
>>>> I create a copy of this as xanadu-k-14700.csd and changed the ksmps line
>>>> to "3".  This took 22 seconds to cook and sounds perfect to me.
>>>>
>>>> I made a similarly modified version of "hommage.csd" with two lines
>>>> changed:
>>>>
>>>> kr = 14700
>>>> ksmps = 3
>>>>
>>>> This took 39 seconds to produce test.wav, 2 minutes 25 seconds, which
>>>> sounded fine to me.
>>>>
>>>> I haven't investigated any further, but the build has clearly been
>>>> successful.  Thanks!
>>>>
>>>>      - Robin
>>>>
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>               https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>>
>>
>
>
> Send bugs reports to the Sourceforge bug tracker
>              https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>

yes, that ("formatting is a pain") is the problem. and maintaing / 
updating is a problem, too. we have a lot of outdated information in the 
manual, and it is too hard to edit them.

i think we should disburden the core developers as much as possible from 
this job. there are a lot of people who build csound on their different 
platforms. it would be ideal if they put together and update 
descriptions, and the best way to do may be a wiki.

can you think to put your How to Build Csound 6 on Windows there, too?

best -

	joachim


Am 15.07.2013 21:03, schrieb Michael Gogins:
used as the metadata for the tickets, rather than have a whole tracker
> Another option for Debian building info is in the How to Build Csound 6
> on Windows document, which could drop windows from the title and add
> section headers for Windows and Debian.
>
> This stuff actually belongs in the manual, if you ask me, but formatting
> it is a pain.
>
> Regards,
> Mike
>
>
> ===========================
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Mon, Jul 15, 2013 at 2:56 PM, Steven Yi  > wrote:
>
>     Hi Joachim,
>
>     Using a Wiki sounds good to me.  The issue now is that Sourceforge
>     used to offer Mediawiki as a separate package you could install. I
>     think now it is only available if you had already installed it, and a
>     number of times they had mentioned discontinuing the wiki in favor of
>     their new built-in one.
>
>     There's a support ticket here that has further information:
>
>     https://sourceforge.net/p/forge/site-support/4238/
>
>     There was some chatter on the dev list about which wiki to use a while
>     back.  I ended up writing the information for how to use Homebrew to
>     install Csound on OSX, and had put it on the built-in wiki.  The main
>     page for the built-in wiki is at:
>
>     https://sourceforge.net/p/csound/wiki/Home/
>
>     If you select "Browse Pages" in the left hand bar, it will show a
>     linke to the Homebrew OSX page:
>
>     https://sourceforge.net/p/csound/wiki/Homebrew%20OSX/
>
>     I think we should migrate our wiki information from Mediawiki to the
>     built-in platform. Perhaps we should put this Debian building
>     information there?
>
>     Thanks!
>     steven
>
>     On Mon, Jul 15, 2013 at 12:46 PM, joachim heintz
>     > wrote:
>      > hi steven -
>      >
>      > i am wondering how we can put an instruction of this together, to
>     which we
>      > can point people? this would be very necessary and useful.
>      >
>      > i suggest to put this in the media wiki. there are already some
>     for csound5
>      > in
>      >
>     http://sourceforge.net/apps/mediawiki/csound/index.php?title=Csound_development
>      >
>      > i personally think that "Csound development" is not the best
>     title for
>      > instructions like this. i suggest to create a new chapter
>     "Building Csound".
>      >
>      > best -
>      >
>      >         joachim
>      >
>      >
>      >
>      > Am 15.07.2013 17:46, schrieb Steven Yi:
>      >>
>      >> Hi Robin,
>      >>
>      >> I should have clarified about step 3: cmake in general promotes
>     using
>      >> out-of-source builds, so that the build is done completely
>     outside of
>      >> the src root.  This is not mandatory though.  I tend to do have
>      >> folders like:
>      >>
>      >> /x/y/z/csound/csound6
>      >> /x/y/z/csound/cs6make
>      >> /x/y/z/csound/cs6xcode
>      >> /x/y/z/csound/cs6ninja
>      >>
>      >> etc. for different build generators. (The default is Makefile,
>     but you
>      >> can generate builds for other build systems.) So that step was meant
>      >> to go into the /x/y/z/csound folder and create cs6make.
>      >>
>      >> As for /usr/local/lib not being on the ld path by default, I'm not
>      >> really sure why that didn't happen. I've seen that happen on
>     occasion
>      >> of the years with various Linux installations, but I haven't come
>      >> across it in a while.
>      >>
>      >> I'm very glad though that you have a working Csound6 system,
>     built from
>      >> source!
>      >>
>      >> All best,
>      >> steven
>      >>
>      >>
>      >>
>      >> On Mon, Jul 15, 2013 at 10:57 AM, Robin Whittle
>     > wrote:
>      >>>
>      >>> Hi Steven,
>      >>>
>      >>> Thanks for your reply.  I did this on a directory which I
>     created by
>      >>> un-targzipping the "Csound6.00.tar.gz" file as a mortal user.
>       Doing so
>      >>> as root creates directories which the mortal user can't write to.
>      >>>
>      >>>> In the past on Debian, I built like so:
>      >>>>
>      >>>> 1. sudo apt-get build-dep csound
>      >>>> 2. sudo apt-get install cmake
>      >>>> 3. cd /dir/where/csound6/folder/is
>      >>>> 4. mkdir cs6make
>      >>>> 5. cd cs6make
>      >>>
>      >>>
>      >>> All was well until this step:
>      >>>
>      >>>> 6. cmake ../csound6
>      >>>
>      >>>
>      >>>      CMake Error: The source directory
>     "/x/y/z/Csound6.00/csound6" does
>      >>>      not exist.
>      >>>
>      >>> I looked around and tried this instead:
>      >>>
>      >>>    cmake ../CMakeLists.txt
>      >>>
>      >>> This produced signs of intelligent life and no errors.  The
>     final line
>      >>> was:
>      >>>
>      >>> -- Build files have been written to: /x/y/z/Csound6.00
>      >>>
>      >>> The file which is created is:
>      >>>
>      >>>    /x/y/z/Csound6.00/Makefile
>      >>>
>      >>> I am not sure what purpose there is in changing to this new
>     directory
>      >>> "csmake", since nothing is written there.
>      >>>
>      >>> This step needs to be done from /x/y/z/Csound6.00/ :
>      >>>
>      >>>> 7. make -j6
>      >>>
>      >>>
>      >>> This produced a lot of happy looking results.  There is an
>     executable:
>      >>>
>      >>>    /x/y/z/Csound6.00/csound
>      >>>
>      >>>> 8. sudo make install
>      >>>
>      >>>
>      >>> This generates a bunch of lines, including the destination of
>     the plain
>      >>> Csound binary I am interested in:
>      >>>
>      >>> -- Installing: /usr/local/bin/csound
>      >>>
>      >>> The text of this can be found in
>     /x/y/z/Csound6.00/install_manifest.txt
>      >>>
>      >>> Now I think I should be able to run it, at least to get some
>     help text.
>      >>>   From the /examples directory I run "csound" - and get:
>      >>>
>      >>>     csound: error while loading shared libraries:
>     libcsound64.so.6.0:
>      >>>     cannot open shared object file: No such file or directory
>      >>>
>      >>> Yet the first line of install_manifest.txt is:
>      >>>
>      >>>    /usr/local/lib/libcsound64.so.6.0
>      >>>
>      >>> and indeed there is such a file there.  After some Googling I
>     found this
>      >>> mailing list thread:
>      >>>
>      >>> http://csound.1045644.n5.nabble.com/5-19-for-Ubuntu-td5720035.html
>      >>>
>      >>> from 2013-02-11 in which David Seidel wrote (regarding Ubuntu -
>     I am
>      >>> using Debian on which Ubuntu is in some way based):
>      >>>
>      >>>> So I had to add /usr/local/lib to /etc/ld.so.conf and run
>      >>>> "sudo ldconfig". Problem solved.
>      >>>
>      >>>
>      >>> My file "/etc/ld.so.conf" contains just:
>      >>>
>      >>>    include /etc/ld.so.conf.d/*.conf
>      >>>
>      >>> and my directory /etc/ld.so.conf.d/ contained two files with the
>      >>> following contents:
>      >>>
>      >>>    libc.conf
>      >>>
>      >>>       # libc default configuration
>      >>>       /usr/local/lib
>      >>>
>      >>>    x86_64-linux-gnu.conf
>      >>>
>      >>>       # Multiarch support
>      >>>       /lib/x86_64-linux-gnu
>      >>>       /usr/lib/x86_64-linux-gnu
>      >>>
>      >>> My /usr/local/lib contained only:
>      >>>
>      >>> /csound/
>      >>> /python2.6/
>      >>> /python2.7/
>      >>>   _csnd6.so
>      >>>   csnd6.jar
>      >>>   csnd6.py
>      >>>   csoundapi~.pd_linux
>      >>>   lib_jcsound6.so
>      >>>   libcsnd.so -> libcsnd.so.6.0
>      >>>   libcsnd.so.6.0
>      >>>   libcsound64.so -> libcsound64.so.6.0
>      >>>   libcsound64.so.6.0
>      >>>   luaCsnd6.so
>      >>>
>      >>> This all looks good to me, but I only rarely think about
>     library paths.
>      >>>   All I had to do was run "sudo ldconfig" and then I could run the
>      >>> command "csound".
>      >>>
>      >>> I am not sure why this is the case.  It is a fresh install of
>     64 bit
>      >>> Debian 8.0 on a Core 2 Duo machine.  The abovementioned files
>     are not at
>      >>> all related to Csound.  Perhaps this command should have been
>     run as
>      >>> part of the installation, but wasn't.
>      >>>
>      >>> Now, from the examples directory, I ran:
>      >>>
>      >>>    csound xanadu
>      >>>
>      >>> and it produced a xanadu.wav file which Wavelab (Windows)
>     recognized as
>      >>> a stereo 44.1kHz 32 bit floating point file and played fine.
>      >>>
>      >>> It never ceases to amaze me how Csound can turn a few kbytes of
>     text
>      >>> into an intriguing piece of music - in this case a minute,
>     calculated in
>      >>> 8.5 seconds (Core 2 Duo E6750 2.67MHz 65nm 4MB cache).   But
>     this is
>      >>> with ksmps = 100, meaning krate is 441Hz.  There was some
>     rattly high
>      >>> distortion, mainly in the first few seconds and 45 to 47 seconds.
>      >>>
>      >>> I create a copy of this as xanadu-k-14700.csd and changed the
>     ksmps line
>      >>> to "3".  This took 22 seconds to cook and sounds perfect to me.
>      >>>
>      >>> I made a similarly modified version of "hommage.csd" with two lines
>      >>> changed:
>      >>>
>      >>> kr = 14700
>      >>> ksmps = 3
>      >>>
>      >>> This took 39 seconds to produce test.wav, 2 minutes 25 seconds,
>     which
>      >>> sounded fine to me.
>      >>>
>      >>> I haven't investigated any further, but the build has clearly been
>      >>> successful.  Thanks!
>      >>>
>      >>>     - Robin
>      >>>
>      >>
>      >>
>      >> Send bugs reports to the Sourceforge bug tracker
>      >> https://sourceforge.net/tracker/?group_id=81968&atid=564599
>      >> Discussions of bugs and features can be posted here
>      >> To unsubscribe, send email sympa@lists.bath.ac.uk
>      with body "unsubscribe
>      >> csound"
>      >>
>      >>
>      >
>
>
>     Send bugs reports to the Sourceforge bug tracker
>     https://sourceforge.net/tracker/?group_id=81968&atid=564599
>     Discussions of bugs and features can be posted here
>     To unsubscribe, send email sympa@lists.bath.ac.uk
>      with body "unsubscribe csound"
>
>

On 07/15/2013 10:57 AM, Robin Whittle wrote:
>> In the past on Debian, I built like so:
>>
>> 1. sudo apt-get build-dep csound
>> 2. sudo apt-get install cmake
>> 3. cd /dir/where/csound6/folder/is
>> 4. mkdir cs6make
>> 5. cd cs6make
> All was well until this step:
>
>> 6. cmake ../csound6
>      CMake Error: The source directory "/x/y/z/Csound6.00/csound6" does
>      not exist.

Hi Robin !

You only need to run "cmake .."  from your build directory and the rest 
of your complications will go away. :)

My process:

1. Do a fresh git pull to ~/src.
2. cd to ~/src/csound-csound6-git
3. mkdir build
4.cd build
5. cmake ..
6. make
7. sudo make install

Like the autoconf tools cmake will query the system for available 
resources. What it doesn't find it won't build, but you can customize 
the cmake options.

Apologies if all this is already apparent, but it might be helpful to 
next intrepid soul trying to build Cs6 on Linux.

Best regards,

dp

The manual is in XML/docbook.

On 18 Jul 2013, at 13:07, aaB wrote:

> Hello all,
> 
>> yes, that ("formatting is a pain") is the problem. and maintaing /
>> updating is a problem, too. we have a lot of outdated information in
>> the manual, and it is too hard to edit them.
> What format is that?
> I am relatively competent in LaTeX, if that is the format, I'd be glad to act as
> secretary and do some typing. If it is in an other format, I could try to learn
> about it and do the formatting.
> 
>> i think we should disburden the core developers as much as possible
>> from this job. there are a lot of people who build csound on their
>> different platforms. it would be ideal if they put together and
>> update descriptions, and the best way to do may be a wiki.
> I totally agree, and as for the FLOSS manual, I would be very glad to help in
> whatever way I can.
> 
> Alexandre
> 
> 
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie

hi alexandre -

i think to join the dev-list is a good idea at any time you want (even 
now); to see what the discussions are, and to be a part of them, 
whenever you like.

all best -

	joachim


Am 18.07.2013 21:51, schrieb aaB:
> On Thu, Jul 18, 2013 at 02:31:38PM +0100, Victor Lazzarini wrote:
>> The manual is in XML/docbook.
>>
> OK, I know nothing about this format, so I will need to learn at least the
> basics before committing myself.
> Once I have acquired a few skills, should I join the dev list to determine what
> should be done?
>
> Best,
>
> Alexandre
>
>
> Send bugs reports to the Sourceforge bug tracker
>              https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>