We have debug and release builds, and our source tree include many
projects. Our developers usually focus on a set of projects (sometimes only
building debug versions) and never compile the others. Meaning, if using
in-dir builds, they could build the desired flavor with "tup
myproject/debug64" or "tup myproject/release64" for example.
For variants, I could not figure out how to build a specific node. How do I
tell tup to build a specific node for that variant? Like, tup variant-name
myproject.
Now, for in-dir builds, I came up with a little trick to avoid repetition.
I have a common file that does the work, and it sits a level above my build
directories. The Tupfiles in these build directories include this common
file after setting the config type (that the common file uses to chose the
right compiler and link flags, etc). It works, but I wonder if there's a
different, easier technique I can use? This is how the directory structure
looks like:
common_file
debug/Tupfile
release/Tupfile
And the "debug" Tupfile has these lines:
include_rules
Config = debug
include ../common_file
--
--
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/tup-users/72494cb8-162f-481c-a0cd-1b6a43cbced1%40googlegroups.com.
