be87ada6b5
After setting-up a buld environment, running something like
~/src/mes/wip/pre-inst-env mescc -v -v ~/src/mes/wip/scaffold/main.c
works again.
TODO: Make this less complex.
* The mescc-lib (and gcc-lib) build directories do not help;
these were introduced to support `wip-autotools'.
* We used to opt for short *PATH variables: "." rather than
/gnu/store/.... or /home/janneke/src/mes/master to avoid
filling the MES arena. XXX Has this been solved?
* In the Guix bootstrap, we run module/mescc.scm directly
$MES -e '(mescc)' module/mescc.scm
...so that's why these overrides started to appear in multiple
places.
* build-aux/pre-inst-env.in (MES_UNINSTALLED): New variable.
* scripts/mescc.in (includedir,libdir): Use it to override these.
* module/mescc/mescc.scm (arch-find): Use it to add <lib>-messc.
|
||
|---|---|---|
| .. | ||
| armv4 | ||
| i386 | ||
| x86_64 | ||
| as.scm | ||
| bytevectors.scm | ||
| compile.scm | ||
| info.scm | ||
| M1.scm | ||
| mescc.scm | ||
| preprocess.scm | ||