Date: Sat, 22 Jun 1996 22:34:35 +0930 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: hackers@freebsd.org Subject: Bmaking 3rd-party components Message-ID: <199606221304.WAA13854@genesis.atrad.adelaide.edu.au>
next in thread | raw e-mail | index | archive | help
Continuing in a series of proposals aimed at dealing with the presence of third-party code in the FreeBSD tree, and as inspired by Garret's comment about not needing to mess with a forecign tree in order to succesfully bmake it. Put the required parts of the foreign tree under src/foreign. Put the bmakefile(s) that refer to the foreign code in directories in appropriate places, and point to the foreign code using .PATH: I just did this for Tcl and it works quite well. (And as a sideeffect I have a bmaked Tcl 7.5 to put my money where my mouth is). In fact, it's highly desirable for something like Tcl which produces several resultant entities. Collecting everything under src/foreign (and perhaps a subcategory src/foreign/gnu) would make doing version sweeps easier, and makes where something is put a simpler choice 8) (eg. tcl, is it a library or a program?) Exact preference (and makefile simplicity) could be helped with a makefile variable FOREIGN_BASE (and maybe FOREIGN_GNU_BASE) which pointed to the root of the foreign code base. Suggestions? Comments? Brickbats? -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606221304.WAA13854>