On Feb 9, 9:30 pm, Charlie Savage <[EMAIL PROTECTED]> wrote: > almost no one on Windows has a C/C++ > compiler installed so making extconf.rb/mkmf.rb work doesn't really buy > you much.
Right, right. But just having the compile process be the same --for developers, whatever the platform, is the benefit I'm after here. I understand, we still will need to make a Windows platform package for end-users. > Thus for ruby-prof I build a Windows executable on my machine, put it in > source control, and create a Windows specific gem for it. > > I think that's the way to go - its easy and fool-proof. The downside of > course is that it means you have to have a special environment setup to > rebuild the Windows binary, but that's going to be true no matter what > you do. That's fine. I'm happy to put the cross-compile on an indefinite back- burner. Lord knows, I have enough to do. But I do want to get the compile process uniform from the developers perspective, which means an extconf.rb file that handles any platform --that way it works across the board, with RubyGems, setup.rb and reap. I just updated the extconf.rb, putting in the master if-condition. I added a Makefile template to the data section at the bottom of the file. For the win32 part it simply grabs the DATA and eval it in context to build the Makefile. The template currentlu is just a copy of what extconf.rb already generates -- which can serve a starting point and we can modify it to suit Windows (ideally we will be able to keep the template platform-neutral and add the windows specifics via the eval process.) Will you take a look at it and help me get it in order? T. _______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
