summaryrefslogtreecommitdiff
path: root/package/Makefile.autotools.in
AgeCommit message (Collapse)Author
2011-03-28Makefile.autotools.in: add libtool v2.4 supportPeter Korsgaard
Packages (like avahi) are now using libtool 2.4, so extend the libtool handling to support those as well. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-01-25autotools: allow host package to use <pkg>_MAKE_ENV and <pkg>_MAKEThomas Petazzoni
This will be needed by the Python interpreter package. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-12-13package: pass TARGET_MAKE_ENV at install/clean/uninstall stepsThomas Petazzoni
TARGET_MAKE_ENV contains the PATH to the host tools built in $(HOST_DIR), and not having this directory in the PATH while installing packages may cause troubles. The specific example that trigerred the problem is the following one. libglib2 ./configure tries to find a awk version, either gawk or mawk. On my limited testing system, only mawk is available, so normally, libglib2 detects mawk and uses it, and it works perfectly. However, when host-gawk has been compiled before libglib2 (which happens for example if you have used the Crosstool-NG backend), gawk is well detected in $(HOST_DIR)/usr/bin at ./configure time ($(HOST_DIR)/usr/bin is in the PATH at ./configure time, thanks to TARGET_MAKE_ENV). But at install time, when libglib2 uses gawk, it doesn't find it anymore because it is not in the PATH. This also makes things coherent with host installation, in which $(HOST_MAKE_ENV) was already used. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-11-05Remove support for shared configuration cacheThomas Petazzoni
The configuration cache shared between packages, while being in principle a nice idea to speed-up the configuration of packages by avoiding repetitive identical checks, turned out to be unreliable due to the subtle differences between similar but not identical checks in different packages. After spending some time trying to fix those, we concluded that supporting the shared configuration cache is definitely too hard and too unreliable, and that we'd better get rid of it altogether. This patch therefore removes the shared configuration cache infrastructure and usage. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-11-05package: move autoreconfigure step to pre configure hookLionel Landwerlin
[Peter: update documentation to match] Signed-off-by: Lionel Landwerlin <llandwerlin@gmail.com> Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-11-05autotools: fix MESSAGE callsLionel Landwerlin
Signed-off-by: Lionel Landwerlin <llandwerlin@gmail.com> Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-10-14Added the ability to patch ltmain.sh based on versionMartin Banky
There are two versions of ltmain.sh in use in the buildroot system, 1.5.x and 2.2.x. buildroot-libtool.patch would only patch 1.5.x, which meant that for 2.2.x, a separate patch for the affected package had to be maintained. Modified Makefile.autotools.in to check the version of ltmain.sh and apply the correct patch. Signed-off-by: Martin Banky <Martin.Banky@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-09-27autotargets: don't use install-stripThomas Petazzoni
Many packages using the AUTOTARGETS infrastructure do not support the install-strip target. Moreover, we are already stripping all binary files in the $(TARGET_DIR) anyway, so using install-strip is a bit useless. So, we use "make install" in all cases, and let Buildroot do the stripping of the binaries if BR2_ENABLE_DEBUG is not set. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-07-07Merge TARGET_CONFIGURE_ENV into TARGET_CONFIGURE_OPTSThomas Petazzoni
TARGET_CONFIGURE_ENV defines CFLAGS, LDFLAGS, CXXFLAGS and FCFLAGS, separatly from all other variables that are part of TARGET_CONFIGURE_OPTS. This is useless and not consistent with the HOST_CONFIGURE_ variables, therefore we merge TARGET_CONFIGURE_ENV into TARGET_CONFIGURE_OPTS and fix the few users of TARGET_CONFIGURE_ENV. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-07-07Introduce support for host config cacheThomas Petazzoni
We now have for quite some time a configuration cache used to speed-up the execution of ./configure scripts when compiling programs for the target. This commit introduces a similar concept when Buildroot compiles programs for the host. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-05-03Fix autotools configuration cache handlingThomas Petazzoni
It got broken by the introduction of the new autotools infrastructure based on the generic infrastructure. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-05-02autotools: fix referencing to LIBTOOL_PATCH variableThomas Petazzoni
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-05-02autotools: inherit LIBTOOL_PATCH for host packagesThomas Petazzoni
When FOO_LIBTOOL_PATCH is defined, assume that the same value should be used for HOST_FOO_LIBTOOL_PATCH. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-05-02autotools: fix autoreconf checkThomas Petazzoni
The autoreconf check was incorrect, missing a $ sign to properly reference a package-specific variable. There was no visible effect until now since : * The existing syntax allowed to access the value defined in the package specific .mk file, so when AUTORECONF was set to YES by a package, it was working. * The default value in Makefile.autotools.in was NO. In fact, when a package .mkf file wasn't defining the AUTORECONF variable, the Makefile.autotools.in test was testing the empty string against 'YES', which was false, leading to the AUTORECONF not being done, which was the desired effect. However, in a later patch, we intend to change this default value. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-05-02package: Force copy of .la files at the post install hook (readonly files ↵Lionel Landwerlin
might be problematic) Signed-off-by: Lionel Landwerlin <llandwerlin@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-05-02package: add PKG_CONF_ENV variables to host packagesLionel Landwerlin
Signed-off-by: Lionel Landwerlin <llandwerlin@gmail.com> Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-04-11Update config.{guess,sub} unconditionallyThomas Petazzoni
Remove the BR2_UPDATE_CONFIG option which allowed to globally enable/disable the replacement of config.{guess,sub} for autotools-based packages. Doing it unconditionnally just works. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-03-30Fix autotools instalation with symbolsPaulius Zaleckas
Closes #1447 When installing without symbols install-strip is used, with symbols - install-exec. Since install-exec installs only executables, we should use simple install, to install other needed files also (like files in /usr/shared) as install-strip does. Signed-off-by: Paulius Zaleckas <paulius.zaleckas@gmail.com> Acked-by: Lionel Landwerlin <llandwerlin@gmail.com> Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-01-18Makefile.autotools.in: fixup .la files in all lib dirsPeter Korsgaard
Sometimes usr/lib32 or usr/lib64 is used instead of usr/lib, so search those for .la files as well. Fixes .la fixup for beecrypt on x86-64. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2009-12-30Makefile.autotools.in: fix libtool patchingPeter Korsgaard
Fixes two issues with libtool patching: - It seems like the default value for <package>_LIBTOOL_PATCH only gets set AFTER the ifdef check, so the conditional was never taken. Fix it by instead checking that it isn't explicitly set to not do the patching instead. - The $i in the libtool patching for loop needed an extra level of escaping to work. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2009-12-15Rework autotools infrastructure on top of the generic infrastructureThomas Petazzoni
Now that the previous commit implemented a generic package infrastructure, we make the autotools infrastructure inherit from the generic one so that the code is not duplicated. The new AUTOTARGETS macro works by defining what should be done at the configure, build and install steps of a package and then calls the GENTARGETS macro of the generic package infrastructure. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2009-10-07honour DISABLE_IPV6Bernhard Reutner-Fischer
pass --disable-ipv6 to autoconfig packages if IPv6 support is turned off Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2009-10-05Prevent libtool patching before autoreconf when autoreconf is requiredLionel Landwerlin
Signed-off-by: Lionel Landwerlin <lionel.landwerlin@openwide.fr> Tested-By: Sven Neumann <s.neumann@raumfeld.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2009-09-20package/Makefile.autotools.in: Add $(PKG)_AUTORECONF_OPT variable.Will Newton
Allow options to be passed to the autoreconf script if necessary. Signed-off-by: Will Newton <will.newton@gmail.com>
2009-09-16Remove the "project" featureThomas Petazzoni
The "project" feature was designed to allow to several projects to be built inside the same Buildroot source tree and allowing the toolchain and non-configurable packages to be shared between the different projects on the same architecture. While being interesting in theory, this feature adds a level of complexity to Buildroot, both from an user perspective and from a developer perspective, while one of the main Buildroot strengh is to be simple. Moreover, this feature is only seldomly used by our users. From a user-level perspective, this for example allows to remove the project_build_ARCH directory, which was very confusing. The autotools-stamps directory is also removed, since these stamps are back at their normal location. Description of the changes involved : * project/, directory removed * Makefile - Don't include project/Makefile.in and project/project.mk anymore - Grab a copy of the contents of project/Makefile.in at the location it was imported, but remove the definition related to PROJECT_BUILD_DIR. The TARGET_DIR is now in $(BUILD_DIR)/target_dir - Remove the creation/removal of the $(PROJECT_BUILD_DIR) and $(PROJECT_BUILD_DIR)/autotools-stamps directories - Don't make world depends on target-host-info. This target was defined by project/project.mk to customize /etc/issue, /etc/hostname and create /etc/br-version depending on the project definitions. We can of course imagine re-adding such a feature later. - Replace PROJECT_BUILD_DIR by BUILD_DIR everywhere - Remove the update, log and lognr.$(PROJECT) target, they were specific to the project feature. * package/Makefile.autotools.in - Replace PROJECT_BUILD_DIR by BUILD_DIR for the location of the configure cache - Move the INSTALL_TARGET and HOOK_POST_INSTALL stamps to the same directory as the other stamps (i.e, in the package directory). * package/Makefile.in - Replace PROJECT_BUILD_DIR by BUILD_DIR for the location of the configure cache * package/at/at.mk, package/busybox/busybox.mk, package/busybox/initramfs.mk, package/customize/customize.mk, package/linux-fusion/linux-fusion.mk, package/ltp-testsuite/ltp-testsuite.mk, package/nfs-utils/nfs-utils.mk, target/cpio/cpioroot.mk, target/cramfs/cramfs.mk, target/device/Atmel/DataFlashBoot/DataflashBoot.mk, target/device/Atmel/Makefile.in, target/device/Atmel/at91bootstrap/at91bootstrap.mk, target/device/KwikByte/Makefile.in, target/ext2/ext2root.mk, target/initramfs/initramfs.mk, target/iso9660/iso9660.mk, target/jffs2/jffs2root.mk, target/linux/Makefile.in, target/romfs/romfs.mk, target/squashfs/squashfsroot.mk, target/tar/tarroot.mk, target/ubifs/ubifsroot.mk - Replace PROJECT_BUILD_DIR by BUILD_DIR * target/device/Config.in - Do not include project/Config.in anymore * target/linux/Makefile.in.advanced - Replace PROJECT_BUILD_DIR by BUILD_DIR - Store the stamps file in $(STAMP_DIR) instead of $(PROJECT_BUILD_DIR)/autotools-stamps * target/u-boot/Makefile.in - Replace PROJECT_BUILD_DIR by BUILD_DIR - Remove $(PROJECT) from the U-Boot target binary name - Remove the insertion in the configuration of the project name as the hostname - The u-boot-autoscript target now generates $(U_BOOT_AUTOSCRIPT).img instead of $(U_BOOT_AUTOSCRIPT).$(PROJECT) * toolchain/gcc/gcc-uclibc-3.x.mk toolchain/gcc/gcc-uclibc-4.x.mk - Move the stamps files to $(STAMP_DIR) Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2009-09-05packages: use qstripThomas Petazzoni
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2009-05-03Makefile.autotools.in: fix minimal foo.mk exampleMarkus Heidelberg
The directory argument was introduced to support packages in subdirectories of package/ several months ago. Signed-off-by: Markus Heidelberg <markus.heidelberg@web.de> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2009-03-17Makefile.autotools.in: use TARGET_PATH for compile stepPeter Korsgaard
This ensures that the correct build tools are found rather than the host versions (glib-genmarshal, ..)
2009-01-28Makefile.autotools.in: add FOO_MAKE for packages needing to use $(MAKE1)Peter Korsgaard
As requested on irc.
2009-01-18Finish the gtk-doc stuff and start on the smae thing with LARGEFILE and NLS.Thomas Lundquist
2009-01-17Easier with one place for configure options for disabling gtk-docThomas Lundquist
2009-01-16DOWNLOAD: don't use := assignment for function implementationPeter Korsgaard
:= causes the function parameters to get evaluated at definition time instead of implementation time, which is kind of silly for a function. Fixes make source-check / external-deps
2009-01-16buildroot: add BR2_BACKUP_SITE and DOWNLOAD helperPeter Korsgaard
This is the long requested backup mirror support. So far only enabled for Makefile.autotools.in, but there's no reason why we cannot use DOWNLOAD everywhere. Notice, I'm still syncing http://buildroot.uclibc.org/downloads/sources/
2009-01-01buildroot: set SHELL instead of messing around with CONFIG_SHELLPeter Korsgaard
Simply set SHELL to bash instead of adding CONFIG_SHELL to all shell invocations. CONFIG_SHELL is still set, as it is used by kconfig.
2008-12-08package/: get rid of unneeded $(strip ..)Peter Korsgaard
2008-11-28Adding Central config.cache optionsDaniel Laird
The following changes allow for use of a central configure cache file. This speeds up configuration of packages. Its use is configurable at the top level (BR2_CONFIG_CACHE - default n). Old style makefiles can use it if they use the following MACRO in makefiles: $(AUTO_CONFIGURE_TARGET) see my change to directfb.mk. New style Autotools.in will use it if you set the global option. However you can enable the global option and on a per package overrule it by doing the following: $(PKGNAME)_USE_CONFIG_CACHE = NO see fontconfig.mk for an example of this. Finally I have removed a few config variable settings which indicated no CXX compiler as this is wrong and breaks the build when using this central cache. Config.in | 8 ++++++++ package/Makefile.autotools.in | 5 ++++- package/Makefile.in | 28 +++++++++++++++++++++++++++- package/atk/atk.mk | 2 +- package/directfb/directfb.mk | 7 +------ package/fontconfig/fontconfig.mk | 3 +++ package/libglib2/libglib2.mk | 2 +- package/libgtk2/libgtk2.mk | 1 - 8 files changed, 45 insertions(+), 11 deletions(-) I would appreciate feedback on this change (I have been testing for 2-3 weeks) But I can never test all cases! If you enable the BR2_CONFIG_CACHE option some Makefile.autotools.in based packages may now break - I cannot build them all. In this case you may need to remove config options that are being hardcoded all over the place (like gtk saying we have 2 CXX compiler) or disable the use of CONFIG CACHE file like I have done in fontconfig. I can build all packages required to get WebKit on DirectFB up and running and it runs fine. I will try to resolve any issues this creates as fast as I can. Signed-off-by: Daniel Laird <daniel.j.laird@nxp.com>
2008-11-07Makefile.autotools.in: make MESSAGE output stand outPeter Korsgaard
The following patch makes the MESSAGE Macro in Makefile.autotools.in work. I think it was originally intended to print the messages in bold type but it doesn't appear to work correctly. This patch should work on all platforms. Signed-off-by: H Hartley Sweeten <hsweeten@visionengravers.com> (Fixed to not continously call tput)
2008-11-05Move creation of $(PROJECT_BUILD_DIR)/autotools-stamps into top level MakefileHans-Christian Egtvedt
This patch will create the autotools-stamps directory early in the build process, thus making it possible for non Makefile.autotools.in packages to use this directory to hold stamp files. Signed-off-by: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
2008-10-21buildroot: add QUIET variable and use it for wget/git/svn/configurePeter Korsgaard
A lot of tools take a -q option to be quiet. Set this if make is called with the -s (silent) option and use for wget, git, svn and configure.
2008-10-20BR2_HAVE_DOCUMENTATION: add option to remove documentation from targetPeter Korsgaard
Some packages' install-strip target install quite big documentation, so create an option to remove it similar to the existing man/info options.
2008-10-20Makefile.autotools.in: default to install-strip for non-debug target installPeter Korsgaard
2008-10-07Makefile.autotools.in: honor CONFIG_SHELL and TAR.Wade Berrier
Don't use recursively expanded definition (Use ':=' instead of '=')
2008-10-06Makefile.autotools.in:Wade Berrier
-Make tar switches 1.14 compatible (Not sure of a more elegant way to handle this ... ?)
2008-09-19Makefile.autotools.in: Get my $(Q)'s in the correct placeDaniel Laird
Minor fix for Makefile.autotools.in that deals with the packages that use AUTOCONF to regenerate configure etc. (my mistake to start with) Daniel Laird
2008-09-19Makefile.autotools.in: Extended to cope with more bad packagesDaniel Laird
1. I added a HOOK_POST_EXTRACT previously so that I could cope with the bad libxml2 package. This required me to remove some dead patches (.rej) files after I extracted the package, the issue is that the EXTRACT target runs patch-kernel.sh to patch the ltmain.sh. It then finds some.rej files and bombs out. I have altered the sequence so that the HOOK_POST_EXTRACT target runs before the make target that patches libtool to deal with this. 2.) I have added a $(PKG)_LIBTOOL_PATCH variable. This is defaulted to YES however if you override it in the package makefile to NO then the ltmain.sh file will not be patched automatically but only if you have added your own patches. This is necessary for freetype 2.3.7 as it cannot use the buildroot-libtool patch. I am using this patch for building a set of packages, however it is not a complete set of packages so await feedback of issues (if any) Daniel Laird
2008-09-14Makefile.autotools.in: fix DESTDIR= help textPeter Korsgaard
DESTDIR per default points to TARGET_DIR / STAGING_DIR without /usr appended.
2008-09-14Makefile.autotools.in: fix FOO_UNINSTALL_TARGET_OPT help textPeter Korsgaard
It defaults to TARGET_DIR, not STAGING_DIR.
2008-09-11Move project-specific stamp files into a project-specific directoryHamish Moffatt
$(PROJECT_BUILD_DIR)/autotools-stamps. Without this, autotools-using packages won't be installed into any other projects than the first.
2008-09-04Make the autotools xyz-clean target call xyz-uninstall first, rather than ↵Hamish Moffatt
duplicating its actions
2008-09-04Fix duplicate $(AUTORECONF) run in autoreconf and configure targetsHamish Moffatt
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-17 16:44:21 +0000