how to maintain two trunks?

Hi,
I'm working on a codebase that is to be used by two different compilers. I have
a trunk-branch layout but realize that does not work that well for this. What
seems to be needed are two "trunks" somehow. Is that possible?

I would like to be able to avoid to clutter the code with #ifdefs in regards to
the compilers, if possible. However, it goes further. Both compilers will for
example read certain project files. These files can't be "shared". I would like
to keep the same naming on files for both compilers too.

The problem now is, as being told in this forum, "feature" branches are to be
abandoned after merged back into the tree. There are some ways to avoid that,
but it seem to esoteric for me.

Anyway, anyone having some suggestions on how to deal with this scenario?

Totte
Received on 2011-05-07 21:07:32 CEST