search

PurpleKingdomGames / indigo

An FP game engine for Scala.
https://indigoengine.io/
MIT License
633 stars 58 forks source link

Expose build folders paths to SBT users #339

Open bilki opened 2 years ago

bilki commented 2 years ago

It would be nice to expose build folders paths, as some use cases require knowing them, such as publishing to GH pages or serving the game for browsers in other ways.

My first idea was to define a new Setting, that could be used both in the current Indigo build tasks as well as in users SBT project settings.

davesmith00000 commented 2 years ago

If we're doing that for sbt, we should try and do something similar for Mill so that they both remain first class citizens. It's all Mill and os-lib under the covers anyway for both plugins.

davesmith00000 commented 2 years ago

Possibly I've misunderstood.

When I first read this I thought you wanted to have the build function return the directory it created, which you could then daisy chain into some other sbt process to move everything where you wanted it. But now I think maybe you want to be able to specify it yourself? Like an output directory? Was either of those right or did you envisage something else?

Also is the output dir enough, or do you want the out, assets, and scripts folders and so on?