Dan Mick wrote:
Dan Mick wrote:
Richard Lowe wrote:
Darren J Moffat wrote:
Peter Memishian wrote:
> well, I can't run ws, and I need to set some env vars that ws
normally
> would set (or xref would if it could run workspace and get a
workspace
> name). Maybe SRC is enough. And maybe MACH. And, um...
So there isn't something in the hg universe that sets up the
environment
such that the stuff in Makefile.master (and other ON Makefiles) works?
How does one build stuff today?
I just use bldenv for that, it works fine.
Indeed, bldenv and nightly. (they're also the only functional
methods outside of SWAN, unless you have your compilers and such in
sun-ish locations).
Yeah. At some point we should hack up xref to deal with the env stuff
the way it does for Codemanager (i.e. magically), without an env file.
What's the right way to tell if it's an hg hierarchy? "hg root"?
(looks like it works.)
something like this (golly, it was tough):
--- /opt/onbld/bin/xref Mon Nov 20 23:45:50 2006
+++ myxref Wed Nov 22 22:32:08 2006
@@ -103,6 +103,10 @@
CODEMGR_WS=`workspace name` export CODEMGR_WS
SRC=$CODEMGR_WS/usr/src export SRC
MACH=`uname -p` export MACH
+ elif whence hg >/dev/null; then
+ CODEMGR_WS=`hg root` export CODEMGR_WS
+ SRC=$CODEMGR_WS/usr/src export SRC
+ MACH=`uname -p` export MACH
else
fail "No active workspace; run \"ws <workspace_name>\""
fi
I'd been thinking, for things such as this that don't really care about
SCM as much as finding CODEMGR_WS, that a tool that would do the
equivalent of 'workspace name' across all 3 SCMs maybe the easier way
to go (as compared to duplicating this, plus svn, across however many
tools).
-- Rich
_______________________________________________
tools-discuss mailing list
[email protected]
