From: Arnout E. <no...@bz...> - 2011-08-07 14:21:36
|
It seems both system-inc.mk and system.mk were originally meant for 'system-specific configuration'. Perhaps we should drop build/system-inc.mk, move system.mk to build/autodetect.mk(?) and include build/libs.mk, build/autodetect.mk and local.mk (if available) directly from the Makefile? This has gotten a bit complex, now seems like a good time to clean up and and simplify :). Regards, Arnout On Sat, May 14, 2011 at 06:26:11PM +0200, Arnout Engelen wrote: > On Fri, May 13, 2011 at 07:24:29AM -0400, Etan Reisner wrote: > > I'm also open to simply having system.mk include (without failing if it > > doesn't exit) a local.mk (or similar) file to allow these sort of > > custom definitions. > > This sounds like an elegant solution to me - any drawbacks we can think of? > > > Arnout > > ------------------------------------------------------------------------------ > Achieve unprecedented app performance and reliability > What every C/C++ and Fortran developer should know. > Learn how Intel has extended the reach of its next-generation tools > to help boost performance applications - inlcuding clusters. > http://p.sf.net/sfu/intel-dev2devmay > _______________________________________________ > Notion-devel mailing list > Not...@li... > https://lists.sourceforge.net/lists/listinfo/notion-devel |