curiousdannii-testing / inform7-imported-bugs

0 stars 0 forks source link

[I7-2073] Inblorb should put the generated blorb in the release folder #11

Closed curiousdannii-testing closed 2 years ago

curiousdannii-testing commented 2 years ago

Perhaps this an unsupported usage, but I’m trying to figure out the simplest way to go from “an Inform 7 project” to “a distributable release”.

My current procedure looks something like this:

  1. inform7 -silence -project path/to/Project.inform which creates path/to/Project.inform/Build/auto.inf
  2. inform6 -G path/to/Project.inform/Build/auto.inf path/to/Project.inform/Build/output.ulx
  3. inblorb -project path/to/Project.inform which creates path/to/Project.inform/Build/output.zblorb and prints “Copy blorb to: [[./Release/Untitled.gblorb]]”

There’s a number of things about inblorb that confuse me:

It seems that things would be simpler all around if inblorb would just put all the release files in the release folder with the correct names, including the blorb file. If the interface needs to do some additional handling of the blorb file, perhaps Inblorb could print “Copied blorb to: [[./Release/Untitled.gblorb]]” to let the interface find it.

imported from: Inblorb should put the generated blorb in the release folder
  • status: Closed
  • priority: Low
  • resolution: Won't Do
  • resolved: 2022-05-02T05:35:06+10:00
  • imported: 2022/01/10
curiousdannii-testing commented 2 years ago

5d0666bb19d1e00c48e1242f:

Inblorb is behaving to spec here, I think. There's a manual on how instructions are given to inblorb ("blurb" files), but the IF Forum is a better place to ask for help - this is a bug tracker rather than being for general support questions.