[M3devel] problems with cm3.cfg and MxConfig

Randy Coleburn rcoleburn at scires.com
Mon Aug 3 06:52:45 CEST 2009


I have been working on the problem of cm3ide not getting the BUILD_DIR from cm3.cfg.  I've run across some perplexing test results.
 
MxConfig.Get("BUILD_DIR") is returning NIL on Windows XP & Vista.  I've tracked it down a bit further.  There seem to be two issues that must be fixed to solve this problem:
 
1.  HOST does not seem to be defined.  In particular my "C:\cm3\bin\cm3.cfg" file appears as follows (this is the file Jay recommended):
INSTALL_ROOT = path() & "/.."
include (path() & "/config/" & HOST)
 
Is HOST a variable?  Or, was I supposed to replace it by "NT386"?  If the latter, my bad on this one--I took Jay's message literally.
 
2.  path() does not appear to always yield the path to the bin folder.  In particular, it seems to work fine unless you invoke the program when the current directory is actually set to the bin folder, in which case path() seems to return the empty string.
 
So, if %CD%=C:\, and I run cm3ide, path() returns "C:\cm3\bin" as it should.
But, if %CD%=C:\cm3\bin, and I run cm3ide, path() returns "".
 
So in the latter case, the include statement winds up trying to pull a file from the wrong place, e.g. "/config/NT386" rather than "C:\cm3\bin/config/NT386"
 
Regards,
Randy Coleburn

CONFIDENTIALITY NOTICE:  This email and any attachments are intended solely for the use of the named recipient(s). This e-mail may contain confidential and/or proprietary information of Scientific Research Corporation.  If you are not a named recipient, you are prohibited from making any use of the information in the email and attachments.  If you believe you have received this email in error, please notify the sender immediately and permanently delete the email, any attachments, and all copies thereof from any drives or storage media and destroy any printouts of the email or attachments.

EXPORT COMPLIANCE NOTICE:  This email and any attachments may contain technical data subject to U.S export restrictions under the International Traffic in Arms Regulations (ITAR) or the Export Administration Regulations (EAR).  Export or transfer of this technical data and/or related information to any foreign person(s) or entity(ies), either within the U.S. or outside of the U.S., may require export authorization by the appropriate U.S. Government agency prior to export or transfer.  In addition, technical data may not be exported or transferred to certain countries or specified designated nationals identified by U.S. embargo controls without prior export authorization.  By accepting this email and any attachments, all recipients confirm that they understand and will comply with all applicable ITAR, EAR and embargo compliance requirements.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20090803/95580dc1/attachment-0001.html>


More information about the M3devel mailing list