>
> 1) How difficult would it be to build Csound without Python (i.e. no Scons/Python needed from build to end-use)?
You will need to write a new Makefile for each platform. Or, worse, write an autoconf script etc.
>
> 2) Can I build Csound with the standard version of mingw (not the setjmp longjmp version -- or whatever it's called). If not, then how hard would it be to recode the "jumps" so it can be built on the normal version of mingw (I haven't delved into the code deeply but as far as I can tell the "jumps" are error and return related so it would seem that they could be removed).
I'm not sure about this. I have installed the standard version of MinGW (as far as I can remember) a
couple of months ago in this vista computer I have at home and it builds Csound for me alright.
Not sure about this requirement now. Mike Gogins will tell you more...
>
> 3) How many "core" dependencies does Csound really have? It seems like most of the dependencies are gui and binding related and that the basic table, opcode, and soundfile code use a small set of libraries that are easy to build.
The only core dependency is libsndfile. Everything else is optional. With libsndfile only you
get a functional system on all platforms. However on Windows RT IO is bad because it
will use the MME IO module. So in this platform I would recommend at least adding portaudio
to the list for ASIO.
>
> 4) My main user-group will be on Windows and I'd like to make the use of Csound as transparent as possible but I'm concerned about Csound's installer for it. Last I knew it was leaving users with an unresolved Python library message box issue during Csound startup. Is this still the case?
Mike Gogins is your man on this one.
Victor
Send bugs reports to this list.
To unsubscribe, send email
sympa@... with body "unsubscribe csound"
