Author Topic: ENV VAR imported from either bashrc or profile, C::B not a child ?  (Read 266 times)

Offline DoingIsLearning

  • Single posting newcomer
  • *
  • Posts: 4
Hi everyone,

So I have really enjoyed the codeblocks experience so far but I have hit a bump in the road.

Environment variables imported in both ~/.bashrc , AND in /etc/profile don't seem to be imported during codeblocks Run.

If I open the project inside an Xterm terminal (i.e. codeblocks myproj.cbp) then codeblocks does act like a terminal child and loads the variables. Why is it not doing the same from launch bar? Am I missing something? 

I would expect I could just launch the application from launchbar and still have the environment variables available.
>> Could you point me to what additional steps are required?

Thank you once again for this great project!

PRETTY_NAME="Debian GNU/Linux 7 (wheezy)"
C::B  Release 10.05 rev 0
(spare me the chuckles! i know it's old but it's what was in the debian database)

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 8564
I don't think we can do anything about this problem.
It is a question that you should ask to the developers of your launcher/wm/de.
<debugger plugin maintainer>
(most of the time I ignore long posts)

Offline stahta01

  • Lives here!
  • ****
  • Posts: 4938
    • My Best Post
I think there is somewhere inside Code::Blocks to set which shell is used for some operations.
No idea if relates to your problem. And, I have no idea if CB works with other shells than the default shell.

Tim S.
C Programmer working to learn more about C++.
On Win7, compiling CB Trunk against wxWidgets WX_3_0_BRANCH branch.
On Debian Jessie, compiling CB Trunk against wxWidgets 2.8.12.
When in doubt, read the CB WiKi FAQ.