[Cs-dev] SCons not working any more with MSYS/MinGW
Date | 2006-01-01 22:07 |
From | Michael Gogins |
Subject | [Cs-dev] SCons not working any more with MSYS/MinGW |
I am one of the developers of the Csound 5 project. I created a build system for this project that uses SConstruct and, on Windows, MSYS/MinGW to build the entire project. This build system was working fine for years until a few days ago. I upgraded my Python installation to Python 2.4.2, and reinstalled MSYS and MinGW with all versions current as of this date. Now the build system does not work on Windows. It fails in the configuration portion of the build. The config tests produce compiler commands like this, and fail: gcc -Wall -g -gstabs -O2 -D_WIN32 -DWIN32 -DPIPES -DOS_IS_WIN32 -mthreads -DBETA -DUSE_DOUBLE -I. -IH -IC:\utah\usr\msys\1.0\local\include -IC:\utah\usr\mingw\include -IC:\utah\opt\Python24\include -IC:\utah\usr\mingw\include -IC:\utah\opt\lua50\include -IC:\utah\opt\Tcl\include -IC:\utah\opt\boost -IC:\utah\opt\jdk1.5.0\include -IC:\utah\opt\jdk1.5.0\include\win32 -IC:\utah\opt\pd-0.38-4-devel-2\src -I\usr\local\include -I\usr\include -c -o .sconf_temp\conftest_0.o .sconf_temp\conftest_0.c The problem appears to be caused by SCons using '\' to separate components of a pathname, instead of '/' which is what works with gcc. How can I instruct SCons to create pathnames with '/' instead of '\'? Is there any way to get the MSys sh to translate pathnames with '\' to pathnames with '/'? All commands passed to tools must use Posix style pathnames. I am getting desperate, thanks for any help you can provide. Regards, Mike Gogins ------------------------------------------------------- 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 |
Date | 2006-01-02 22:03 |
From | Oeyvind Brandtsegg |
Subject | [Cs-dev] massign resets controller |
I discovered that using massign inside an instr resets midi continuous controllers. Is this supposed to be so ? It would be good to be able to massign without resetting controllers, imho. An attached csd shows the behaviour, when instr 2 is called, gkctrl1 resets to zero (Csound version of 13th Dec 2005 on windowsXP, coundrc =-odac16 -iadc16 -b128 -B2048 -M0 -m0 -+rtaudio=pa --expression-opt -d -+raw_controller_mode=1) best Oeyvind |
Date | 2006-01-02 22:06 |
From | Oeyvind Brandtsegg |
Subject | [Cs-dev] re: massign resets controller |
Attachments | pgm_ch_ctrl.csd |
...and here's the attachment... > From: Oeyvind Brandtsegg [obrandts@online.no] > Sent: 2006-01-02 23:03:43 CET > To: csound-devel@lists.sourceforge.net > Subject: massign resets controller > > I discovered that using massign inside an instr resets midi continuous controllers. > Is this supposed to be so ? > > It would be good to be able to massign without resetting controllers, imho. > An attached csd shows the behaviour, when instr 2 is called, gkctrl1 resets to zero (Csound version of 13th Dec 2005 on windowsXP, coundrc =-odac16 -iadc16 -b128 -B2048 -M0 -m0 -+rtaudio=pa --expression-opt -d -+raw_controller_mode=1) > > best > Oeyvind |
Date | 2006-01-03 09:22 |
From | Istvan Varga |
Subject | Re: [Cs-dev] massign resets controller |
Attachments | None |
Date | 2006-01-03 15:06 |
From | Istvan Varga |
Subject | Re: [Cs-dev] massign resets controller |
Attachments | None |
Date | 2006-01-03 21:06 |
From | Oeyvind Brandtsegg |
Subject | re: [Cs-dev] massign resets controller |
great ! very useful. I also noticed that the vst plugin opcodes (vstinit family) seems to be gone, at least I can't use them, and they don't show when trying csound -z. Haven't tried rc2 yet, but will soon. Looking forward to usinng the chn opcodes. Oeyvind > From: Istvan Varga [istvan_v@fibermail.hu] > Sent: 2006-01-03 16:06:13 CET > To: csound-devel@lists.sourceforge.net > Subject: Re: [Cs-dev] massign resets controller > > massign now has an optional third argument which defaults to 1. > If this is zero, the controllers are not reset. > > On Monday 02 January 2006 23:03, Oeyvind Brandtsegg wrote: > > > I discovered that using massign inside an instr resets midi continuous controllers. > > Is this supposed to be so ? > > > ------------------------------------------------------- > 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 > |
Date | 2006-01-03 21:33 |
From | Istvan Varga |
Subject | Re: [Cs-dev] massign resets controller |
Attachments | None |
Date | 2006-01-05 07:46 |
From | jpff@codemist.co.uk |
Subject | Re: [Cs-dev] massign resets controller |
Did you change the manual? ==John ffitch ------------------------------------------------------- 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 |
Date | 2006-01-05 10:10 |
From | Istvan Varga |
Subject | Re: [Cs-dev] massign resets controller |
Attachments | None |