The equivalent to ${container_loc} is
${selected_resource_loc}/.. (note the slash and
dots).
Hey Toni,
I downloaded eclipse 3.5 right away (3.5M5),
changed build directory to ${selected_resource_loc} (without telling anyone)
but still no advance :(
Am I doing something wrong here?
Project
> Properties > C/C++ Build > Builder Settings:
Build command : D:\bin\bash.exe -c "echo build directory `pwd` && make
-j5 && echo FINISHED" Build
directory: ${selected_resource_loc}
Still gives
****
Build of configuration mkdir for project CURRENT_B ****
D:\bin\bash.exe
-c echo build directory `pwd` && make -j5 && echo FINISHED
build directory D:\home\jeroend\eclipse\CURRENT_B make: *** Geen doelen
gespecificeerd en geen makefile gevonden.
Stop.
======
Well, I think I shall have to look into registering
a dynamicVariable.
Tnx,
Jeroen
Leherbauer, Anton (Toni)
schreef:
You can recreate the same behaviour by registering your
own dynamicVariable as suggested by Olexiy.
Or - if you are using Eclipse 3.5 - you can also use
${selected_resource_loc}/.. (but don't tell others ;).
HTH
Toni
Thanks for the info. Is there however
any other way to perform a build in the current directory? We now use an
external tool for this but this doesn't link the errors with the problems
view (which is inconvenient).
Thanks again for the quick
response,
Jeroen
Leherbauer, Anton (Toni) schreef:
Hi,
expansion of certain eclipse variables has been
disallowed due to problems with deadlocks.
In general the use of variables which depend on
the current selection in the UI are not allowed.
Regards,
Toni
Hi,
I think that variable was deprecated, but not sure 100%
You may reintroduce it again
using org.eclipse.core.variables.dynamicVariables extension
point.
Or maybe that was not good idea to remove those variable and
someone may return them back.
We used some of deprecated variables too for our build system and
had to find workaround.
--
Olexiy
On Mon, Mar 9, 2009 at 9:43 AM, Jeroen
Dhollander <jeroen.dhollander@xxxxxxxxxxxxxxxxxx>
wrote:
Hey
all,
In our company we have a huge project, which uses custom
makefiles. To speed things up we created a build configuration which
only builds the directory of the currently selected file. To achieve
this behaviour we used ${container_loc} as "Build Directory". So
our build configuration looks like this ( project > properties
> C/C++ Build > Builder Settings ): - Build command:
D:\bin\bash.exe -c "echo build directory `pwd`
&& make && echo FINISHED" - Build
Directory: ${container_loc}
In CDT 5.0.1 and 5.0.2
this works correctly as you can see in the build output:
****
Build of configuration mkdir for project CURRENT_B
****
D:\bin\bash.exe -c echo build directory `pwd` &&
make && echo FINISHED build directory
D:\home\jeroend\ws_i\b\panos\rapidlogic make: Niets te doen voor
`lib'. FINISHED
However, in CDT 6.0.0 the ${container_loc}
variable doesn't seem to work as we always stay in the project
root:
**** Build of configuration mkdir for project CURRENT_B
****
D:\bin\bash.exe -c echo build directory `pwd` &&
make -j5 && echo FINISHED build directory
D:\home\jeroend\eclipse\CURRENT_B make: *** Geen doelen
gespecificeerd en geen makefile gevonden. Stop.
Am I
overlooking something or is this a bug?
With kind
regards,
Jeroen _______________________________________________ cdt-dev
mailing list cdt-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
--
Jeroen Dhollander
IPD R&D Belgium - Software design team
Jeroen.Dhollander@xxxxxxxxxxxxxxxxxx
+32(0)3/240.38.07
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
--
Jeroen Dhollander
IPD R&D Belgium - Software design team
Jeroen.Dhollander@xxxxxxxxxxxxxxxxxx
+32(0)3/240.38.07
|