when ./project is run in a non-interactive environment it fails when asking a question instead of printing a reason
Using the recipe in #13 (closed)
The rest of the output was
===============
Build directory
===============
The project's "source" (this directory) and "build" directories are treated
separately. This greatly helps in managing the many intermediate files that
are created during the build. The intermediate build files don't need to be
archived or backed up: you can always re-build them with the contents of
the source directory. The build directory also needs a relatively large
amount of free space (atleast serveral Giga-bytes), while the source
directory (all plain text) will usually be a mega-byte or less.
'.build' (a symbolic link to the build directory) will also be created
during this configuration. It can help encourage you to set the actual
build directory in a very different address from this one (one that can be
deleted and has large volume), while having easy access to it from here.
--- CAUTION ---
Do not choose any directory under the top source directory (this
directory). The build directory cannot be a subdirectory of the source.
---------------
The command '/bin/sh -c ./project configure --software-dir=software-1637cce' returned a non-zero code: 1
When running the command in an interactive terminal we are prompted for information
$ docker run -it e9ed11167921
root@33316af024b0:/maneage-paper# ./project configure --software-dir=software-1637cce
Checking host C compiler...
...C compiler works.
Checking if static C library is available...
...yes
-----------------------------
Project's local configuration
-----------------------------
Local configuration includes things like top-level directories, or
processing steps. It is STRONGLY recommended to read the comments, and set
the best values for your system (where necessary).
===============
Build directory
===============
The project's "source" (this directory) and "build" directories are treated
separately. This greatly helps in managing the many intermediate files that
are created during the build. The intermediate build files don't need to be
archived or backed up: you can always re-build them with the contents of
the source directory. The build directory also needs a relatively large
amount of free space (atleast serveral Giga-bytes), while the source
directory (all plain text) will usually be a mega-byte or less.
'.build' (a symbolic link to the build directory) will also be created
during this configuration. It can help encourage you to set the actual
build directory in a very different address from this one (one that can be
deleted and has large volume), while having easy access to it from here.
--- CAUTION ---
Do not choose any directory under the top source directory (this
directory). The build directory cannot be a subdirectory of the source.
---------------
Please enter the top build directory:
(Note how Please enter the top build directory:
was not there in the non-interactive session)