| Age | Commit message (Collapse) | Author |
|---|
|
As suggested on the list by Thiago - Makes more sense to have this together
with the stuff using it.
|
|
Thanks to HcE for noticing.
|
|
The buildroot toolchain is installed in $(STAGING_DIR)/usr/bin and not
in $(STAGING_DIR)/bin so let,s adjust the --prefix accordingly.
Also the BFLT binary format is always stripped by definition, so it is
incompatible with any kind of stripping option.
Signed-off-by: Nicolas Pitre <nico@cam.org>
|
|
all the different COPYTOs spread out all over
Buildroot.
Generate COPY_FILE subroutine which can be used
to copy a file.
$(COPY_FILE , file, directory, filename)
This will copy to binary dir and to the selected
copy dir if set in new config (intended to replace
all old COPYTO configs)
This is overridden by BUILDROOT_COPYTO,
if set into the environment.
|
|
Signed-off-by: Markus Heidelberg <markus.heidelberg@web.de>
|
|
|
|
|
|
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>
|
|
Some packages' install-strip target install quite big documentation,
so create an option to remove it similar to the existing man/info options.
|
|
It's confusing to have different behaviour of target independent options.
As reported by HcE on IRC.
|
|
for i in `find -name 'Config*' -o -name 'Makefile*' -o -name '*.mk'`;
do
sed -i 's/ \+$//' $i;
done
|
|
'default n' is the default, so there's no need to say it explicitly.
|
|
|
|
|
|
The new kconfig is more strict regarding depends/depends on, so fixup
the tree.
|
|
ports mirrors (like: ftp2.uk.freebsd.org/pub/FreeBSD/ports/distfiles) are a good place to find almost all of the source packages.
|
|
|
|
compilation problems for people
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Not yet functional. Help welcome
|
|
Adjust some accordingly
|
|
gcc target abi back to a place where the other arch-specific settings live
|
|
Put first according to principle of configuration order
Merge root skeleton configuration to one place
- currently in package/busybox/Config.in
- Should maybe have it's own Config.in
gcc ABI configuration moved from toplevel to toolchain/gcc/Config.in
|
|
|
|
|
|
of config steps
|
|
|
|
This is ment to ease configuration by providing toolchain related options in one place
No functional changes, just shuffling the menus around..
|
|
|
|
Will need to change the GCC_TARGET_TUNE accordingly.
|
|
|
|
- add sparc{,64} CPU variants
|
|
|
|
|
|
respective documentation on your target filesystem.
|
|
|
|
|
|
|
|
quite work yet for me, but this clearly is a huge project and not having it
quite work on the first pass is hardly unexpected. We definately want this
stuff in buildroot.
|
|
|
|
debugging purposes)
|
|
|
|
|
