I remember seeing somewhere in documentation (maybe the manual) that outputs must be located where the tupfile is. And there were discussions about it in this forum. It was said that having "/" in the output sections in the tupfile would trigger an error. Now I can't find that text in the manual. Perhaps I was reading an older version of the manual somehow.
When you are dealing with thousands of files, you really don't want to mix them. In fact, we also use a separate work tree for all the intermediate files. The source control is Perforce, not Git. I would really prefer Python parser. I've never heard of Lua before I read about Tup. There will be several people working on the project, and most of them probably never heard of Lua either. While there are really good introduction examples for using tupfiles, there's nothing for using Lua other than one page API description. On the other hand, sometimes I would need to run calculation to figure the list of inputs and outputs, so without a scripting support this could be tricky. In the face of these uncertainties I might have to go with SCons, although it is reportedly very slow :( I've already tried Waf and found it not intuitive at all. Evgenii On Friday, June 20, 2014 7:25:27 AM UTC-7, Andrew Wagner wrote: > > Hello Evgenli! > > I can't answer you scalability question, but I can say that I have > personally used tup's out-of-source building feature configurations / > tup.config on a small codebase and it works. So that answers your second > question; you can keep your Tupfiles next to your sources and still have > tup generate your built files in a separate directory if you wish. Do > reconsider building in source, though; people still debate about it, but > many of the old reasons for an out-of-source build are obsolete if you're > using git/tup. > > One thing you should be aware of is that the tup community is currently > split between the older native parser, and a newer lua based parser; if it > is an existing codebase you're building, you might need the power of the > lua stuff. > >> >> > -- -- 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.
