Csound Csound-dev Csound-tekno Search About

[Cs-dev] SConstruct changes for tclcsound

Date2005-12-14 03:28
From"Michael Gogins"
Subject[Cs-dev] SConstruct changes for tclcsound
My aplogies if I broke anything, but if I did it should be easy to fix.

I had to change SConstruct in order to build both the Python libraries and 
the tclcsound stuff on Windows with MinGW.

The changes amount to first building the tclcsound shared library, then 
creating a new Environment for Tclcsound programs which links with the 
tclcsound library, and then using the new Environment to build the Tclcsound 
programs.

This is necessary because SCons objects to building the same object 
(commands.o) more than once with different flags.

I have updated the NSIS Windows installer to include the Tclcsound library 
and applications, as well.

I'm fairly confident this will work on Linux, but I'm not so sure about OS 
X, and have no way to test it. If I have broken the OS X build, then we will 
need to conditionally build the new way on Windows and the old way on OS X.

I will release a new file package with the NSIS installer, following 
Istvan's conventions except that only 64 bit executables will be included, 
but also including Loris, Fluidsynth, the C++ STK opcodes, Tclcsound, 
CsoundVST, and the LISP stuff, in the not too distant future. This will be 
my idea of a release candidate for Csound 5.

Thanks to Istvan for reducing the sizes of things, and for implementing the 
callbacks for Python and Java.

Regards,
Mike





-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2005-12-14 09:11
FromVictor Lazzarini
SubjectRe: [Cs-dev] SConstruct changes for tclcsound
I'll check the OSX build today and fix anything that might be broken.

Victor

At 03:28 14/12/2005, you wrote:
>My aplogies if I broke anything, but if I did it should be easy to fix.
>
>I had to change SConstruct in order to build both the Python libraries and 
>the tclcsound stuff on Windows with MinGW.
>
>The changes amount to first building the tclcsound shared library, then 
>creating a new Environment for Tclcsound programs which links with the 
>tclcsound library, and then using the new Environment to build the 
>Tclcsound programs.
>
>This is necessary because SCons objects to building the same object 
>(commands.o) more than once with different flags.
>
>I have updated the NSIS Windows installer to include the Tclcsound library 
>and applications, as well.
>
>I'm fairly confident this will work on Linux, but I'm not so sure about OS 
>X, and have no way to test it. If I have broken the OS X build, then we 
>will need to conditionally build the new way on Windows and the old way on 
>OS X.
>
>I will release a new file package with the NSIS installer, following 
>Istvan's conventions except that only 64 bit executables will be included, 
>but also including Loris, Fluidsynth, the C++ STK opcodes, Tclcsound, 
>CsoundVST, and the LISP stuff, in the not too distant future. This will be 
>my idea of a release candidate for Csound 5.
>
>Thanks to Istvan for reducing the sizes of things, and for implementing 
>the callbacks for Python and Java.
>
>Regards,
>Mike
>
>
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
>for problems?  Stop!  Download the new AJAX search engine that makes
>searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
>http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2005-12-14 09:57
FromIstvan Varga
SubjectRe: [Cs-dev] SConstruct changes for tclcsound
AttachmentsNone  

Date2005-12-14 10:02
FromVictor Lazzarini
SubjectRe: [Cs-dev] SConstruct changes for tclcsound
I agree. Can you make these changes?

At 09:57 14/12/2005, you wrote:
>On Wednesday 14 December 2005 04:28, Michael Gogins wrote:
>
> > My aplogies if I broke anything, but if I did it should be easy to fix.
> >
> > I had to change SConstruct in order to build both the Python libraries and
> > the tclcsound stuff on Windows with MinGW.
> >
> > The changes amount to first building the tclcsound shared library, then
> > creating a new Environment for Tclcsound programs which links with the
> > tclcsound library, and then using the new Environment to build the 
> Tclcsound
> > programs.
> >
> > This is necessary because SCons objects to building the same object
> > (commands.o) more than once with different flags.
> >
> > I have updated the NSIS Windows installer to include the Tclcsound library
> > and applications, as well.
> >
> > I'm fairly confident this will work on Linux, but I'm not so sure about OS
> > X, and have no way to test it. If I have broken the OS X build, then we 
> will
> > need to conditionally build the new way on Windows and the old way on OS X.
>
>I think it could have been enough to just build commands.c as a SharedObject,
>and adding that to the sources of all three targets. Linking to tclcsound.so
>does not work on Linux because it uses a non-standard name (i.e. no 'lib'
>prefix), and it also requires installing the library to a directory where it
>is found by the dynamic linker at run-time.
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
>for problems?  Stop!  Download the new AJAX search engine that makes
>searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
>http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2005-12-14 10:05
FromVictor Lazzarini
SubjectRe: [Cs-dev] SConstruct changes for tclcsound
It will be easier if cswish, cstclsh and tclcsound.so(.dylib.dll) link
directly against libcsound. It is strange that on OSX and Linux,
as well as windows MSVC, there was no problem with the way
tclcsound was built before. Commands.c was shared between those
targets without any problem. I don't know why the problem in MSYS

At 09:57 14/12/2005, you wrote:
>On Wednesday 14 December 2005 04:28, Michael Gogins wrote:
>
> > My aplogies if I broke anything, but if I did it should be easy to fix.
> >
> > I had to change SConstruct in order to build both the Python libraries and
> > the tclcsound stuff on Windows with MinGW.
> >
> > The changes amount to first building the tclcsound shared library, then
> > creating a new Environment for Tclcsound programs which links with the
> > tclcsound library, and then using the new Environment to build the 
> Tclcsound
> > programs.
> >
> > This is necessary because SCons objects to building the same object
> > (commands.o) more than once with different flags.
> >
> > I have updated the NSIS Windows installer to include the Tclcsound library
> > and applications, as well.
> >
> > I'm fairly confident this will work on Linux, but I'm not so sure about OS
> > X, and have no way to test it. If I have broken the OS X build, then we 
> will
> > need to conditionally build the new way on Windows and the old way on OS X.
>
>I think it could have been enough to just build commands.c as a SharedObject,
>and adding that to the sources of all three targets. Linking to tclcsound.so
>does not work on Linux because it uses a non-standard name (i.e. no 'lib'
>prefix), and it also requires installing the library to a directory where it
>is found by the dynamic linker at run-time.
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
>for problems?  Stop!  Download the new AJAX search engine that makes
>searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
>http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2005-12-14 10:08
FromIstvan Varga
SubjectRe: [Cs-dev] SConstruct changes for tclcsound
AttachmentsNone  

Date2005-12-14 10:12
FromVictor Lazzarini
SubjectRe: [Cs-dev] SConstruct changes for tclcsound
Another question. I have just built the OSX CsoundLib.Framework,
why is it building version 5.1 now? How does the version system
work?

Victor

At 10:08 14/12/2005, you wrote:
>On Wednesday 14 December 2005 11:02, Victor Lazzarini wrote:
>
> > I agree. Can you make these changes?
>
>I already made them, just did not commit. I will do some testing
>first.
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
>for problems?  Stop!  Download the new AJAX search engine that makes
>searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
>http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2005-12-14 10:20
FromIstvan Varga
SubjectRe: [Cs-dev] SConstruct changes for tclcsound
AttachmentsNone  

Date2005-12-14 10:25
FromIstvan Varga
SubjectRe: [Cs-dev] SConstruct changes for tclcsound
AttachmentsNone  

Date2005-12-14 10:31
FromVictor Lazzarini
SubjectRe: [Cs-dev] SConstruct changes for tclcsound
No, it's fine. I just wanted to see what the story was. The framework build 
seems
to be working OK now. The only slightly odd thing is that an extra symbolic 
link is
generated in Versions/5.1/5.1 -> 5.1 (as if ln was called twice). This is 
not a major
problem.

Victor

At 10:20 14/12/2005, you wrote:
>On Wednesday 14 December 2005 11:12, Victor Lazzarini wrote:
>
> > Another question. I have just built the OSX CsoundLib.Framework,
> > why is it building version 5.1 now? How does the version system
> > work?
>
>It uses the version number defined around line 455:
>
># library version is CS_VERSION.CS_APIVERSION
>csoundLibraryVersion = '5.1'
>
>If you would prefer not using this, just replace the following
>at line 644:
>
>             csoundFrameworkEnvironment.Command(
>                 i[0].replace('5.0', csoundLibraryVersion),
>                 i[1].replace('5.0', csoundLibraryVersion),
>                 i[2].replace('5.0', csoundLibraryVersion))
>
>with:
>
>             csoundFrameworkEnvironment.Command(i[0], i[1], i[2])
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
>for problems?  Stop!  Download the new AJAX search engine that makes
>searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
>http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2005-12-14 10:36
FromVictor Lazzarini
SubjectRe: [Cs-dev] SConstruct changes for tclcsound
The build works on OSX now.

Victor

At 10:25 14/12/2005, you wrote:
>On Wednesday 14 December 2005 11:08, Istvan Varga wrote:
>
> > On Wednesday 14 December 2005 11:02, Victor Lazzarini wrote:
> >
> > > I agree. Can you make these changes?
> >
> > I already made them, just did not commit. I will do some testing
> > first.
>
>Now in CVS. Hopefully the change did not break the Win32 build
>again, but if it did, then it could be built differently on each
>platform.
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
>for problems?  Stop!  Download the new AJAX search engine that makes
>searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
>http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2005-12-14 11:22
FromVictor Lazzarini
Subject[Cs-dev] update on OSX installation structure
Things are starting to get clearer now on OSX. It looks like the
best way to distribute the csound library is as a framework, which
is copied into /Library/Frameworks. This is working fine on my machine.

Now it's just the matter to decide where to put the programs. I'd suggest
doing the same as in Linux and putting everything on /usr/local/bin, since
this is generally on the path.

Another idea is put them on the framework, in a bin subdirectory (and put
links to them on /usr/local/bin). It would be as:

/Library/Frameworks/CsoundLib.Framework
                                      /bin  -> Versions/Current/bin

                                     /Versions
                                           /Current -> 5.1
                                           /5.1
                                                /bin
                                                        csound
                                                        cswish
                                                        cstclsh
                                                        lpanal
                                                        ...

I'm not sure whether this complicates the install.

The libraries (csnd, csoundapi~,tclcsound etc.) can also either go
in /usr/local/lib or have a similar arrangement inside the framework.

Any suggestions?

Victor



Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net