Both CsoundVST.py and _CsoundVST.so or .dll have to be in the same
directory, and must be either in the local (./) directory, or in directories
found in the PYTHONPATH environment variable.  The -outdir option causes
SWIG to generate these files in the same directory that SConstruct is in,
namely csound5. I tried to put in rules to copy files but the -outdir option
works better. It requires a recent version of SWIG (currently the only
version of SWIG that I'm confident can build CsoundVST is 1.3.21).

Therefore, please leave the -outdir option, and test the version of SWIG for
support of this option. It is the only way I found to reliably overcome the
shared library loading error.

----- Original Message ----- 
From: "steven yi" 
To: "Csound Developers Discussion List" 
Sent: Sunday, October 10, 2004 5:28 PM
Subject: [CSOUND-DEV:5393] CsoundVST


> Hi Michael and all,
>
> In trying to build CsoundVST today, I had to remove "-outdir ." from the
> SWIGFLAGS as SWIG didn't recognize those as options.  I removed it and
> it seemed to work fine.  Any problems if I remove them from the
> SConstruct file?
>
> Also, it seems no matter what I try, when trying to run CsoundVST, I get:
>
> ./CsoundVST: error while loading shared libraries: _CsoundVST.so: cannot
> open shared object file: No such file or directory
>
> Running ldd on CsoundVST, I get:
>
>  _CsoundVST.so => not found
>         libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x07c49000)
>         libpthread.so.0 => /lib/tls/libpthread.so.0 (0x00647000)
>         libm.so.6 => /lib/tls/libm.so.6 (0x004b0000)
>         libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00338000)
>         libc.so.6 => /lib/tls/libc.so.6 (0x00393000)
>         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x0037a000)
>
> I also find that trying to run the Windows build that you've put
> together I get the same error and thus am unable to run CsoundVST on
> WinXP.  On both XP and Linux I've tried moving the _CsoundVST.so or .dll
> into system folders and /usr/local/lib and I've set up PYTHONPATH to the
> location of _CsoundVST.so and CsoundVST.py.  I can run CsoundVST within
> python by starting python and doing "import CsoundVST", just not the
> executable.
>
> Any help on the linking issue with CsoundVST executable would be
> appreciated!
> steven
>
>

Hi Michael,

I had 1.3.19 installed and tried 1.3.22 but that was no good.  1.3.21 
worked fine and I was able to use "-outdir .".  However, the shared 
library loading error was not resolved and the same error message 
appeared.  Again, it seems fine to use from python shell, but the 
executable can't find the library and ldd lists it as not found.  
PYTHONPATH is set and botht the lib and .py files are in the directory. 

Ha!  Okay, I just tried something and it worked. Changing the LINKFLAGS to:

guiProgramEnvironment.Prepend(LINKFLAGS = ['-mwindows', './_CsoundVST.so'])

(appending the "./" to _CsoundVST) made it such that CsoundVST was able 
to load.  I noticed when using ldd on CsoundVST before, the only library 
that wasn't in a usual lib directory had a fully path:

 /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x0037a000)

All of the other libraries were linked to were in the system's lib 
directory.  So, my assumption is that libraries that are linked to but 
are not in the system directories or maybe those that do not have have 
standard names ('libXXX.so") need to have relative or absolute path's 
added.  I'm not very well versed in the intracicies of linking, so a 
more definitive answer would be appreciated by the more experienced here.

I've made that change for my SConstruct file, but my file currently is 
very different from the CVS version.  If this change works for you, 
would you be able to check it in?

Thanks,
steven

p.s. - I've attached my current SConstruct file in case anyone wanted to 
take a look as to how I'm going about doing it.  It's not quite finished 
as I haven't been able to devote too much time, but I think it's shaping 
up well.  I've got it now that it will build Loris and Python opcodes 
without depending on CsoundVST, and the file is moving much more towards 
using Alias's to build by target rather than configuration. 


Michael Gogins wrote:

>Both CsoundVST.py and _CsoundVST.so or .dll have to be in the same
>directory, and must be either in the local (./) directory, or in directories
>found in the PYTHONPATH environment variable.  The -outdir option causes
>SWIG to generate these files in the same directory that SConstruct is in,
>namely csound5. I tried to put in rules to copy files but the -outdir option
>works better. It requires a recent version of SWIG (currently the only
>version of SWIG that I'm confident can build CsoundVST is 1.3.21).
>
>Therefore, please leave the -outdir option, and test the version of SWIG for
>support of this option. It is the only way I found to reliably overcome the
>shared library loading error.
>
>----- Original Message ----- 
>From: "steven yi" 
>To: "Csound Developers Discussion List" 
>Sent: Sunday, October 10, 2004 5:28 PM
>Subject: [CSOUND-DEV:5393] CsoundVST
>
>
>  
>
>>Hi Michael and all,
>>
>>In trying to build CsoundVST today, I had to remove "-outdir ." from the
>>SWIGFLAGS as SWIG didn't recognize those as options.  I removed it and
>>it seemed to work fine.  Any problems if I remove them from the
>>SConstruct file?
>>
>>Also, it seems no matter what I try, when trying to run CsoundVST, I get:
>>
>>./CsoundVST: error while loading shared libraries: _CsoundVST.so: cannot
>>open shared object file: No such file or directory
>>
>>Running ldd on CsoundVST, I get:
>>
>> _CsoundVST.so => not found
>>        libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x07c49000)
>>        libpthread.so.0 => /lib/tls/libpthread.so.0 (0x00647000)
>>        libm.so.6 => /lib/tls/libm.so.6 (0x004b0000)
>>        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00338000)
>>        libc.so.6 => /lib/tls/libc.so.6 (0x00393000)
>>        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x0037a000)
>>
>>I also find that trying to run the Windows build that you've put
>>together I get the same error and thus am unable to run CsoundVST on
>>WinXP.  On both XP and Linux I've tried moving the _CsoundVST.so or .dll
>>into system folders and /usr/local/lib and I've set up PYTHONPATH to the
>>location of _CsoundVST.so and CsoundVST.py.  I can run CsoundVST within
>>python by starting python and doing "import CsoundVST", just not the
>>executable.
>>
>>Any help on the linking issue with CsoundVST executable would be
>>appreciated!
>>steven
>>
>>
>>    
>>
>
>
>
>  
>