[src/trunk]: src/usr.bin/config + suffix rules

[uebayasi <uebayasi%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/a5f5edd4e6b4
branches:  trunk
changeset: 340215:a5f5edd4e6b4
user:      uebayasi <uebayasi%NetBSD.org@localhost>
date:      Fri Aug 28 01:01:57 2015 +0000

description:
+ suffix rules

diffstat:

 usr.bin/config/TODO |  16 ++++++++++++++++
 1 files changed, 16 insertions(+), 0 deletions(-)

diffs (26 lines):

diff -r a1743bb58761 -r a5f5edd4e6b4 usr.bin/config/TODO
--- a/usr.bin/config/TODO       Thu Aug 27 17:18:58 2015 +0000
+++ b/usr.bin/config/TODO       Fri Aug 28 01:01:57 2015 +0000
@@ -405,6 +405,22 @@
   non-DIAGNOSTIC ones.  In that case, debug type informations should match
   theoretically (not confirmed).
 
+o Use suffix rules.
+
+  Build objects following suffix rules.  Source files are defined as relative to
+  $S (e.g. sys/kern/init_main.c) and objects are generated in the corresponding
+  subdirectories under kernel build directories (e.g.
+  .../compile/GENERIC/sys/kern/init_main.o).  Dig subdirectories from within
+  config(1).
+
+  Debugging (-g) and profiling (-pg) objects could be generated with *.go/*.po
+  suffixes as userland libraries do.  Maybe something similar for
+  DIAGNOSTIC/DEBUG.
+
+  genassym(1) definitions will be split into per-source instead of the single
+  assym.h.  Dependencies are corrected and some of misterious dependencies on
+  `Makefile' in sys/conf/Makefile.kern.inc can go away.
+
 o Define genassym(1) symbols per file.
 
   Have each file define symbols that have to be generated by genassym(1) so