Environment Variable Support For Def Files

[napperley]

With the def file format it doesn't support the use of environment variables. If environment variables were supported then a def file would look like this:

linkerOpts = -L${HOME}/ncurses-6.1/lib -lncurses
compilerOpts = -I${HOME}/ncurses-6.1/include
headers = curses.h
package = ncurses

The main use case for supporting environment variables in a def file is to allow custom built C libraries to be used without having to hard code paths in a def file, which is a big issue when using a VCS (eg Git).

[msink]

Probably duplicate of #3484 and #2314

[artdfel]

Why do you prefer to use .def configuration instead of setting these options by Gradle?

[napperley]

Environment variables would be set by Gradle. In a def file the environment variables would be read only.

[SvyatoslavScherbina]

The main use case for supporting environment variables in a def file is to allow custom built C libraries to be used without having to hard code paths in a def file, which is a big issue when using a VCS (eg Git).

As mentioned above, you can easily pass anything from Gradle. See the documentation for more details.
I'm closing this issue, because we are migrating issue tracking to YouTrack. Feel free to submit it again to https://kotl.in/issue if it still affects you.