So leave the CRuby libs portion alone for now, and just get it to identify a root path. That I can do.
JD From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Lam (IRONRUBY) Sent: Thursday, June 05, 2008 1:49 PM To: [email protected] Subject: Re: [Ironruby-core] irvars.bat Make it calculate the path based on the path where irvars.bat lives- put it in a known location and you should be able to figure out everything else modulo MRI lib install path based on that. In the future we'll start shipping the MRI standard pure ruby libs along with IronRuby. -John From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jim Deville Sent: Thursday, June 05, 2008 4:45 PM To: [email protected] Subject: Re: [Ironruby-core] irvars.bat Fixed. So this still leaves the problem of how to manage it so it doesn't have version conflicts. We could make a irvars.bat.temp in the repo, add irvars.bat to the .svnignore and have people fill out the Ruby path in their personal copy of irvars.bat. But I'm not wild about that one. Any other ideas? JD From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Letterle Sent: Thursday, June 05, 2008 1:37 PM To: [email protected] Subject: Re: [Ironruby-core] irvars.bat Looks good, it does look like PROGRAM_FILES_64 is never actually used... On Thu, Jun 5, 2008 at 4:29 PM, Jim Deville <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote: Any problems with this file? It's what I have so far as the batch file for the SVN vars. jd _______________________________________________ Ironruby-core mailing list [email protected]<mailto:[email protected]> http://rubyforge.org/mailman/listinfo/ironruby-core -- Michael Letterle [Polymath Prokrammer] http://blog.prokrams.com
_______________________________________________ Ironruby-core mailing list [email protected] http://rubyforge.org/mailman/listinfo/ironruby-core
