Hi Satish, On Wed, Mar 14, 2018 at 6:34 AM, Satish K <[email protected]> wrote:
> I have the build scripts written with no/little dependence on the PATH. > All the commands are specified with full path. > However, any change in PATH rebuilds everything. > At the command prompt, working with different batch files, PATH may be > modified to run some postbuild tools which should not affect the build. > > tup upd <- initial build > postbuild.bat <- path is modified to run some tools > tup upd <- rebuilds everything > > Is there a way to configure Tup to ignore PATH changes ? > > Unfortunately no, the PATH environment is hardcoded as an environment dependency, since almost everything that would normally be executed is dependent on PATH in some way. Can you have postbuild.bat simply save the PATH when it starts up and restore it to the original value when it quits? Is it changing the PATH every time it runs or only the first run? (eg: is it continually making the PATH longer by appending the same thing every time) -Mike -- -- tup-users mailing list email: [email protected] unsubscribe: [email protected] options: http://groups.google.com/group/tup-users?hl=en --- You received this message because you are subscribed to the Google Groups "tup-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
