On 2015-11-20 at 17:51 Kevin Klues <[email protected]> wrote: > I'd personally rather see an external framework that can be told how > to build libs and apps on a per lib/app basis and install them into > the akaros kfs via make magic. Something like: > > akaros-pkg-builder/ > ├── pkg/ > ├── sysroot/ > ├── .gitignore > ├── .config > └── Makefile > > Where we use ncurses to select packages we know how to build, and we > have per-package Makefiles in the 'pkg' directory which the top level > Makefile can invoke to build and install a specific package. Packages > would then be installed into the 'sysroot' directory and recursively > copied into $AKAROS_ROOT/kern/kfs once all selected packages were > built. We could also remove them from kfs via the reverse operation.
This is a little broader in scope from what I was asking Davide for (which was the ability to make snc or kprof2perf in a stand-alone manner). But, since we're on the topic, this is basically a package management system. Instead of rolling our own, we should try to use an existing one. There's an excellent one that already exists for Gentoo (a source-based distro) called portage. It's a tree of packages and instructions for building them that doesn't contain the source. It has local patches. You can specify CFLAGS and do cross compilations and all sorts of things. It can build from git repos. I think the right answer is to try and use portage to build packages for akaros. We'd need to modify or write the ebuilds, for which there are numerous instructions online. This also doesn't seem like a high priority, esp considering apps like busybox are closely coupled with the kernel/runtime. Barret -- You received this message because you are subscribed to the Google Groups "Akaros" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
