[news.eclipse.tools.cdt] fun with paths in eclipse

[Tim Black <timblaktu@xxxxxxxxx>]

I am using eclipse galileo on win/cygwin and have an eclipse CDT project that includes a nested source code folder structure. I have makefiles in the nested subfolders that I sometimes want to make without doing a Build All (Ctrl+B), so I set up some make targets. (This is the point of make targets, no?) I chose to put a make target everywhere I've got a makefile, to serve as a wimple wrapper for invoking my makefiles. 

ProjectRoot/
 makefile
 SubFolder1/
   makefile
   source1.h
   source1.cpp
 SubFolder2/
   makefile
   source2.h
   source2.cpp

The problem lies in properly specifying path information in the "Build command" in the "Modify Make Target" dialog. The only way I've gotten it to work is to put the full, absolute path in there, like follows:

make -C /cygdrive/c/ProjectRoot/SubFolder1/

This is of course, horrible, because none of my colleagues can use this shared project without changing all the "Build Command" settings.

I had first tried a "Build Command" like:

make -C SubFolder1/

thinking eclipse would understand I meant relative to the top-level of the project. But this doesn't work. By the way, all of the above work fine if I cd to ProjectRoot and type the same command at the cygwin command line.

Is there a better way to do this? Why does the same make command behave differently in eclipse than it does at the command line?

I also have a general problem with the lack of support for relative links in eclipse external resource links. It presents a major obstacle when it comes to sharing multi-rooted projects. The external resource links seem to only work in an absolute path manner. I understand that there is support for path variables, but this still requires an absolute setting. Does anyone have an update or general thoughts on this issue?

Thanks!