Date: Sat, 10 Jan 2015 10:59:37 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 192946] put tailored copies of <bsd.prog.mk>, <bsd.lib.mk>, etc in Mk/ Message-ID: <bug-192946-13-NMpTTntgJT@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-192946-13@https.bugs.freebsd.org/bugzilla/> References: <bug-192946-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192946 --- Comment #3 from John Marino <marino@FreeBSD.org> --- i took a closer look -- this is not going to be easy at all. There are many includes, each which pull in other includes -- definitely overkill. I'm guessing most of the users of <bsd.prog.mk> and <bsd.lib.mk> are just taking shortcuts and a highly cut-down version would fit the needs of 95% but no matter how you slice it, this is a big job. <prog> pulls in: .include <bsd.init.mk> .include <bsd.compiler.mk> .include <bsd.libnames.mk> .include <bsd.nls.mk> .include <bsd.files.mk> .include <bsd.incs.mk> .include <bsd.links.mk> .include <bsd.man.mk> .include <bsd.dep.mk> .include <bsd.obj.mk> .include <bsd.sys.mk> <lib> pulls in: .include <bsd.init.mk> .include <bsd.libnames.mk> .include <bsd.symver.mk> .include <bsd.nls.mk> .include <bsd.files.mk> .include <bsd.incs.mk> .include <bsd.links.mk> .include <bsd.man.mk> .include <bsd.dep.mk> .include <bsd.obj.mk> .include <bsd.sys.mk> -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-192946-13-NMpTTntgJT>