I believe ( have not tried it ) you should be able to use Timidity to test
midi out on Linux, along with some form of loopback. I know there exists a
loopback of some kind, cause we used it on my old Debian install but I can't
remember the exact name. If I find it today I'll write back.

Speaking of testing, I would like to be able to help out in that department
as I have two soundcards, Gina and Delta 44, and two midi cards, both USB
and serial, on a dual boot machine, along with whole bunch of csound
diagnostic ensembles meant for testing various forms of real time i/o. Can
anyone suggest the best place for a compiling-from-source newbie to learn
how scons works?

Thanks
Iain


----- Original Message -----
From: 
To: "Csound Developers Discussion List" 
Sent: Thursday, April 22, 2004 6:56 AM
Subject: [CSOUND-DEV:4489] Re: Csound5 and MinGW


I have no way to test MIDI out on Windows, or any MIDI at all on Linux.
Maybe I can use a MIDI loopback to test MIDI out on Windows, though.

Original Message:
-----------------
From: iain duncan iainduncan@telus.net
Date: Wed, 21 Apr 2004 23:19:51 -0700
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:4486] Re: Csound5 and MinGW


Great news!

> To do:
>
> MIDI in on Windows

Don't suppose the above could be change to Midi i/o?

Thanks
Iain

> Verify VST plugin still works
> Loris plugin opcode
> Verify Linux build with this SConstruct
> Mathematica interface
> Add usage tutorials to CVS and to csound.pdf.
>
> Thanks to Erik, John Fitch, Steven Yi, and everyone else who has been
> working to bring Csound 5 to life.
>
> Would it be feasible to remove all autotools build files and Makefiles
from
> Csound 5 CVS? Is anyone building Csound 5 in any other way except with
> scons?
>


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .

Hi Iain,

The scons home page has a nice man page:

http://www.scons.org/doc/HTML/scons-man.html

Michael's csound.pdf that's in csound5 CVS has got enough information to 
get things set up for running scons I think.  Once you have a copy of 
the sources and scons setup, go into the csound5 directory and type:

scons

which will start the build.  Ideally, that's all you'll have to do.  If 
you do get errors, it might be from some configuration settings that 
still need some working out.  You can get past most of those though by 
passing in commandline flags to scons, i.e.:

scons buildCsoundVST=0

will turn off building CsoundVST.  To see a list of what command-line 
flags are available, type:

scons -h

Hope that helps and please do ask as many questions as they arise, as it 
will help to point out what should be added to the csound.pdf document 
to make it easier for other users to compile. 

Good luck!
steven


iain duncan wrote:

>I believe ( have not tried it ) you should be able to use Timidity to test
>midi out on Linux, along with some form of loopback. I know there exists a
>loopback of some kind, cause we used it on my old Debian install but I can't
>remember the exact name. If I find it today I'll write back.
>
>Speaking of testing, I would like to be able to help out in that department
>as I have two soundcards, Gina and Delta 44, and two midi cards, both USB
>and serial, on a dual boot machine, along with whole bunch of csound
>diagnostic ensembles meant for testing various forms of real time i/o. Can
>anyone suggest the best place for a compiling-from-source newbie to learn
>how scons works?
>
>Thanks
>Iain
>  
>

Hi all,
First, thanks all for your great effort in getting Csound5 up and running! I 
can't wait to see it working!

Now for the problems...

I'm trying to build on Windows XP using mingw, and msys, but I'm getting the 
following on the msys terminal:
(I'm using Windows Python 2.3.3)

System platform is 'win32'.
Tools:  
['default', 'mslink', 'msvc', 'g77', 'gas', 'mslib', 'CVS', 'lex', 'm4', 'midl'
, 'msvs', 'tar', 'yacc', 'zip']
Build platform is 'unsupported'.

Using single-precision floating point for audio samples.
Checking for C header file sndfile.h... no
The sndfile library is required to build Csound 5.



Apparently, the build system is not recognizing mingw, even though I've set 
the /bin and /include directories for my mingw installation in custom.py. Do I 
need to install the msys sources as well? (That one is a really huge 
download...).
I have already downloaded libsndfile. Am I setting the path correctly by using:

    customLIBPATH.append('C:/Dev-Cpp/libsndfile-1.0.10pre4/src')

in custom.py ?

Thanks in advance and be prepared to hear from me again....=)
Andres

Hi Andres,

I'm not sure about what's going on with the platform as 'unrecognized', 
but for libsndfile, you can not use just the source and must compile it 
before using it.  After compiling libsndfile, you should get a 
sndfile.dll or libsndfile.dll, and whatever directory that is in should 
be added to customLIBPATH.  (I haven't tried compiling on MinGW/MSYS yet 
so am going off how I'm seeing it; if otherwise, some please correct me).

steven


acabrera@teleset.com.co wrote:

>Hi all,
>First, thanks all for your great effort in getting Csound5 up and running! I 
>can't wait to see it working!
>
>Now for the problems...
>
>I'm trying to build on Windows XP using mingw, and msys, but I'm getting the 
>following on the msys terminal:
>(I'm using Windows Python 2.3.3)
>
>System platform is 'win32'.
>Tools:  
>['default', 'mslink', 'msvc', 'g77', 'gas', 'mslib', 'CVS', 'lex', 'm4', 'midl'
>, 'msvs', 'tar', 'yacc', 'zip']
>Build platform is 'unsupported'.
>
>Using single-precision floating point for audio samples.
>Checking for C header file sndfile.h... no
>The sndfile library is required to build Csound 5.
>
>
>
>Apparently, the build system is not recognizing mingw, even though I've set 
>the /bin and /include directories for my mingw installation in custom.py. Do I 
>need to install the msys sources as well? (That one is a really huge 
>download...).
>I have already downloaded libsndfile. Am I setting the path correctly by using:
>
>    customLIBPATH.append('C:/Dev-Cpp/libsndfile-1.0.10pre4/src')
>
>in custom.py ?
>
>Thanks in advance and be prepared to hear from me again....=)
>Andres
>
>
>
>  
>

> 
> >I believe ( have not tried it ) you should be able to use Timidity to test
> >midi out on Linux, along with some form of loopback. I know there exists a
> >loopback of some kind, cause we used it on my old Debian install but I can't
> >remember the exact name. If I find it today I'll write back.

snd-virmidi.  it's an alsa module, just do ./configure
--with-cards=,,virmidi --enable-sequencer=yes or the
like when you're compiling alsa, and then check out the documentation from
the usual alsa places.

glyn