forked from tsoome/grub
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
reintroduce BUILD_LDFLAGS for the cross-compile case
This allows providing separate LDFLAGS for build and host environments, which are not necessary the same for cross-compile case. In particular, it allows building host programs statically to not depend on presence of libraries at run-time (e.g. MinGW DLLs on Windows) while continue to use default dynamic linking at build time. Also fix obsolete comments in confgure.ac - we do use different environment for build and host now.
- Loading branch information
Showing
5 changed files
with
24 additions
and
13 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,10 @@ | ||
2014-01-07 Andrey Borzenkov <[email protected]> | ||
|
||
* configure.ac: Add support for BUILD_LDFLAGS. | ||
* Makefile.am: Use BUILD_LDFLAGS for build time programs here ... | ||
* grub-core/Makefile.am: ... and here. | ||
* INSTALL: Mention BUILD_LDFLAGS. | ||
|
||
2014-01-18 Vladimir Serbinenko <[email protected]> | ||
|
||
* util/grub-mount.c: Extend GCC warning workaround to grub-mount. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -26,11 +26,10 @@ dnl This is necessary because the target type in autoconf does not | |
dnl describe such a system very well. | ||
dnl | ||
dnl The current strategy is to use variables with no prefix (such as | ||
dnl CC, CFLAGS, etc.) for the host type as well as the build type, | ||
dnl because GRUB does not need to use those variables for the build | ||
dnl type, so there is no conflict. Variables with the prefix "TARGET_" | ||
dnl (such as TARGET_CC, TARGET_CFLAGS, etc.) are used for the target | ||
dnl type. | ||
dnl CC, CFLAGS, etc.) for the host type, variables with prefix "BUILD_" | ||
dnl (such as BUILD_CC, BUILD_CFLAGS, etc.) for the build type and variables | ||
dnl with the prefix "TARGET_" (such as TARGET_CC, TARGET_CFLAGS, etc.) are | ||
dnl used for the target type. See INSTALL for full list of variables. | ||
|
||
AC_INIT([GRUB],[2.02~beta2],[[email protected]]) | ||
|
||
|
@@ -477,6 +476,7 @@ AC_SUBST(HOST_CC) | |
AC_SUBST(BUILD_CC) | ||
AC_SUBST(BUILD_CFLAGS) | ||
AC_SUBST(BUILD_CPPFLAGS) | ||
AC_SUBST(BUILD_LDFLAGS) | ||
AC_SUBST(TARGET_CC) | ||
AC_SUBST(TARGET_NM) | ||
AC_SUBST(TARGET_RANLIB) | ||
|
@@ -1290,10 +1290,12 @@ SAVED_CC="$CC" | |
SAVED_CPP="$CPP" | ||
SAVED_CFLAGS="$CFLAGS" | ||
SAVED_CPPFLAGS="$CPPFLAGS" | ||
SAVED_LDFLAGS="$LDFLAGS" | ||
CC="$BUILD_CC" | ||
CPP="$BUILD_CPP" | ||
CFLAGS="$BUILD_CFLAGS" | ||
CPPFLAGS="$BUILD_CPPFLAGS" | ||
LDFLAGS="$BUILD_LDFAGS" | ||
|
||
unset ac_cv_c_bigendian | ||
unset ac_cv_header_ft2build_h | ||
|
@@ -1356,6 +1358,7 @@ CC="$SAVED_CC" | |
CPP="$SAVED_CPP" | ||
CFLAGS="$SAVED_CFLAGS" | ||
CPPFLAGS="$SAVED_CPPFLAGS" | ||
LDFLAGS="$SAVED_LDFLAGS" | ||
|
||
|
||
DJVU_FONT_SOURCE= | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters