[M3commit] CVS Update: cm3

[Jay Krell]

CVSROOT:	/usr/cvs
Changes by:	jkrell at birch.	08/01/20 15:54:26

Modified files:
	cm3/m3-libs/m3core/src/: m3makefile 
	cm3/m3-libs/m3core/src/win32/: m3makefile 
	cm3/m3-sys/cminstall/src/config/: cm3.cfg 
	cm3/scripts/python/: pylib.py upgrade.py 

Log message:
	cm3.cfg:
	use sysinfo.sh to probe the (native) target
	needs to be fleshed out mechanically, currently just PPC_DARWIN
	
	m3core
	expose just enough of win32, types only, so that mklib can build
	on any platform; this might enable some cross build scenarios
	
	note this highlights that "package sets" need something
	analogous to "filtering". That is, previously, mklib was filtered
	to only build for win32. However, it can build for anything.
	It should be in min/core/base/front/upgrade for win32, and in std/all for
	the rest. Might just need to create ad-hoc groups like
	win32core, win32std, posixcore, posixstd that get added to
	std conditionally (contrary to me not liking ad-hoc target names?)
	
	scripts/python:
	let mklib, import-libs, m3objfile, libdump build for all
	import-libs does its own filtering
	laggard fix_nl has a build problem so leave it filtered
	
	copy sysinfo.sh to /cm3/bin along with cm3.cfg, so it can
	use it to probe target
	
	fold one line single use function into caller