Closed TheNathannator closed 3 months ago
For non-matching, what about changing the default target to be the dol instead of neutering the check and progress targets?
Thanks for the PR! I agree with cadmic that adjusting the default target would be more ideal. Otherwise looks good.
For non-matching, what about changing the default target to be the dol instead of neutering the check and progress targets?
I'm not familiar with Ninja, so I never considered this as a possibility. That definitely sounds like a better option.
Looks good, thanks!
Additional re-configure dependencies can now be added in the project config. For example, for rb3, we moved object configuration to a pair of
objects.json
andflags.json
files so we can configure things per-version, and edits to these files need to cause a re-configure.Additionally, a non-matching build can now be performed by passing the
--non-matching
argument to configure.py. This skips the hash check and progress output, since those don't make sense to run in this configuration. A newEquivalent
object status has also been added, which will make an object be built and linked only in this configuration.I also fixed a small type-checking issue in configure.py,
config.version
was still anOptional[str]
after being set from args.