Trying to use pesde managed rojo in a build script won't work when the build folder is placed in the system's temp directory (as this directory doesn't have rojo installed).
Current workarounds are:
- Setting the temp_dir_location to ".", placing it under the current directory.
- Using the library instead of the script, which allows you to manually spawn the rojo process (under the current directory).
Fixing this would probably involve making the build directory no longer temporary (and by default placing it in the current directory, named "build").