Hi,
I have a C project with 36 (and growing) variants where each can be build
with debug and release configuration. It is an embedded project where the
firmware for a controller device is compiled in multiple variants for
different sets of tools attached to the controller.
If I understand it correctly, with tup, I would need a variant directory
for configuration and build outputs for each variant in the root directory
of the project. This would translate to 36 debug variant directories plus
36 release variant directories. That is ok but is there a way to not put
them in the root directory of the project without completely restructuring
my soure code?
The project is basically structured like this
project_root/
.git
core_sources
lib_sources
tool_driver_sources
makefile # currently
.other-
.dev_tool-
.config_files
So for navigating all sources plus the variant configurations in an IDE, it
would be nice to not have 72 variant directories directly under the project
root but in some subdirectory. Is there a way to achieve this? After
studying the tup manual it looks like there is no straight forward way.
I could think of something like
project_root/
.git
build/
.tup
variant_a
variant_b
...
variant_xy
core_link -> ../core_sources
lib_link -> ../lib_sources
drv_link -> ../tool_driver_sources
core_sources
lib_sources
tool_driver_sources
.other-
.dev_tool-
.config_files
But I have to use this project on windows and somehow file system links
feel wonky on windows. Would encourage me to do it like this anyways?
--
--
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/dd592026-d3da-4d2d-9c36-2ac63df00f7an%40googlegroups.com.
