I have the latest scintilla building as a dll and static library using
visual studio 6 if you want me to send you a zip of it all.
I haven't tested the static build as I don't use it.
Thanks Tom, but Scintilla builds right "out of the box" as both a static lib and .dll on windows, not an issue really.
The problem is there are two extensions here we're talking about based on two different "base" libraries that do basically the same thing.
1. Is gtkscintilla from
http://sourceforge.net/project/showfiles.php?group_id=31426 . Really it's a wrapper around the scintilla library that makes it act more "gtk-ish" What makes this a good choice? A lot of linux distros use this already, it builds as an .so "out of the box". What makes it a bad choice? My biggest issue is it's completely unmaintained. The last release was in 2003, and it doesn't build without some code hacking on windows. We'd basically have to support gtkscintilla in some way ourselves.
2. Is straight scintilla from
http://www.scintilla.org/ . This is the actual underlying library. What makes this a good choice? Well maintained, new releases, bugfixes on a regular basis, builds "out of the box" as both .dll and static lib on windows. What makes it a bad choice? The only makefile provided builds a static linux library (.a), so there's no .so that's routinely distributed on *nix like gtkscintilla. We could bundle the library with a makefile to generate an .so or figure out how to use the php-gtk build system to build the static library first and then link it with the php-gtk build system, but as I said before I'm not a *nix user and Anant can't figure out how to do it.
Personally I'm not a fan of trying to upgrade and maintain gtkscintilla, so I'd prefer the straight scintilla solution, besides the fact that I really don't have time to be hacking up the source to get it cooperating on windows with MSVC. The PyGTK extension has moved to straight scintilla as well. Anant would prefer the gtkscintilla solution since it would require no work on the *nix end.
Anyone else have some thoughts on which would be the "better" solution? Would someone with autotools experience willing to step up and figure out how to bundle the scintilla library and get it building easily on *nix to distribute with php-gtk? That is the main issue with option 2.
Or would someone be willing to take over support and maintainence of the gtkscintilla wrapper (including getting it building with MSVC on windows, updating the bundled scintilla lib, and fixing bugs?) since distributing something based on an unmaintained library is not really the best idea.
Anyway, just my views on this subject (we keep going around and around here...)