RE: Trying a workaround -- the 'include path' problem again
- Posted by Brian Broker <bkb at cnw.com> Jun 04, 2004
- 439 views
Actually, I think Win32Lib transparently handles the conversion of strings to pointers before making the call... The fact of the matter is that setting an environment variable within a program is a bit more complicated that simply calling SetEnvironmentVariable. from PSDK: "Programs started by the command processor inherit the command processor's environment variables." "By default, a child process inherits the environment variables of its parent process. However, you can specify a different environment for the child process by creating a new environment block and passing a pointer to it as a parameter to the CreateProcess function." -- Brian Bernie Ryan wrote: > > > posted by: Bernie Ryan <xotron at bluefrognet.net> > > Rubem: > > You need POINTERS. > atom str1, str2 > > str1 = allocate_string("EUINC") > str2 = allocate_string("C:\\util\\Euphoria\\includes") > > > VOID = w32Func(xSetEnv, {str1, str2}) > > bernie