If it is indeed possible to get it to build many binaries in a single build 
then subpackages would be a good way to handle it. But seeing as the build 
type is passed to the configure script I thought it would probably be a 
pain to do that so I suggested flavours.

You can rename the installed binary so the flavours don't conflict. Easiest 
way to handle the PLIST is probably to name the files (binary, desktop 
file, etc) based on the flavour (e.g. minivmac-ii) set a variable with the 
extension part ("SUFFIX=-ii") set that in SUBST_VARS ("SUBST_VARS=SUFFIX") 
and use that in PLIST ("bin/minivmac${SUFFIX}")

The other step to allow installing together is to adjust FULLPKGNAME so 
that pkg_add doesn't treat them as conflicting. With the above, 
FULLPKGNAME=minivmac${SUFFIX}-${V} should do.

-- 
  Sent from a phone, apologies for poor formatting.

On 30 July 2024 07:22:24 "Anthony J. Bentley" <bentley@openbsd.org> wrote:

> Jag Talon writes:
>> By default, Mini vMac emulates a Macintosh Plus. Another popular model
>> that Mini vMac emulates is a Macintosh II because it offers more memory
>> (8MB instead of 4MB), a larger screen, and color.
>
> So /usr/local/bin/minivmac will emulate only one machine or the other
> depending on which flavor is installed. Can you convince the build system
> to generate emulators for multiple machines as separate executables that
> could be installed side by side? Because if someone is interested in
> emulating both types of machines, it would be a real pain to have to run
> pkg_delete and pkg_add every time to switch between them.