We recently had a discussion here about distributing versions of
Csound with host software, and Sigurd suggested that I could simply
package Csound and have my host search for it in a specified location
before looking in the standard paths. How do I go about this? Is there
an eloquent and cross platform approach?

That's exactly what I do in Surmulot:
http://www.zogotounga.net/surmulot/surmulot.html

Emacs overrides PATH settings so that they point to the Csound shipped 
with Surmulot; the user has an option to ignore this mechanism and use 
the system-wide Csound.

Works fine in Windows and Linux

Stef

Can I just call const char *csoundGetEnv(CSOUND *csound, const char
*name); beore I run any instance of Csound, and pass my own
OPCODEDIR64 as an argument?

On 3 February 2013 09:29, Stéphane Rollandin  wrote:
> That's exactly what I do in Surmulot:
> http://www.zogotounga.net/surmulot/surmulot.html
>
> Emacs overrides PATH settings so that they point to the Csound shipped with
> Surmulot; the user has an option to ignore this mechanism and use the
> system-wide Csound.
>
> Works fine in Windows and Linux
>
> Stef
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>

> Can I just call const char *csoundGetEnv(CSOUND *csound, const char
> *name); beore I run any instance of Csound, and pass my own
> OPCODEDIR64 as an argument?

I don't know about the C API. I haven't programmed in C for the last 20 
years :)

Stef

Great. Thanks for the heads up.

On 4 February 2013 01:51, Bernt Isak Wærstad  wrote:
> Hadron uses the csoundSetGlobalEnv-function (with "OPCODEDIR64" as the first
> argument and a c-string with the path to the custom directory as the second
> arg) when the plugin is initialized. We also use the same function to set
> "INCDIR".
>
>
> On Sun, Feb 3, 2013 at 11:56 AM, Rory Walsh  wrote:
>>
>> Can I just call const char *csoundGetEnv(CSOUND *csound, const char
>> *name); beore I run any instance of Csound, and pass my own
>> OPCODEDIR64 as an argument?
>>
>> On 3 February 2013 09:29, Stéphane Rollandin 
>> wrote:
>> > That's exactly what I do in Surmulot:
>> > http://www.zogotounga.net/surmulot/surmulot.html
>> >
>> > Emacs overrides PATH settings so that they point to the Csound shipped
>> > with
>> > Surmulot; the user has an option to ignore this mechanism and use the
>> > system-wide Csound.
>> >
>> > Works fine in Windows and Linux
>> >
>> > Stef
>> >
>> >
>> >
>> > Send bugs reports to the Sourceforge bug tracker
>> >            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> > Discussions of bugs and features can be posted here
>> > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> > csound"
>> >
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
>
>
> --
> Mvh.
>
> Bernt Isak Wærstad
>
>

Hi Rory,

Editing csoundSetGlobalEnv ensures that Csound picks up the opcodes from your own Csound package, but your host may still use a different csound engine. On Windows, if you want your host to run the csound engine from your package as well, you have to do two things:

1. In project settings turn on delay loading of the main csound dll (normally csound64.dll.5.2, but we renamed it to avoid conflicts).
2. Modify the VST wrapper to use SetDllDirectoryA when creating the plugin. I've attached a piece of our wrapper code you could look at. 

Sigurd

-----Original Message-----
From: Rory Walsh [mailto:rorywalsh@ear.ie] 
Sent: Monday, February 04, 2013 2:59 AM
To: csound@lists.bath.ac.uk
Subject: Re: [Csnd] forcing a host to use its own Csound package?

Great. Thanks for the heads up.

On 4 February 2013 01:51, Bernt Isak Wærstad  wrote:
> Hadron uses the csoundSetGlobalEnv-function (with "OPCODEDIR64" as the 
> first argument and a c-string with the path to the custom directory as 
> the second
> arg) when the plugin is initialized. We also use the same function to 
> set "INCDIR".
>
>
> On Sun, Feb 3, 2013 at 11:56 AM, Rory Walsh  wrote:
>>
>> Can I just call const char *csoundGetEnv(CSOUND *csound, const char 
>> *name); beore I run any instance of Csound, and pass my own
>> OPCODEDIR64 as an argument?
>>
>> On 3 February 2013 09:29, Stéphane Rollandin 
>> wrote:
>> > That's exactly what I do in Surmulot:
>> > http://www.zogotounga.net/surmulot/surmulot.html
>> >
>> > Emacs overrides PATH settings so that they point to the Csound 
>> > shipped with Surmulot; the user has an option to ignore this 
>> > mechanism and use the system-wide Csound.
>> >
>> > Works fine in Windows and Linux
>> >
>> > Stef
>> >
>> >
>> >
>> > Send bugs reports to the Sourceforge bug tracker
>> >            
>> > https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> > Discussions of bugs and features can be posted here To unsubscribe, 
>> > send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>> >
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             
>> https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here To unsubscribe, 
>> send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>
>
>
>
> --
> Mvh.
>
> Bernt Isak Wærstad
>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"