Hi all,
Thanks for your help!
I finally got libsword.dll built by cross-compiling in linux (using cmake).
For completness I have included the details of my solution:
The main trouble seemed to be the conflicting icu51 includes provided by
mxe and my build of icu54 dlls. They were both cross-comp
I never have finished getting the CMake system working for MSVC, so that is
probably contributing to your woes. I never keep a Windows build system
around long enough to fully test it.
In the Linux world, what distro are you using? All of the dependencies for
cross compile are presently available
I have tried both windows as build machine and linux as build machine.
*In the windows case*, I used mingw for anything that could be built using
gnumake (sometimes using cmake to get the Makefiles).
ICU couldn't be built with cmake it seams, so I built that with visual
studio.
libsword wouldn't bu
Hi Daniel
I'm sure you've thought of this, but can you get everything to build and
link using VS2013?
I was having similar problems trying to call libsword functions in the
flatapi from C# - the
libsword.dll would compile without complaint but the C# application
would crash saying it
could not
When you are trying to compile with mingw, what is your host environment?
Karl Kleinpaste and I build for Windows with the mingw toolchain from Linux
on a regular basis.
If you are building the latest release of sword (1.7.4) with cmake+mingw
you will likely find that the .dll is stored in the bin
Hi Jon,
Yeah, I hadn't done all the steps correctly - nevertheless MSVS was still
generating the dll.
It appears it's a mingw/msvc interoperability issue because the dll is
generated but I can't link against it.
I can't seem to build it with cmake either. I get as far as the libsword.a
and libswo
Hi Daniel
Since your problem is in the flatapi, continue in the instructions for
the c# bindings.
There are some changes that need to be made in the dll export
declaration to get
it to work with Windows. Those are steps 5 and 6 of the tutorial. Also,
in step 9, you
need to make sure that the dl
Yeah, I wondered about the msvc/mingw issue. I have tried building sword
with cmake/mingw to no avail... though perhaps with thes changes to flatapi
it will work.
Funny thing is that I can link to the xiphos libsword.dll no problem - but
then run-time dlls are missing.
--
In the beginning Kibo cre
You mentioned using msvc and mingw together. That probably will need you
up. Additionally, if you don't want to use flatapi, then you shouldn't
include that set of files.
On Dec 31, 2014 6:05 PM, "Daniel Sheffield" wrote:
> Hi Jon,
>
> Thanks for that help, I changed icu-sword dir back to icu (it
Hi Jon,
Thanks for that help, I changed icu-sword dir back to icu (it really is the
latest icu - not icu-sword!), and rebuilt the dll.
Still can't link to it: -lsword -licuuc54 -licuin54 -licudt54
Linker doesn't complain can't find lib or anything, but still outputs the
errors in my prior message.
Hello Daniel
Look here http://www.crosswire.org/wiki/CSharp_Bindings_on_Windows
The first section of this tutorial deals with changes needed to get
Sword 1.7.3 to build
with VS2013. You can ignore the remainder.
Be blessed,
Jon
On 12/30/2014 8:29 PM, Daniel Sheffield wrote:
Hi all,
I've been h
11 matches
Mail list logo
