openap-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[openap-cvs] : openap-main/config README,1.4,1.5


From: David Kimdon <address@hidden>
Subject: [openap-cvs] : openap-main/config README,1.4,1.5
Date: Mon, 05 Aug 2002 19:30:43 -0400

Update of /cvsroot/openap/openap-main/config
In directory subversions:/tmp/cvs-serv13783

Modified Files:
        README 
Log Message:
update

Index: README
===================================================================
RCS file: /cvsroot/openap/openap-main/config/README,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- README      30 Jul 2002 18:16:40 -0000      1.4
+++ README      5 Aug 2002 23:30:41 -0000       1.5
@@ -9,21 +9,21 @@
 config.in : system wide confiuration, independant of board, vendor or
     application.
 
-<board>/config.in : Board specific configuration logic.  Some boards require
-certain configuration options in order to function properly.
+<target>/config.in : Board/vendor specific configuration logic.  Some boards
+require certain configuration options in order to function properly.
 
-<board>/defconfig : Default top-level configuration for that board (which 
-applications to install on the root filesystem as well as how those 
applications
-should be configured.)
+<target>/defconfig : Default top-level configuration for that board/vendor
+(which applications to install on the root filesystem, how those applications
+should be configured and the target kernel configuration.)
 
-<board>/defconfig.kernel : Default kernel configuration for that board.
+<target>/<flavor>config : Configuration for a particular application of this
+board.  For example <board>/dkconfig might be the configuration that David
+Kimdon uses on his access point at home, really, it just might be.
 
-<board>/<flavor>config : Configuration for a particular application of this 
board.
-For example <board>/dkconfig might be the configuration that David Kimdon
-uses on his access point at home, really, it just might be.
+<target>/(<flavor>)config.mk : make rules specific to a particular target (or
+flavor).
 
-<board>/<flavor>config.kernel : Same as above, a flavored kernel configuration.
-
-When flavor=native it means we want to build binaries that will run on the
-native platform.  This can be especially useful for testing and debugging.
+flavor=native is a special flavor, it changes more than just the configuration.
+'native' means we want to build binaries that will run on the native platform.
+This can be especially useful for testing and debugging.
 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]