[M3devel] INSTALL_ROOT and PKG_USE in cm3.cfg

Fri Jan 25 03:48:28 CET 2008

Jay:

I've already edited my version of cm3.cfg to make it work for me.

I don't know what the path() function does.

The path() function is only used in the following code:

if not defined("INSTALL_ROOT")
    if not equal ($INSTALLROOT, "")
        INSTALL_ROOT = $INSTALLROOT
    else
        INSTALL_ROOT = (path() & "\\..")
    end
end
Since this code is not executed when I define INSTALL_ROOT as
"c:\\cm3", there is no need to remove it for my use.

I've already confirmed that the other variables I need get set
correctly inside CM3-IDE/Reactor once the INSTALL_ROOT is set properly. 
Note that a bunch of variables inside cm3.cfg depend on INSTALL_ROOT.

I'm still want to find a solution for the general user population.

Regards,
Randy

>>> Jay <jayk123 at hotmail.com> 1/24/2008 9:23 PM >>>
Randy, don't worry, whatever you do, I'll be able to recover from.

Just try editing your \cm3\bin\cm3.cfg file to say INSTALLROOT="c:\cm3"
or whatever.
Remove the path() function as a variable.
See what happens. Maybe it's the problem, maybe not. It is something
that I changed, and is worth trying the old way.

Use write() and error() to print the other variables.

Can you make the stuff you are working on available? To just some
people?

 - Jay

Date: Thu, 24 Jan 2008 21:07:29 -0500
From: rcoleburn at scires.com 
To: jay123 at hotmail.com; jayk123 at hotmail.com 
CC: m3devel at elegosoft.com 
Subject: Re: [M3devel] INSTALL_ROOT and PKG_USE in cm3.cfg

Jay:

Not sure exactly what you mean by:
>I'm not sure what versions of cm3 have path(). I did think I saw it
missing the other day.
I assume you are not referring to the path env variable.  Is this some
built-in quake function or a function you have written in quake?
The version of cm3.cfg that I am using is the one that *you* put in the
minimal binary installation for windows.

Reactor does indeed "run" the cm3.cfg in that it uses quake to load and
interpret this file.

What is the significance of doing the copy you suggest below?
>In terms of my workflow, you can go ahead and copy NT386 to the
config-no-install directory. I'll survive.
I'm not trying to be obtuse here.  It's just that you have been working
on the windows distribution and all these scripts etc for a while now. 
I don't want to mess up anything you are doing and I know I don't have a
deep understanding of all this, so I am reluctant to change anything
like cm3.cfg for my needs.

My goal is to make the CM3-IDE (old Reactor) available to everyone.  As
I said before, it does "run" the cm3.cfg and it needs to use this
somehow to come up with a valid "PKG_USE" which should point to the
"pkg" folder inside the cm3 installation root.

Regards,
Randy

>>> Jay <jayk123 at hotmail.com> 1/24/2008 8:33 PM >>>
I'm not sure what versions of cm3 have path(). I did think I saw it
missing the other day.
That could be your problem.
m3cgcat also doesn't like my config file, it wants to open it to find
TARGET, not sure it uses it at all, but it wants it. When I run mcgcat,
I first put back a TARGET line in my cm3.cfg. And then remove it.
This is very related.
I would suspect that whoever reads the files MIGHT find it acceptable
to RUN them.
Running them doesn't mean compiling or linking or anything, those are
functions that the "host" would chose to call or not. But toplevel can
have arbitrary code so maybe this is not great.

Reactor is a persistant web server though, right? It should be ok
"running" the file, esp. since it doesn't start often.

The "normal" alternative that other folks use is to run cminstall,
which I find all but useless.

In terms of my workflow, you can go ahead and copy NT386 to the
config-no-install directory. I'll survive.

Randy you should try debugging stuff. Quake is readily debuggabe
through printing.

if defined("path")
  write("path is defined")
  write("path is " & path())
else
  write("path is not defined")
end
error("")

I put in error so I stop after my printing and don't go and build stuff
when my intent was just to run a snippet of Quake.

 - Jay

Date: Thu, 24 Jan 2008 20:06:09 -0500
From: rcoleburn at scires.com 
To: jay123 at hotmail.com; jayk123 at hotmail.com 
CC: m3devel at elegosoft.com 
Subject: RE: [M3devel] INSTALL_ROOT and PKG_USE in cm3.cfg

Jay:

That's the reason I asked before making a change.  I don't want to
break or mess up what you are doing.

I can get around the problem easily for me.  I just remove the comment
from the 
%INSTALL_ROOT="c:\\cm3" 
and "everything" is ok.

I'm hoping we can come up with a way that works for everyone.  Once the
CM3_IDE (formerly known as Reactor) package is in the repository and
part of the standard distribution, it would be best if folks don't have
to go around editing cm3.cfg to make it work properly.

Now, you are saying your way is more automatic and portable.  I like
these words.  Is there a way we can set something in cm3.cfg that I can
key off of for CM3_IDE/Reactor?  I don't mind changing the code to
accommodate.

The big thing for CM3_IDE/Reactor, is that it needs to know where to
look for the cm3 installation because it has to find all of the subdirs,
like doc, examples, etc.

BTW, I still don't see why all this "works" since I am getting "\.." as
my INSTALL_ROOT.

Regards,
Randy

>>> Jay <jayk123 at hotmail.com> 1/24/2008 7:24 PM >>>
Blech. My way is more automatic and "portable" in the sense that you
can move installations around and they keep working. As well, with my
way, you just extract an archive and go, no setup/cminstall, no editing
of the cm3.cfg file, just set %PATH% and run vcvars, and vcvars I think
I can remove the need for.

path() is a builtin Quake function that returns the directory of the
currently being run Quake code.

But yet Reactor.
To unblock yourself, remove my code, add back the commented out, fix
the path to match your particular install, don't submit the file.

Perhaps move the current checked in file over to the config-no-install
directory and then put config's file back in the old style, that
requires running cminstall. My workflow will keep working, since it
probes for config-no-install first.

 - Jay

Date: Thu, 24 Jan 2008 18:53:48 -0500
From: rcoleburn at scires.com 
To: jay123 at hotmail.com 
CC: m3devel at elegosoft.com 
Subject: [M3devel] INSTALL_ROOT and PKG_USE in cm3.cfg

Jay:

The cm3.cfg that comes with your minimal binary installation on Windows
(NT386) has the following lines:

-----------------------------------------
% INSTALL_ROOT = BEGIN_CONFIG
%   "Where should CM3 be installed?"
%     7 %-- user specified install root
% END_CONFIG

% INSTALL_ROOT = "c:\\cm3"

if not defined("INSTALL_ROOT")
    if not equal ($INSTALLROOT, "")
        INSTALL_ROOT = $INSTALLROOT
    else
        INSTALL_ROOT = (path() & "\\..")
    end
end

BIN_INSTALL   = INSTALL_ROOT & "\\bin"          % executables
LIB_INSTALL   = INSTALL_ROOT & "\\lib"          % libraries
PKG_INSTALL   = INSTALL_ROOT & "\\pkg"          % packages
DOC_INSTALL   = INSTALL_ROOT & "\\doc"          % documents
EMACS_INSTALL = INSTALL_ROOT & "\\elisp"        % emacs lisp code
MAN_INSTALL   = INSTALL_ROOT & "\\man"          % man pages
HTML_INSTALL  = INSTALL_ROOT & "\\www"          % public hypertext

%
% On some systems (e.g. AFS) you must install public files in a
different
% place from where you use them.  If that is the case for your system,
% specify the "use" location here, otherwise leave them alone.
%
%USE_ROOT  = INSTALL_ROOT
BIN_USE   = BIN_INSTALL   % executables
LIB_USE   = LIB_INSTALL   % libraries
PKG_USE   = PKG_INSTALL   % packages
-----------------------------------------

Notice that the lines for INSTALL_ROOT and USE_ROOT are commented out.

The Reactor program is coded to grab several variables out of cm3.cfg. 
For example,

    build_dir       := M3Config.Get ("BUILD_DIR");
    system_root     := M3Config.Get ("PKG_USE");
    doc_root        := M3Config.Get ("DOC_INSTALL");
    initial_browser := M3Config.Get ("INITIAL_CM3_IDE_BROWSER");
    initial_editor  := M3Config.Get ("INITIAL_CM3_IDE_EDITOR");
What is happening on my installation is that PKG_USE winds up being
"\..\PKG".  This is not a valid path and it is causing all sorts of
trouble for Reactor.

The reason it is getting set this way is that the ELSE branch of the,
if not defined("INSTALL_ROOT"), is getting executed resulting in
INSTALL_ROOT=\..

I'm not sure why this is coded this way.

How do you suggest this should be repaired?  

Note, I have not checked all of the cm3.cfg variants for the other
target platforms, but in order for reactor to work properly, it must be
able to find a valid "PKG_USE" in the cm3.cfg.

Regards,
Randy

Climb to the top of the charts! Play the word scramble challenge with
star power. Play now! (
http://club.live.com/star_shuffle.aspx?icid=starshuffle_wlmailtextlink_jan
) 
Climb to the top of the charts! Play the word scramble challenge with
star power. Play now! (
http://club.live.com/star_shuffle.aspx?icid=starshuffle_wlmailtextlink_jan
) 
Need to know the score, the latest news, or you need your Hotmail*-get
your "fix". Check it out. ( http://www.msnmobilefix.com/Default.aspx ) 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20080124/0f4e7679/attachment-0002.html>