Description
Porytiles currently uses a path-based command flow. I.e. you must supply absolute or relative paths for your input tileset, your behaviors header, and your output location.
As an alternative, provide a project-based flow. I.e. if Porytiles is executed within a pokeemerald project folder, you should be able to call it like this, using the new syntax referenced in #39.
## note the new compilation command syntax ##
# compile a primary
porytiles compile tileset -Wall my-cool-primary
# compile a secondary
porytiles compile tileset -Wall my-cool-secondary my-cool-primary
It will automatically look for the Porytiles-format my-cool-primary in data/tilesets/primary/my-cool-primary/porytiles, it will look for the behaviors header at include/constants, and it will output your results to data/tilesets/primary/my-cool-primary. Similarly for my-cool-secondary.
The legacy workflow can be supported via the legacy compile-primary and compile-secondary commands, i.e.
porytiles compile-primary -Wall -o data/tilesets/primary/my-cool-primary data/tilesets/primary/my-cool-primary/porytiles include/constants/metatile_behaviors.h
porytiles compile-secondary -Wall -o data/tilesets/secondary/my-cool-secondary data/tilesets/secondary/my-cool-secondary/porytiles data/tilesets/primary/my-cool-primary/porytiles include/constants/metatile_behaviors.h