Hi Mike, Thank you. I will try this as soon as possible. If there are issues with the new version, I will let you know.
- Gerhard Am Freitag, 28. September 2018 20:09:39 UTC+2 schrieb [email protected]: > > Unfortunately tup complains about all unexpectedly written files, not just > those written inside the hierarchy. Perhaps ignoring those outside of the > hierarchy would be more consistent since that's how inputs are handled. > Though I think I'd prefer to change the behavior of inputs instead so that > full_deps is the default, if it can be done in a performant way. > > However, I just landed some preliminary support for ignoring unexpected > files in v0.7.8. So you might be able to ignore them using a construction > like this: > > : |> yourcmd... |> output.o ^/FLEXnet/ > > This should ignore any file accesses (both reads and writes) to files that > contain a directory path "FLEXnet". Note that the feature is very new, so > it is highly likely there are still some issues with it. If you try to use > it, I'd appreciate any feedback on whether or not it works for your case. > > See also: https://github.com/gittup/tup/issues/182#issuecomment-425518883 > > -Mike > > On Thu, Sep 27, 2018 at 11:30 AM Gerhard Giefing <[email protected] > <javascript:>> wrote: > >> I think I have an idea, why this directory is also part of the tup >> hierarchy. We include one file called ToolSetRules, where we define some >> Macros. In there we export nearly all Environment variables: >> >> # export these Windows environment variables to the build child-processes >> export ALLUSERSPROFILE >> export APPDATA >> export CommonProgramFiles >> export CommonProgramFiles(x86) >> export CommonProgramW6432 >> export COMPUTERNAME >> export ComSpec >> export PROCESSOR_LEVEL >> export PROCESSOR_REVISION >> export ProgramData >> export ProgramFiles >> export ProgramFiles(x86) >> export ProgramW6432 >> .... >> >> Can it be, that this is why files in C:\ProgramData are also recognized >> by tup, and not only within the project itself? >> >> -- >> -- >> tup-users mailing list >> email: [email protected] <javascript:> >> unsubscribe: [email protected] <javascript:> >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- -- 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.
