Does it need to be via the API? You can just call the C library function 
getenv() with the required names.

Richard Dobson



steven wrote:
> Hi all,
> 
> Is there a way through the host API or GLOBALS/ENVIRON struct to get 
> SFDIR, SSDIR, SADIR, etc.?
> 
> thanks,
> steven
> 
> 

Hi all,

Is there a way through the host API or GLOBALS/ENVIRON struct to get 
SFDIR, SSDIR, SADIR, etc.?

thanks,
steven

I thought about that, but there's this in the csound.h:

/**
        * Sets an evironment path for a getenv() call in Csound.
        * you can also use this method as a way to have different
        * csound instances have different default directories,
        * change the default dirs during performance, etc..
        *
        * Currently, Csound uses these 'envi' names only:
        *       "SSDIR", "SFDIR", "SADIR", "SFOUTYP", "INCDIR",
        *               "CSSTRNGS", "MIDIOUTDEV", and "HOME"
        */
        PUBLIC void csoundSetEnv(void *csound, const char 
*environmentVariableName, const char *path);

So I figured a corresponding call would make sense in this case. 

steven

Richard Dobson wrote:

> Does it need to be via the API? You can just call the C library 
> function getenv() with the required names.
>
> Richard Dobson
>
>
>
> steven wrote:
>
>> Hi all,
>>
>> Is there a way through the host API or GLOBALS/ENVIRON struct to get 
>> SFDIR, SSDIR, SADIR, etc.?
>>
>> thanks,
>> steven
>>
>>
>
>
>

Indeed so; I hadn't allowed for the possibility of a ~set~ function 
without a matching ~get~ in the API.
:-)


Richard Dobson

steven wrote:

> I thought about that, but there's this in the csound.h:
> 
> /**
>        * Sets an evironment path for a getenv() call in Csound.
>        * you can also use this method as a way to have different
>        * csound instances have different default directories,
>        * change the default dirs during performance, etc..
>        *
>        * Currently, Csound uses these 'envi' names only:
>        *       "SSDIR", "SFDIR", "SADIR", "SFOUTYP", "INCDIR",
>        *               "CSSTRNGS", "MIDIOUTDEV", and "HOME"
>        */
>        PUBLIC void csoundSetEnv(void *csound, const char 
> *environmentVariableName, const char *path);
> 
> So I figured a corresponding call would make sense in this case.
> steven
> 

=)

I ended up using getenv anyways and have my soundFonts loading now from 
SSDIR and SFDIR(which is nice as I keep a copy of SSDIR synced up on 
different computers and only have to worry about moving the work files 
in between).  I figure the opcode lib stuff is going through some 
reworking anyways so might as well go with the perfectly fine interim 
solution. 

steven



Richard Dobson wrote:

> Indeed so; I hadn't allowed for the possibility of a ~set~ function 
> without a matching ~get~ in the API.
> :-)
>
>
> Richard Dobson
>