Description Chris Recoskie 2010-11-10 10:31:44 EST

Go to the project properties->C/C++ Build->Environment property page, and undefine an environment variable.  The variable's original value from the shell is still passed to the remote process even though you theoretically undefined it.

There is some legacy code (copied from the CDT make builder - no longer used BTW) in the remote make builder checks the make info to see whether it should override the environment or just append to it.  Since the value never gets set to specify that the environment should be replaced, the code that clears out the remote environment so that the one specified by the user takes over entirely is never called.

The solution is to always clear the remote environment.  The list the user edited will have already contained the remote environment, so their edits should be fully respected.