This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 167294 - bashrc analog for remote connection
Summary: bashrc analog for remote connection
Status: STARTED
Alias: None
Product: cnd
Classification: Unclassified
Component: Remote (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@cnd
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-18 10:25 UTC by leniviy
Modified: 2014-04-14 14:35 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description leniviy 2009-06-18 10:25:12 UTC
Hi. I need to set some environment variables prior to running any build or debug tool on remote machine. Currently I
have to use wrapper scripts for all tools (gcc,make,gdb) which sets up the environment first.
.bashrc works if user shell in /etc/passwd is bash, but my shell is 'ksh' and I can't change it because I have no root
password.

I think we need an additional option in "Host Properties" window. Something like "session init script path"
Comment 1 Andrew Krasny 2009-10-30 09:22:03 UTC
Another use case:

----------------------------------- 
Hello



Im trying to use netbens in a remote development host but without success



Generally I have access to this host via ssh, and in this host I compile and run my code. To compile my code I must load
path of compilers whit this instruction: "module load name_of_compilers "



This istruction call a user interface that provides for the dynamic modification of the user's environment via modulefiles.

this is the link of this module package: http://linux.die.net/man/1/module



My problem with netbeans is that I'm not able to load compilers path ...



there is a solution to this problem?



thank you very much



gg

-----
Comment 2 Andrew Krasny 2009-11-05 11:02:29 UTC
Will not add this functionality to the current release.
Actually, problems with environment could be solved using existent means... 

- if some environment variable needs to be setup for make - just add something like "export VAR=VAL" to a Makefile
(it will also have effect on all executed commands from make [i.e. c/c++/etc... ])

- if some environment variable is needed for the execution (Run) - just add this variable in "Environment Variables"
under "Run" section in project's properties

- if some script needs to be executed before make - use .build-pre section of the Makefile (in case of managed project)
or modify own makefile (in case of Makefile-based project).

- another option for the Makefile-based project is to configure the IDE to use a wrapper script instead of make