|Empty build_files variable [message #806864]
||Sat, 25 February 2012 16:22
| Ian Edwards
Registered: February 2012
I am trying to put together an external builder for our (ancient) build system, specifically I want to be able to kick off a subset of our build when a particular file is modified.|
All that I need to make this work, I believe, is a list of the files that have been modified to cause the build, when I get this, I can simply cd to the directory in which each file exists and issue our bespoke build command - iterating over all of the modified file directories in this way will result in the build I want.
Looking at the documentation, and indeed the description of the variable 'build_files' I believe I should get precisely that - a list of the files that caused the build to be initiated - but it is coming back with an empty list...
What am I doing wrong?
The description I see for build_files is:
"Returns the set of absolute file system paths whose modification caused the current build. A list of the characters, 'a' (added), 'c' (changed), 'r' (removed), 'f' (files only), 'd' (directories only), can be supplied as an argument to limit the file list to just those types of deltas. Defaults to all deltas."
The CDT version I'm using is: 220.127.116.11002161416 (in RTC 18.104.22.168, Eclipse 3.5.2.R35) but I have also tried using CDT 22.214.171.124202111925 (using RTC 126.96.36.199 under Eclipse 3.7.1.r37) and it also doesn't seem to do what I expect.
[Updated on: Sat, 25 February 2012 21:07]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.01916 seconds