unless its set for each target, it uses the default value. same os for single-target, really (except you cant set it via the IDE in multi-target because the IDE doesn’t support settings for multi-target yet ;).
Island generates each architecture separately (for consistency as the other non-Cocoa platforms dont’ support merging). Only executable projects are merged into a final single fat/universal binary.
you can override this my setting MergeArchitectures to True or False, on either (it default to True for Toffee always, and for Island if the output type is “Executable”). But I suggest to not mess with that, unless you have to.
Headers of curse cant be merged (easily) so even Toffee generates 2 or more; in most cases they will be virtually identical.
If you do want them merged, set MergeArchitectures so you can safe the extra step. Caveat that I didn’t test how Island reacts to then trying to reference the from a different island project, as project reference or regular reference, but I’d love to hear if it goes ok.
Unless set differently, they probably all write to the same folder, ie the one that builds later overwrites then one from earlier. youn might wanna set OutputPathUsesModes to True, if you don’t wanna set explicit OutputPaths for each target manually.
Hmm, yet in your other thread we were talking about problem with an Island header file…