On Mon, Apr 1, 2024 at 10:34 PM Mike Shal <[email protected]> wrote:
> On Mon, Apr 1, 2024 at 3:45 PM Pascal <[email protected]> wrote: > >> 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? >> > > Unfortunately at this time, tup only supports variants at the root of the > project (where 'tup init' is run). (There's been an issue open for a long > time, but I don't think anyone has tried to address it: > https://github.com/gittup/tup/issues/232 - it might be easier now with > the explicit variants merge, as previously the structure was tied to the > FUSE overlay but now it is just internal path manipulations). > Actually I just gave this a try and it seems to be pretty straightforward to do now. There are a few small details to work out, but if I can set aside some time to work on it I might be able to add support for "variants anywhere" later this week. -Mike -- -- 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/CA%2B6x0LX2My0XUU69%2Bx1ArQFhyC5nTSbXHWJMngag0x3paJ-Oaw%40mail.gmail.com.
