On Mon, 2016-12-05 at 11:34 -0800, [email protected] wrote: > I saw in the mailing list that in 2015 there was no (easy?) way to > accomplish it. What’s the recommendation today?
You have to be more clear about your intent, as I really don't understand your question. Generally tup creates directories when it needs them, so you don't have to do anything. > what is an easy way to build both debug and release in one run? (i.e > multiple targets), alternatively what is the recommended method to > have something like make DEBUG=1 ? Building multiple versions of the program in one run will just require you to have multiple versions of the rules involved, possibly in the form of a special file with rules, included in two separate directories with some special flags declared. > I use git submodule named ‘scream’ and get “tup warning: Writing to > hidden file '/Users/noam/w/hp-router/.git/modules/src/scream/index' “ > the files in the submodule are compiled as part of the main (parent) > project ( i.e. I don’t want to create libraries and link them) I don't think that this warning is from the compilation - how would your compilation process mess with git and why? Unless your compilation includes things like "git submodule update --remote" in every run, which is not the best idea... Regards, FCh -- -- 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.
