Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
EnvVars Plugin and PATH
MortenMacFly:
--- Quote from: pkrcel on February 10, 2012, 01:26:40 pm ---Since I'm not all that accustomed with SVN/git and the like...you mean I shall retrieve all TRUNK and build Code::Blocks or I can do only the plugin?
--- End quote ---
...depends: If you link against a nightly, a checkout / build of the envvars plugin will be enough. If you are using an old version of C::B you'll have to wait for the next nightly. But I am sure it won't take long until then...
pkrcel:
Ok thanks, I thought to checkout into the latest nightly I installed for this trial....will try and see, otherwise I will lazily wait for anightly :P
Alpha:
--- Quote from: pkrcel on February 10, 2012, 08:57:19 am ---EDIT: having gone (again) through the Wiki you linked me, seems that the envvvars plugin is specifically designed to dabble with system EnvVars, as I deducted reading here
--- End quote ---
--- Quote from: oBFusCATed on February 10, 2012, 08:58:30 am ---Alpha: You are wrong here. It sets system env variables and at least on linux it works as expected.
--- End quote ---
Apologies for the incorrect information... it looks like I have mislead myself based on a previous edit I did to the plugin's page :-[. (I have now changed it to be more accurate.)
pkrcel:
No need to apologize Alpha, at least to my concern :)
In the meantime I went full league and built C::B from sources (SVN 7787) , with all the contrib plugins....unfortunately it has the same behavior as 10.05, attached you can find the debug-log. ..if that is of any help.
Now that I've a fully working build environment for C::B I should be able to check faster ;D
MortenMacFly:
--- Quote from: pkrcel on February 11, 2012, 01:17:21 am ---attached you can find the debug-log. ..if that is of any help.
--- End quote ---
Hmmm, I don't see what could go wrong now. Can you strip down you project to a minimalistic example and provide me with exact steps what you do to achieve this "error"? Also, please attach your (zipped) default.conf file - at least the ennvars section, starting with:
--- Code: --- <envvars>
<sets>
<default>
[...]
--- End code ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version