| 1 | = Config.site = |
| 2 | |
| 3 | |
| 4 | When cross-compiling, it's sometimes helpful to store the settings in a shell script, such as config.site. |
| 5 | For example: you may want to tell configure that RTEMS has a int32_t available to it, but the configure script can't find the int32_t, then config.site can be used to tell configure there is an int32_t. |
| 6 | |
| 7 | For RTEMS, a place that would make sense for config.site might be: /opt/rtems-4.11/share/config.site |
| 8 | |
| 9 | # /opt/rtems-4.11/share/config.site for configure |
| 10 | # |
| 11 | # Change some defaults. |
| 12 | test "$prefix" = NONE && prefix=/opt/rtems-4.11/ |
| 13 | test "$exec_prefix" = NONE && exec_prefix=/opt/rtems-4.11/ |
| 14 | test "$sharedstatedir" = '${prefix}/com' && sharedstatedir=/var |
| 15 | test "$localstatedir" = '${prefix}/var' && localstatedir=/var |
| 16 | |
| 17 | # Give Autoconf 2.x generated configure scripts a shared default |
| 18 | # cache file for feature test results, architecture-specific. |
| 19 | if test "$cache_file" = /dev/null; then |
| 20 | cache_file="$prefix/var/config.cache" |
| 21 | # A cache file is only valid for one C compiler. |
| 22 | CC=gcc |
| 23 | fi |
| 24 | |
| 25 | To get a configure script to read config.site input on the command line: |
| 26 | $ CONFIG_SITE=/opt/rtems-4.11/share/config.site |
| 27 | = References = |
| 28 | |
| 29 | http://www.gnu.org/software/autoconf/manual/autoconf-2.67/html_node/Site-Defaults.html |