[DragonFlyBSD - Bug #3415] (New) Kernel objects should keep their directory hierachies

[liweitianux]

Issue #3415 has been reported by liweitianux.

----------------------------------------
Bug #3415: Kernel objects should keep their directory hierachies
http://bugs.dragonflybsd.org/issues/3415

* Author: liweitianux
* Status: New
* Priority: Normal
* Assignee: liweitianux
* Target version: 6.6
* Start date: 2026-06-23
----------------------------------------
As mentioned in commit 4414dac0c0c01d46bf969f21a7f4460c975ae15b, all the kernel objects currently are placed in the same directory (e.g., @/usr/obj/usr/src/sys/X86_64_GENERIC@), which prevents the kernel sources from choosing arbitrary filenames to avoid conflicts.

I think the solution is to keep the directory hierarchies for the kernel objects, e.g.,

<pre>
sys/kern/init_main.c  =>  ${SYSOBJ}/${KERNCONF}/kernel/sys/kern/init_main.o
sys/net/if_loop.c     =>  ${SYSOBJ}/${KERNCONF}/kernel/sys/net/if_loop.o
</pre>

The paths of kernel module objects already have the directory hierarchies, so no change needed.
However, note their paths to avoid conflicts; e.g., @/usr/obj/usr/src/sys/X86_64_GENERIC/usr/src/sys/net/wg/if_wg.o at .

Questions:
* What is the best layout?
* How to best determine the source releative path (e.g., @sys/net/if_loop.o@), as required by the above layout?
* How to correctly handle the generated headers, e.g., @opt_*.h@, @use_*.h@, @usb_if.h@?

Any other things to watch out?



-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account