path: root/fs/common.mk
Commit message (Collapse)AuthorAgeFilesLines
* System config: split static-dev device table setting into seperate optionGravatar Peter Korsgaard2011-07-251-1/+2
| | | | | | | | | | | | | As discussed here: http://lists.busybox.net/pipermail/buildroot/2011-May/043251.html Add BR2_ROOTFS_STATIC_DEVICE_TABLE for the extra device table file(s) to create device nodes in /dev, rather than complicated logic in BR2_ROOTFS_DEVICE_TABLE, making it complicated to move between static and dynamic modes. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* Allow several device tables and split in two parts our device tableGravatar Thomas Petazzoni2011-05-091-4/+6
| | | | | | | | | | | | | | This allows to have a device table for all directories/files and another device table for the device files themselves. Both are needed for static /dev, but only the first one is needed when devtmpfs/mdev/udev are used. We take this opportunity to move the documentation of the device table format in a common location, package/makedevs/README. [Peter: simplify code slightly, fix indentation] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* fs: add extra deps to ROOTFS_*_DEPENDENCIES variablesGravatar Peter Korsgaard2010-11-191-2/+5
| | | | | | Instead of explicitly adding it both places it is used. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* fs: rename make targets to match package/ conventionGravatar Peter Korsgaard2010-11-191-3/+3
| | | | | | | | | Use rootfs-* rather than *-root, to match the convention used under package/ and which fits with the ROOTFS_*_ variables. This will also help with the host dependencies. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* linux: add support for initramfsGravatar Thomas Petazzoni2010-06-221-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In Buildroot, the kernel is built and installed *before* the root filesystems are built. This allows the root filesystem to correctly contain the kernel modules that have been installed. However, in the initramfs case, the root filesystem is part of the kernel. Therefore, the kernel should be built *after* the root filesystem (which, in the initramfs case simply builds a text file listing all files/directories/devices/symlinks that should be part of the initramfs). However, this isn't possible as the initramfs text file would lack all kernel modules. So, the solution choosen here is to keep the normal order: kernel is built before the root filesystem is generated, and to add a little quirk to retrigger a kernel compilation after the root filesystem generation. To do so, we add a ROOTFS_$(FSTYPE)_POST_TARGETS variable to the fs/common.mk infrastructure. This allows individual filesystems to set a target name that we should depend on *after* generating the root filesystem itself (contrary to normal ROOTFS_$(FSTYPE)_DEPENDENCIES, on which we depend *before* generating the root filesystem). The initramfs code in fs/initramfs/initramfs.mk uses this to add a dependency on 'linux26-rebuild-with-initramfs'. In linux/linux.mk, we do various things : * If BR2_TARGET_ROOTFS_INITRAMFS is enabled (i.e if initramfs is enabled as a root filesystem type), then we create an empty rootfs.initramfs file (remember that at this point, the root filesystem hasn't been generated) and we adjust the kernel configuration to include an initramfs. Of course, in the initial kernel build, this initramfs will be empty. * In the linux26-rebuild-with-initramfs target, we retrigger a compilation of the kernel image, after removing the initramfs in the kernel sources to make sure it gets properly rebuilt (we've experienced cases were modifying the rootfs.initramfs file wouldn't retrigger the generation of the initramfs at the kernel level). This is fairly quirky, but initramfs really is a special case, so in one way or another, we need a little quirk to solve its specialness. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* Add a <fs>-root-show-depends targetGravatar Thomas Petazzoni2010-05-211-0/+3
| | | | Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* makedevs: convert to a more normal way of building packagesGravatar Thomas Petazzoni2010-04-191-1/+1
| | | | Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* fs: change the way the device table is configuredGravatar Thomas Petazzoni2010-04-171-2/+3
| | | | | | | | | | | | | | | | Until now, the location of the device table was specified by a variable in board Makefiles. Unfortunately, this variable is not accessible from fs/common.mk, since the target/ code is included *after* fs/common.mk. Anyway, the general idea is to move away from these boards Makefile, and provide configuration option for things like the device table location. Therefore, this patch adds a BR2_ROOTFS_DEVICE_TABLE option which allows to specify which device table should be used. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* Move all filesystem generation code to fs/Gravatar Thomas Petazzoni2010-04-091-0/+70
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>