A file does not have to be locked when opened on Windows, but what I am
actually doing something like:
ifeq ($(MODE),)
MODE = common
include Tupfile
MODE = debug
include Tupfile
MODE = profile
include Tupfile
MODE = release
include Tupfile
else
ifeq ($(VARIANT),)
VARIANT = common
include Tupfile
VARIANT = shared
include Tupfile
VARIANT = static
include Tupfile
VARIANT =
else
# lots of stuff based on $(MODE) and $(VARIANT)
endif
endif
The real thing has more layers than this--including building with multiple
compilers, cross-compiling, etc.. The "variants" mechanism does not work
as (AFAICT) there is no way for them to share build artifacts (e.g. object
files used in both static and shared linking variants).
Sure, the above can be refactored into a separate Tupfile for each layer,
but I would rather not spread out the Cartesian product generation over
four or five files.
--
--
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/8da79d74-b0da-4d2b-87e1-0178613869d8o%40googlegroups.com.
