On 10/20/06, Marvin Humphrey <[EMAIL PROTECTED]> wrote:
On Oct 18, 2006, at 7:34 PM, Marvin Humphrey wrote: > We may need to augment those loops with some symbol detection, > break them up if possible, or just come up with a different approach. The naive probing approach is a goner -- can't probe for object extention and executable extension on top of everything else. I'm going to try setting things up so that we pass a lower-case string representing the OS via the infile. Is that information available to you in Ruby?
Yep. No problem there.
Then we'll detect the compiler using symbols: __GNUC__, etc. Right now, the only compilers I'm really concerned about are GCC and MSVC. We can add more later.
Yep sounds good to me. As long as we have the framework set up for others to extend it to work on different compilers we should be fine.
