[M3devel] [M3commit] CVS Update: cm3

[Randy Coleburn]

Jay:
 
Your change to MxConfig.m3 seems to work fine for cm3ide, provided that I replace HOST by "NT386" in my cm3.cfg is as follows:
 
INSTALL_ROOT = path() & "/.."
include (path() & "/config/NT386")
 
Thank you!
 
Can we get your revised MxConfig.m3 put into the RC2 branch?
 
Regards,
Randy

>>> "Randy Coleburn" <rcoleburn at scires.com> 8/3/2009 11:35 AM >>>
Jay:
I agree that running cm3 from "bin" folder is not going to be productive; however, other programs (such as cm3ide) also use the quake stuff and they don't have this limitation.  I think your change is a good one.  I'll run some tests and see how cm3ide fares.  Thanks.
--Randy

>>> Jay Krell <jkrell at elego.de> 8/3/2009 11:31 AM >>>
CVSROOT:/usr/cvs
Changes by:jkrell at birch.09/08/03 11:31:35

Modified files:
cm3/m3-sys/m3quake/src/: MxConfig.m3 

Log message:
use "." instead of empty string for path() when current working
directory is the actual directory of cm3; not sure what good
running cm3 here is, and we probe way too many places..


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/3566f8ba/attachment-0002.html>