On Sun, Jun 22, 2014 at 20:06:41 +0200, Andrew Wagner wrote: > Like I said, people debate about this :)
I was more disputing the "git/tup make out-of-source build reasons obsolete" part since I actually like out-of-source a lot *more* with git. For example, with SVN, you're basically juggling multiple source trees with branches *anyways*. I don't know how tup would make them any less desireable either. > And of course it depends on your application. In my application many > of our targets are generating code snippets, and it is convenient to > have them next to the other code they need to interface with when > we're debugging them. Hmm. I've had no issues with debugging sources that live in the build tree (i.e., the paths from the debuginfo work just fine in the debugger; both in VS and gdb). (FWIW, I think there are ~3000 code-gen related targets for each language binding enabled in the project as well; at least according to Ninja.) --Ben -- -- 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.
