Using -export command to automate multi cart package building and blocked by a number of bugs:
- unable to specify HTML plate path (only works if export is actually performed from home folder)
- inconsistent path parameters between bin and html exports:
# works for html pico8.exe carts\cart_0.p8 -home . -export "game_alpha.html -p my_plate cart_1.p8 cart_2.p8" # doesn't work for bin pico8.exe carts\cart_0.p8 -home . -export "game_alpha.bin cart_1.p8 cart_2.p8" # works for bin cd carts pico8.exe cart_0.p8 -export "game_alpha.bin cart_1.p8 cart_2.p8"
- incomplete js generated unless export is run from carts folder
# produces broken js pico8.exe carts\cart_0.p8 -home . -export "game_alpha.html -p my_plate cart_1.p8 cart_2.p8"
Thanks @freds72 -- I've made some changes for 0.2.2 that I think should address this.
Earlier versions suffered from the assumption that you'd always be working with files inside the PICO-8 drive (i.e. ~/AppData/Roaming/pico-8/carts on Windows), and these bugs are all symptoms of that. 0.2.2 allows you to specify paths that are resolved relative to the (host) pwd regardless of where the PICO-8 drive is. So the following will both work:
pico8.exe carts\cart_0.p8 -export "out.html -p my_plate cart_1.p8 cart_2.p8" pico8.exe carts\cart_0.p8 -export "out.html -p foo\my_plate carts\cart_1.p8 carts\cart_2.p8"
When an html template name is specified, the explicit file is tried first (./foo/my_plate.html) and if it doesn't exist, the global plates path is used (~/AppData/Roaming/pico-8/plates/my_plate.html).
Extra note for anyone reading: cartridges are named without any path. For example, bundling carts\cart_1.p8 -- it would be referred to from inside the program as "cart_1.p8", and not "carts\cart_1.p8".
[Please log in to post a comment]