a39c93813c
better place to handle dependencies. Make another step at helping cross-compiling: when the user specifies an alternate source tree, the script takes care of creating include files and libraries for the new tree. Furthermore, build and use a version of the "config" program which matches the new sources. It takes a long time to create libraries, and it might even not do the right thing at once, there might be some dependencies that i have forgotten. At any rate, with this code i have been able to build a working picobsd image using -CURRENT sources on -STABLE MFC after: 3 days |
||
---|---|---|
.. | ||
bridge | ||
build | ||
custom | ||
dial | ||
doc/src | ||
floppy.tree/etc | ||
help | ||
install | ||
isp | ||
mfs_tree | ||
net | ||
router | ||
tinyware | ||
README.html | ||
Version |
<html> <body> <h1><b><center> PicoBSD Development Kit </center></b></h1> <p>All documentation, instructions, list of supported hardware and FAQ are in doc/ directory. If they are missing, go to the doc/src/ subdirectory and do a 'make'. The docs are marked with HTML tags, but we try to keep them readable even without a browser. <p>Please start from <A HREF="doc/intro.html">here</a> for general description of the project and its features, or just go directly <A HREF="doc/how2build.html">here</a> for detailed instructions on how to build your version of PicoBSD. <p>Enjoy!</p> <! $FreeBSD$ > </body> </html>