Is that available for cygwin? I didn't see it in the list of packages
or libraries.
Dave
David Blue (Mailing List Addy) wrote:
On Sunday 18 December 2005 19:16, David Forslund wrote:
Fixing this made a big difference, but now when compiling
utilfuns/utilstr.cpp, it can't find various uni
That gets it further. Now it has a problem with lucene. I don't think
there is a lucene package in cygwin (at least by default). Can I
comment out the lucene compile, too? Or is it available somewhere?
Dave
Troy A. Griffitts wrote:
David,
You might try editing usrinst.sh to not build
On Sunday 18 December 2005 19:16, David Forslund wrote:
> Fixing this made a big difference, but now when compiling
> utilfuns/utilstr.cpp, it can't find various unicode/*.h include files.
> I can't tell what package is supposed to have them.
I believe libunicode is what you want
_
David,
You might try editing usrinst.sh to not build with ICU, for now. Then
restart the build process from ./usrinst.sh
Thanks for staying with this.
-Troy.
David Forslund wrote:
Fixing this made a big difference, but now when compiling
utilfuns/utilstr.cpp, it
Fixing this made a big difference, but now when compiling
utilfuns/utilstr.cpp, it can't find various unicode/*.h include files.
I can't tell what package is supposed to have them.
thanks,
Dave
Chris Little wrote:
Actually, it's just a problem in the installed CygWin environment. The
defaul
I can try this out. What I need to know are the required dependencies
of the sword software to see what needs to be installed with cygwin.
It is difficult to guess from error messages.
Thanks,
Dave
Chris Little wrote:
Actually, it's just a problem in the installed CygWin environment. Th
Actually, it's just a problem in the installed CygWin environment. The
default Cygwin environment isn't a full development environment, so you
need to install libtool (and maybe other packages) using the CygWin
installer.
(I'm not sure that there aren't OTHER problems with a CygWin build, but
Hi,
you can send me the file. I'll put this and the module together into the beta
section of the modules so users can test the module for 2-3 weeks before the
module can be released on the main site (if no copyright or content problems
remain).
Thank you for your work,
Joachim
> Thanks fo
