On 3/24/07, D.J. Heap <email@example.com> wrote:
> On 3/23/07, Joe Swatosh <firstname.lastname@example.org> wrote:
> > In the absense of actual understanding I was going for consistency;
> > copy everything. But I'm not married to any of this, although I find
> > it useful as it puts everything in one place.
> > As far as changing how the sqlite directory is laid out, again I have
> > no problem. I've been trying to let the original packagers have their
> > way and the .zip files I downloaded with the .dll and .h files don't
> > have any directory structure within them. The one question I would
> > have is since it is working for me all mashed together, would the
> > gen-make.py have to be modified to know where to get the .lib and .h?
> I think it does already (seems to be working for me with that
> structure - inc/lib directories under --with-sqlite directory).
Great, I'll change to match.
> > As long as I have your attention, I wanted to ask now, while it is
> > still a ways off, if you have any interest in producing Windows
> > binarys for the Ruby bindings when the 1.5 time comes? And if you are
> > willing to take on that additional task, how can I help?
> Sure -- I've made some feeble attempts in the past, but since you've
> obviously been successful I'll give it a more serious shot. Did you
> have to build Ruby from source yourself or do you match the compiler
> they used for the standard dist? Or is that not necessary at all? It
> seems like my main problem was different compiler/CRT versions if I
> recall correctly.
I've been using the "One-Click Installer"
I've been using Ruby 1.8.5, I'll upgrade to 1.8.6 this weekend. So no
I have not been building Ruby from source. I'm matching the compiler
used which is VC6 (I think I read that that is the one your using?).
There are prebuilt windows binaries at
although there isn't any indication that I can find about what
compiler was used. I'm guessing it's VC6 because I think these are
what are packaged in the one-click installer.
There _are_ problems on Windows with mixing the CRT versions that are
used to build Ruby vs that used to build extensions. So the problems
you're describing aren't surprising.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sat Mar 24 18:48:22 2007