I am distinguishing between build time dependencies and run time dependencies. Csound 5 depends on Python to build, so Python can assumed to be present. There is no run time dependency on Python or any other software.

I'm not "forcing" anything on anyone, except maybe for the Csound developers to install SWIG, which is no big deal. The presence of the wrappers does not make anyone do anything. It is simply a facility that is available for those who wish to use it.

Regards,
Mike

-----Original Message-----
From: Istvan Varga 
Sent: Oct 21, 2005 12:36 PM
To: csound-devel@lists.sourceforge.net
Subject: Re: [Cs-dev] wrappers, frontends etc

Michael Gogins wrote:

> What I propose is that the language wrappers be built into the core of Csound.
 > They are not "front ends", they are enabling technology for "front ends" and
 > they need to be standardized and universally available, just like we need a
 > standard piano keyboard or standard music notation, and for exactly the same
 > reasons.

You somehow always avoid explaining what the major disadvantages of
splitting what you consider the "core" of Csound into two separate
libraries (that can, however, both be included in a binary distribution),
where one contains the wrappers and glue code for external languages.
Others seem to generally not oppose this modular design.

Or do you think it gets more attention by unconditionally forcing it
on everyone whether they want it or not ?

> The 3rd party dependencies involved in the wrappers that I am creating are
 > minimal. They are C++ (we already have it), Python (we already have it),

These assumptions are both wrong. Or did I miss something here ?
I see nothing other than sndfile and standard system libraries.

if (commonEnvironment['dynamicCsoundLibrary'] == '1'):
   print 'CONFIGURATION DECISION: Building dynamic Csound library'
   csoundLibraryEnvironment.Append(LIBS = ['sndfile'])
   if getPlatform() == 'mingw':
     csoundLibraryEnvironment.Append(LIBS = csoundWindowsLibraries)
     csoundLibraryEnvironment.Append(SHLINKFLAGS = ['-module'])
     csoundLibraryEnvironment['ENV']['PATH'] = os.environ['PATH']
   elif getPlatform() == 'linux':
     csoundLibraryEnvironment.Append(LIBS = ['dl', 'm', 'pthread'])
   csoundLibrary = csoundLibraryEnvironment.SharedLibrary('csound',
                                                          libCsoundSources)


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel





-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Michael Gogins wrote:

> I am distinguishing between build time dependencies and run
 > time dependencies. Csound 5 depends on Python to build, so Python
 > can assumed to be present.

Wrong again. Not everyone builds Csound with SCons, even if currently
that is the most commonly used option.

> There is no run time dependency on Python  or any other software.

So, do the wrappers depend on the Python library (and possibly others
in the future as more languages are added), or not ?

And, of course, still not answered:

You somehow always avoid explaining what the major disadvantages of
splitting what you consider the "core" of Csound into two separate
libraries (that can, however, both be included in a binary distribution),
where one contains the wrappers and glue code for external languages are.
Others seem to generally not oppose this modular design.

Or do you think it gets more attention by unconditionally forcing it
on everyone whether they want it or not ?


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net