<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
I think WDROOT was only ever a synonym for ROOT -- the root of the source tree, available for overrides to get "builtlocal" unshipped stuff.<BR>
This does somewhat resemble what Olaf was talking about, but it is referencing, essentially, the source tree, in a different layout than the shipped tree. Instead Olaf and I advocate multiple (I think two is maybe enough) roots with the same layout as the shipped/installed system, instead of one shipped and one unshipped. All outputs that would be shipped should just go to this place, rather than first to build_dir and then later copied into the right layout. They might still be copied, but it would not be a layout changing copy.<BR>
(And yes, this mechanism does work.)<BR>
<BR>
Searching for 'wdroot'...<BR>C:\dev2\cm3.2\m3-db\stable\example\src\m3makefile(7):override ("stable", WDROOT) % try to pick up the local copy<BR>C:\dev2\cm3.2\m3-libs\arithmetic\test\src\m3overrides(1):%override("arithmetic",WDROOT)<BR>C:\dev2\cm3.2\m3-libs\lapack\test\src\m3overrides(1):%override("lapack",WDROOT)<BR>C:\dev2\cm3.2\m3-sys\cm3\src\m3makefile.7(350):.BR WDROOT ,<BR>C:\dev2\cm3.2\m3-sys\cm3\src\m3makefile.7(516):.B WDROOT <BR>C:\dev2\cm3.2\m3-sys\cm3\src\m3makefile.7(554):.B WDROOT <BR>C:\dev2\cm3.2\m3-sys\m3loader\src\m3makefile(10): override ("winlib", WDROOT)<BR>C:\dev2\cm3.2\m3-tools\m3tk\src\files\m3overrides.not(1):override(m3tk-misc.3.1, WDROOT)<BR>C:\dev2\cm3.2\m3-ui\juno-2\juno-app\src\m3overrides(9):% override ("vbtkit", WDROOT)<BR>C:\dev2\cm3.2\m3-ui\juno-2\juno-app\src\m3overrides(10):% override ("formsvbt", WDROOT)<BR>C:\dev2\cm3.2\m3-ui\juno-2\juno-app\src\m3overrides(11):%override ("juno-machine", WDROOT)<BR>C:\dev2\cm3.2\m3-ui\juno-2\juno-app\src\m3overrides(12):%override ("juno-compiler", WDROOT)<BR>C:\dev2\cm3.2\m3-ui\juno-2\juno-compiler\src\m3overrides(10):%override("juno-machine", WDROOT)<BR>C:\dev2\cm3.2\m3-ui\juno-2\juno-compiler\tests\compiler\src\m3overrides(9):%override("juno-machine", WDROOT)<BR>C:\dev2\cm3.2\m3-ui\juno-2\juno-compiler\tests\compiler\src\m3overrides(10):%override("juno-compiler", WDROOT)<BR>C:\dev2\cm3.2\m3-ui\juno-2\juno-compiler\tests\lexer\src\m3overrides(9):override(juno-machine, WDROOT)<BR>C:\dev2\cm3.2\m3-ui\juno-2\juno-compiler\tests\lexer\src\m3overrides(10):override(juno-compiler, WDROOT)<BR>C:\dev2\cm3.2\m3-ui\juno-2\juno-compiler\tests\parser\src\m3overrides(9):%override(juno-machine, WDROOT)<BR>C:\dev2\cm3.2\m3-ui\juno-2\juno-compiler\tests\parser\src\m3overrides(10):%override(juno-compiler, WDROOT)<BR>C:\dev2\cm3.2\m3-ui\juno-2\juno-compiler\tests\scope\src\m3overrides(9):%override(juno-machine, WDROOT)<BR>C:\dev2\cm3.2\m3-ui\juno-2\juno-compiler\tests\scope\src\m3overrides(10):%override(juno-compiler, WDROOT)<BR>C:\dev2\cm3.2\m3-ui\juno-2\juno-machine\linear\src\m3overrides(9):%override("juno-machine", WDROOT)<BR>C:\dev2\cm3.2\m3-ui\juno-2\juno-machine\nonlinear\src\m3overrides(9):%override("juno-machine", WDROOT)<BR>C:\dev2\cm3.2\m3-ui\juno-2\juno-machine\runtime\src\m3overrides(9):%override("juno-machine", WDROOT)<BR>C:\dev2\cm3.2\m3-ui\juno-2\juno-machine\solve\src\m3overrides(3):%override("juno-machine", WDROOT)<BR>C:\dev2\cm3.2\m3-www\http\src\m3makefile(7):%write("WDROOT = ", WDROOT, CR)<BR>26 occurrence(s) have been found.<BR><BR>
- Jay<BR><BR> <BR>> Date: Mon, 6 Jul 2009 10:00:19 -0700<BR>> From: eiserlohpp@yahoo.com<BR>> To: m3devel@elegosoft.com<BR>> Subject: [M3devel] WDROOT private repository not working?<BR>> <BR>> <BR>> Hi Guys,<BR>> <BR>> Seeing all the attention placed on creating relative<BR>> linking, and so forth, I decided to examine the behavior<BR>> of CM3, when building for a private root. <BR>> <BR>> So, I set WDROOT to ${HOME}/m3work in my m3makefile.<BR>> <BR>> ---- BEGIN m3makefile ----<BR>> %# Time-Space-Position Information (TSPI) library<BR>> <BR>> HOME = "/home/peter"<BR>> WDROOT = HOME & "/m3work"<BR>> <BR>> include_dir("xform")<BR>> % include_dir("smoothing")<BR>> % include_dir("editing")<BR>> % include_dir("geoid")<BR>> % include_dir("testing")<BR>> ---- EMD m3makefile ----<BR>> <BR>> <BR>> Then I, attempted to build and ship from there.<BR>> <BR>> It said, there was an error <BR>> <BR>> ---- BEGIN ERROR MSG ----<BR>> peter@black:/data/modula-3/peters-stuff/tspi/src $ cm3 -ship<BR>> --- shipping from ../AMD64_LINUX ---<BR>> <BR>> "/data/modula-3/peters-stuff/tspi/AMD64_LINUX/.M3SHIP", line 1: quake runtime error: unable to create directory "/usr/lib/cm3/pkg/tspi": errno=13<BR>> <BR>> --procedure-- -line- -file---<BR>> make_dir -- <builtin><BR>> 1 /data/modula-3/peters-stuff/tspi/AMD64_LINUX/.M3SHIP<BR>> <BR>> ---- END ERROR MSG ----<BR>> <BR>> <BR>> <BR>> Was support for WDROOT removed? Can CM3 support the ability to<BR>> have a private repository, while also having the public repo?<BR>> <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> +--------------------------------------------------------+<BR>> | Peter P. Eiserloh |<BR>> +--------------------------------------------------------+<BR>> <BR>> <BR>> <BR></body>
</html>