(moved from #122)
asar cli should 1) have the ability to use separate filenames for input and output rom, and 2) have the ability to ignore any existing rom file and force a clean rebuild.
idk how i'd want to design this though.
- could do
./asar patch.asm input.sfc output.sfc and add an option like --ignore-existing-rom which does the clean rebuild. but then there's asymmetry in that in the 3-argument form, arg 2 is used only for input, but with --ignore-existing-rom, it'd be only output.
- the same, but make the 3-arg form
./asar patch.asm output.sfc input.sfc. but output being before input feels a bit odd.
- could do
./asar patch.asm input.sfc output.sfc and allow specifying something like - or /dev/null as the input file to do a clean rebuild. but then we'd need to invent a name for it. (i'd rather use a custom name than tell people to use NUL on windows or /dev/null on linux. mostly because i don't want to acknowledge the existence of NUL.)
on second thought, output being before input also happens with other compilers (at least whenever i write makefiles by hand i seem to default to that), so maybe it's not that weird. i'm leaning towards 2 now.
(moved from #122)
asar cli should 1) have the ability to use separate filenames for input and output rom, and 2) have the ability to ignore any existing rom file and force a clean rebuild.
idk how i'd want to design this though.
./asar patch.asm input.sfc output.sfcand add an option like--ignore-existing-romwhich does the clean rebuild. but then there's asymmetry in that in the 3-argument form, arg 2 is used only for input, but with--ignore-existing-rom, it'd be only output../asar patch.asm output.sfc input.sfc. but output being before input feels a bit odd../asar patch.asm input.sfc output.sfcand allow specifying something like - or /dev/null as the input file to do a clean rebuild. but then we'd need to invent a name for it. (i'd rather use a custom name than tell people to use NUL on windows or /dev/null on linux. mostly because i don't want to acknowledge the existence of NUL.)on second thought, output being before input also happens with other compilers (at least whenever i write makefiles by hand i seem to default to that), so maybe it's not that weird. i'm leaning towards 2 now.