<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-15">
<META content="MSHTML 6.00.6000.16587" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>Jay:</DIV>
<DIV> </DIV>
<DIV>That's the reason I asked before making a change. I don't want to break or mess up what you are doing.</DIV>
<DIV> </DIV>
<DIV>I can get around the problem easily for me. I just remove the comment from the </DIV>
<DIV>%INSTALL_ROOT="c:\\cm3" </DIV>
<DIV>and "everything" is ok.</DIV>
<DIV> </DIV>
<DIV>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.</DIV>
<DIV> </DIV>
<DIV>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.</DIV>
<DIV> </DIV>
<DIV>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.</DIV>
<DIV> </DIV>
<DIV>BTW, I still don't see why all this "works" since I am getting "\.." as my INSTALL_ROOT.</DIV>
<DIV> </DIV>
<DIV>Regards,</DIV>
<DIV>Randy<BR><BR>>>> Jay <jayk123@hotmail.com> 1/24/2008 7:24 PM >>><BR>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.<BR> <BR>path() is a builtin Quake function that returns the directory of the currently being run Quake code.<BR> <BR>But yet Reactor.<BR>To unblock yourself, remove my code, add back the commented out, fix the path to match your particular install, don't submit the file.<BR> <BR>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.<BR> <BR> - Jay<BR><BR></DIV>
<DIV>
<HR id=EC_stopSpelling>
</DIV>
<DIV>Date: Thu, 24 Jan 2008 18:53:48 -0500<BR>From: rcoleburn@scires.com<BR>To: jay123@hotmail.com<BR>CC: m3devel@elegosoft.com<BR>Subject: [M3devel] INSTALL_ROOT and PKG_USE in cm3.cfg<BR><BR>
<META content="Microsoft SafeHTML" name=Generator><BR></DIV>
<BLOCKQUOTE>
<DIV>Jay:</DIV>
<DIV> </DIV>
<DIV>The cm3.cfg that comes with your minimal binary installation on Windows (NT386) has the following lines:</DIV>
<DIV> </DIV>
<DIV>-----------------------------------------</DIV>
<DIV>% INSTALL_ROOT = BEGIN_CONFIG<BR>% "Where should CM3 be installed?"<BR>% 7 %-- user specified install root<BR>% END_CONFIG</DIV>
<DIV> </DIV>
<DIV>% INSTALL_ROOT = "c:\\cm3"</DIV>
<DIV> </DIV>
<DIV>if not defined("INSTALL_ROOT")<BR> if not equal ($INSTALLROOT, "")<BR> INSTALL_ROOT = $INSTALLROOT<BR> else<BR> INSTALL_ROOT = (path() & "\\..")<BR> end<BR>end</DIV>
<DIV> </DIV>
<DIV>BIN_INSTALL = INSTALL_ROOT & "<A target=_blank>\\bin</A>" % executables<BR>LIB_INSTALL = INSTALL_ROOT & "<A target=_blank>\\lib</A>" % libraries<BR>PKG_INSTALL = INSTALL_ROOT & "<A target=_blank>\\pkg</A>" % packages<BR>DOC_INSTALL = INSTALL_ROOT & "<A target=_blank>\\doc</A>" % documents<BR>EMACS_INSTALL = INSTALL_ROOT & "<A target=_blank>\\elisp</A>" % emacs lisp code<BR>MAN_INSTALL = INSTALL_ROOT & "<A target=_blank>\\man</A>" % man pages<BR>HTML_INSTALL = INSTALL_ROOT & "<A target=_blank>\\www</A>" % public hypertext</DIV>
<DIV> </DIV>
<DIV>%<BR>% On some systems (e.g. AFS) you must install public files in a different<BR>% place from where you use them. If that is the case for your system,<BR>% specify the "use" location here, otherwise leave them alone.<BR>%<BR>%USE_ROOT = INSTALL_ROOT<BR>BIN_USE = BIN_INSTALL % executables<BR>LIB_USE = LIB_INSTALL % libraries<BR>PKG_USE = PKG_INSTALL % packages<BR>
<DIV>-----------------------------------------</DIV>
<DIV> </DIV></DIV>
<DIV>Notice that the lines for INSTALL_ROOT and USE_ROOT are commented out.</DIV>
<DIV> </DIV>
<DIV>The Reactor program is coded to grab several variables out of cm3.cfg. For example,</DIV>
<DIV> </DIV>
<DIV> build_dir := M3Config.Get ("BUILD_DIR");<BR> system_root := M3Config.Get ("PKG_USE");<BR> doc_root := M3Config.Get ("DOC_INSTALL");<BR> initial_browser := M3Config.Get ("INITIAL_CM3_IDE_BROWSER");<BR> initial_editor := M3Config.Get ("INITIAL_CM3_IDE_EDITOR");<BR></DIV>
<DIV>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.</DIV>
<DIV> </DIV>
<DIV>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=\..</DIV>
<DIV> </DIV>
<DIV>I'm not sure why this is coded this way.</DIV>
<DIV> </DIV>
<DIV>How do you suggest this should be repaired? </DIV>
<DIV> </DIV>
<DIV>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.</DIV>
<DIV> </DIV>
<DIV>Regards,</DIV>
<DIV>Randy</DIV></BLOCKQUOTE><BR>
<HR>
Climb to the top of the charts! Play the word scramble challenge with star power. <A href="http://club.live.com/star_shuffle.aspx?icid=starshuffle_wlmailtextlink_jan" target=_new>Play now!</A> </BODY></HTML>