2008/2/8 Charlie Savage <[EMAIL PROTECTED]>: > > > > Rather then a one-off script, care to help me automate that > > functionality in Reap? > > Took a quick look, does it have any support for building c extensions?
Yes, using extconf.rb and make. > The problem you'll run into is that you can't use extconf.rb on Windows > with MinGW because all the CONFIG settings are based on VC++ and not on > MingW. Oh? Hmm... I'm just going by what I've read others doing --cross compiling on Linux using mingw. I'm not sure at all about actually compiling on a WIndows platform, since I don't use Windows at all. > Ruby needs something like Python's DistUtils, which support for > using various different compiles. That would be nice, of course. But I imagine that's a whole additional level of heavy involvement. Ultimately it would be great to add this level of functionality to Reap. But that's outside of my scope. If other would like to do so though, I'd be more than happy to work with them in accomplishing it. > So, you have to roll your own solution (I don't know of any good one > sadly). My approach with ruby-prof is to have a rakefile that I run > from a msys prompt that invokes gcc. You could of course just use Make > instead. If that's the case, it might be possible right now. $ reap-make That's the same as running extconf.rb and then make by hand. The only thing substantially missing is building binary packages. That shouldn't be too hard though, as it basically means setting the platform field and not doing a full distclean before packaging. Or am I missing something? > I've just reached an early beta status with > > this project, and these two features are on the upcoming todo list: > > binary platform packages and mingw Windows cross compile. > > I wouldn't bother with the cross-compile (if you mean build Windows > libraries on Linux or some other OS). First you'll need access to the > VC++ ruby libraries. Yea, I'm not sure. I haven't really tested it. I simply read of others doing it and their examples. Basically it requires re-compiling ruby itself with mingw, and from there supposedly one can make it work. > Second I can't see how that will work anymore in > the latest version of Ruby Gems (which seems to require building on the > same OS and what you deploy to, at least for Windows). Arghh... If that's true, that pisses me off. Eric Hodel is a source of endless headaches! > Long story short - you have to roll a custom solution for MinGw and > create a separate GEM for win32. I'd love if there is a better way, > but I've never found one. I wrote a script for it actually, but before I could test it, I accidentally deleted it :-( Basically it downloaded Ruby source, compiled it under mingw and then compiled one's project against that. That at least is the account of others who have done it manually --I'm just trying to automate what they reportedly have done by hand. Is there more to it then I am understanding? I admit I'm pretty amateurish when it comes to compiling --I really don't have any love for c. T. _______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
