Hi there, I recently started using tup as an alternative to waf, and I'm very happy with it. However there is one issue: It seems to be incompatible with OS X resource forks.
As part of a build step, I have to create and append to an object's resource fork, but that fails under tup. I think it's because the filesystem that tup instantiates for builds is not compatible with OS X resource forks and extended attributes. Is that correct, and is there any way to work around that? Thanks! Best, Casey -- -- 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.
