Hey developers,

I decided to restructure the build directories, because the current
structure has a few disadvantages:

- building several targets in one checkout causes problems, because the
root dir and the packages dir are shared
- the toolchain is contained in the staging dir - no way to keep it
elsewhere
- switching targets will not cause gcc to be rebuilt with the correct
version

I'm working on a patch which changes these issues. The new structure
looks like this:

- build_dir/host (previously tool_build and tool_build_dir)
contains the build directories of all target independent tools built for
the host

- build_dir/toolchain-$(ARCH) (previously toolchain_build_$(ARCH))
contains the build directories for the toolchain

- build_dir/$(ARCH) (previously build_dir_$(ARCH))
build directories for the target

- staging_dir/host
installation directory for target independent host tools

- staging_dir/toolchain-$(ARCH)-gcc$(GCC_VERSION)
toolchain directory (I will add later a config option to move this one
elsewhere)

- staging_dir/$(ARCH)
staging directory for headers/libraries of packages


staging_dir/host/bin and
staging_dir/toolchain-$(ARCH)-gcc$(GCC_VERSION)/bin are kept in $PATH,
staging_dir/$(ARCH)/bin is not.

When all of this is done, I want to be able to run dpkg-buildpackage in
toolchain/ and get a .deb package, which can be used to install the
toolchain for the current target globally on the system.

Any comments, suggestions, flames?

- Felix
_______________________________________________
openwrt-devel mailing list
[email protected]
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Reply via email to