Linux cross compiling for windows failing

[nohal]

Jon...
I have updated the compilation instructions so that now the new versions of Poedit are mentioned first as most of the new readers will have them already.
BTW, it is all a wiki, so if you have an account on opencpn.org, you can make these changes directly - about the same amount of work as posting here and you'll be sure it gets done - although I try to follow all the meaningful posts and update the docs accordingly when needed, it's not always possible.

Cheers

Pavel

[jongough]

Having now compiled and run OCPN under windows I can see that there is a difference in where the zlib is. Under windows there is a wxzlib*.lib file for linking. Under Linux with cross compiling the zlib is only incorporated in the Linux version of the wxwidget library, i.e. ones ending in "*.a", there is no DLL generated with the zlib components, i.e. gzopen, incorporated. This is probably why it is failing the link part.

There must be another option for the compiling of the wxWidgets library that will cause a DLL to include the zlib components. Does anyone know what it is?

[jongough]

Pavel,
Thanks for doing that and telling me how to update the doco. I have now updated the Windows compile/run doco to fix up a couple of errors (missing '.'s) and to show how to run opencpn the first time without installing it. I will continue to update as and when I find things.

Jon

Originally Posted by nohal

Jon...
I have updated the compilation instructions so that now the new versions of Poedit are mentioned first as most of the new readers will have them already.
BTW, it is all a wiki, so if you have an account on opencpn.org, you can make these changes directly - about the same amount of work as posting here and you'll be sure it gets done - although I try to follow all the meaningful posts and update the docs accordingly when needed, it's not always possible.

Cheers

Pavel

[jongough]

After failing to link properly because gzopen etc cannot be found I hunted around and eventually did a cross compile of zlib to generate libz.dll.a and zlib1.dll. I copied these to the wxWidgets-mingw directory and now the make completes successfully.

I had to issue this command in the zlib-1.2.8 directory
make -f win32/Makefile.gcc CC=/usr/bin/i686-w64-mingw32-gcc RC=/usr/bin/i686-w64-mingw32-windres
to get the windows DLL's produced.

Now I have a built version of opencpn.exe and the two plugins. I am not sure it will work as I think there may still be a problem with the InterlockedCompareExchange, which I got around by commenting out the
SET( CMAKE_EXE_LINKER_FLAGS "../buildwin/mingw-export-symbols.def" )
line in CMakeLists.txt

I have tried to run opencpn.exe under wine, but it fails with a:
wine: Unhandled page fault on write access to 0x0081ee6c at address 0x6f5263d0 (thread 000b), starting debugger..
message. I will have to try and track this down. But I want to see if it will acutally run under windows to make sure I am doing things correctly.

[seandepagnier]

Now it built, but only has a run-time error?
Did you copy the needed gcc and mingw dll files?

Did you try a prebuilt mingw opencpn package? It should work under wine.
opencpnplugins - Browse /opencpn_mingw_experimental at SourceForge.net

[jongough]

I have just managed to get back to the cross compiling and am now falling foul of NSIS and no Unicode support. The "make package" seems to generate a "project.nsi" file with "Unicode true" in it. However, NSIS 2.46-7, which is all that is currently available for Ubuntu does not have unicode support in it. The 3.0-beta apparently does have support but I am having trouble finding a copy that I can install.

[seandepagnier]

I am using version nsis 3.0b, if you install that, it should work.

Otherwise, maybe you can disable unicode support in the installer? I'm not sure how it works for visual studio.

In any case, does the mingw opencpn.exe you built run ok?

[nohal]

Sean...
The NSIS packaging step comes to play after VS (or gcc) is done. And we kind of need the unicode version to support non-ASCII charsets in the installer. Of course it can be stripped out, but I don't see any reason why the unicode version should not work.
@Jon: the unicode version of 2.46 lives at Unicode NSIS

Pavel

[jongough]

Pavel,
I may be missing something, but every unicode version of NSIS I can find is a windows exe file. If I get the source and try and compile it for unix it fails with all sorts of errors.

Jon

Originally Posted by nohal

Sean...
The NSIS packaging step comes to play after VS (or gcc) is done. And we kind of need the unicode version to support non-ASCII charsets in the installer. Of course it can be stripped out, but I don't see any reason why the unicode version should not work.
@Jon: the unicode version of 2.46 lives at Unicode NSIS

Pavel

[nohal]

Jon...
What errors are you getting? I have just built it successfully using:

tar xjf nsis-3.0b1-src.tar.bz2
cd nsis-3.0b1-src
scons SKIPSTUBS=all SKIPPLUGINS=all SKIPUTILS=all SKIPMISC=all NSIS_CONFIG_CONST_DATA=no PREFIX=. install-compiler

It does not mean that I know you need to build it at all, maybe you should run the Windows version under Wine...

Pavel

[jongough]

Pavel,
I have just done what you did below with the 3.0b1 src and it built. I was getting errors with the 2.46 Unicode builds like:
g++ -o build/urelease/makensis/build.o -c -Wno-non-virtual-dtor -Wall -O2 -m32 "-DNSISCALL= __attribute__((__stdcall__))" -D_WIN32_IE=0x0500 -Ibuild/urelease/config Source/build.cpp
In file included from Source/build.cpp:24:0:
build/urelease/config/nsis-version.h:3:19: fatal error: tchar.h: No such file or directory
#include "tchar.h"
^
compilation terminated.

Now that I have built it I tried to run just makensis -h from the bin directory and got:
Error: opening stub "./share/nsis/Stubs/zlib-x86-ansi"
Error initalizing CEXEBuild: error setting default stub

I must be missing something at a fundamental level. I am being confused by the apparent mix between unix and windows directories, installation instructions, reference, etc.

Originally Posted by nohal

Jon...
What errors are you getting? I have just built it successfully using:

tar xjf nsis-3.0b1-src.tar.bz2
cd nsis-3.0b1-src
scons SKIPSTUBS=all SKIPPLUGINS=all SKIPUTILS=all SKIPMISC=all NSIS_CONFIG_CONST_DATA=no PREFIX=. install-compiler

It does not mean that I know you need to build it at all, maybe you should run the Windows version under Wine...

Pavel

[nohal]

Jon...
You should get the stubs from the binary distribution of NSIS (Open it as an archive).
They in theory are buildable with something like

scons SKIPPLUGINS=all SKIPUTILS=all SKIPMISC=all NSIS_CONFIG_CONST_DATA=no APPEND_CPPPATH=/usr/include/wine/windows PREFIX=. install-stubs

It fails for me (but I'm not trying to crosscompile, don't have the environment).

Pavel

[jongough]

I have tried running the opencpn.exe under both windows and a real win 7 machine (the one I used the MSVC compiler on), but I get a crash.

wine opencpn.exe
wine: Unhandled page fault on write access to 0x0081ee6c at address 0x6f5263d0 (thread 002d), starting debugger...
fixmele:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046}

I have attached the backtrace file as well.

Originally Posted by boat_alexandra

I am using version nsis 3.0b, if you install that, it should work.

Otherwise, maybe you can disable unicode support in the installer? I'm not sure how it works for visual studio.

In any case, does the mingw opencpn.exe you built run ok?