Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Solution for: Latest changes in HEAD break C::B build

<< < (2/4) > >>

mandrav:

--- Quote ---1. How do you set the env vars, via win32 API (SetEnvironmentVariable()) or...?
--- End quote ---

wxSetEnv() to be cross-platform

--- Quote ---2. This is totally offtopic here, but, what is the exact function that calls the new process?
--- End quote ---

CompilerGCC::DoRunQueue() is actually spawning processes. CompilerGCC::Run() and the likes, just fill the commands queue that is processed by CompilerGCC::DoRunQueue().

Yiannis.

darklordsatan:
Ok, thanks! BTW, nice "666" post count

mandrav:
Hehehe, and I was replying to DarkLordSatan with my 666th post  :twisted:

Yiannis.

David Perfors:
I have troubles with this when using the unicode version of wx...
1. Instead of lib/gcc_dll/msw it is lib/gcc_dll/mswu
2. libwxmsw26.a and libwxmsw26_stc.a are also with the "u". (this coudl be changed by using WX_VER again)

tiwag:

--- Quote from: mandrav ---I forgot to note that custom variables are global C::B settings. The next logical enhancement will be to set them per-project/target.

Yiannis.
--- End quote ---


at least a "per project" setting is absolutely necessary before i can use this feature.
i don't want to edit everytime the globals when i have to compile one project with wx24 and the other with wx26,
another one with wx-dll and another another one with wx-static-lib ...
not already mentioned debug and release versions ...
wx has soooooo much flavours...

--tiwag

Navigation

[0] Message Index

[#] Next page

[*] Previous page