[news.eclipse.tools.cdt] Re: CDT6.0 container_loc

[thundernail@xxxxxxxxxx (Thundernail )]

Thanks for the reply, 

Andrew Gvozdev wrote:

> Thundernail wrote:
> > have I seen this correct, that the variable 'container_loc' of the build 
> > command is not usable any more?

> The problem with these variables is that the build plugin is independent 
> of UI plugins and so it cannot expand UI variables. The best you can do is 
> to use build variables like ${ProjDirPath}.

The build plugin has the ${selected_resource_loc} variable, so it should 
be possible to give the path of the directory.

> > Is there any solution to set the workdirectory of the make command to the 
> > directory of the active file?

> If you use "Build Project" command it is always executed in project build 
> directory. As an alternative you could try Make Target view. If you create 
> its  target in a subfolder the working directory will be that subfolder. 
> This holds true for not managed build only. 

I don't linke the idea to set up the Make Targets for around 100 
directorys ;-)


My solution at the moment is a Makefile at the protject root, that 
forwards to the Makefile in the directory of the ressource.

My build command: 
   make RESOURCE_LOC=${selected_resource_loc}

The Makefile in the project root directory:
   CONTAINER_LOC:=$(shell dirname "${RESOURCE_LOC}")

   all:
       @$(MAKE) -C ${CONTAINER_LOC}/ all;