Cross compiling for Windows(eventually DOS) under Ubuntu

[WWTBAM]

I am trying to build the Windows version of OpenTTD under the Windows Subsystem for Linux which runs an Ubuntu userland on top of a reverse Wine like set of drivers for the Windows NT Kernel. I am able to build the windows version of OpenTTD so long as I exclude all the optional libraries. Building OpenTTD with the following set of commands in Bash on Windows gives me a "working" executable - by working I mean most savegames can't be loaded amongst other optional things.

Code: Select all

./configure --host=i686-w64-mingw32 --without-png --without-icu --without-liblzma --without-lzo2 --without-zlib --without-sdl --without-iconv
make

I would like to get the libraries working. I have tried following the wiki page on cross compiling for Windows without luck. I suspect I need to go over the contents of that page to make sure all the commands I execute from that page work properly under WSL. I would like to try and get zlib working first, so that I can at least get the titlegame to load(currently I just get water).

edit:
or I may need to hack some scripts in the build process as Rubidium told me on IRC a coule of days ago. I would not have any clue as to which scripts to hack at though.

[adf88]

It think I don't understand something ... if you are building on windows for windows, why cross compile? Just use MSYS or MSVC...

Anyway, I recently compiled windows binaries on Linux with all the libraries. However, I couldn't make ICU working, OpenTTD hangs on startup. If someone has a solution then that would be great.

Get the source, apply the patch (optional) and execute commands from the script (I suggest doing this one by one). The patch removes some warnings.

[Eddi]

if you are building on windows for windows, why cross compile?

sometimes travelling is about the journey, not about the destination.

[adf88]

OFC, I'm traveling a lot last time

I'm just wondering why, just "because I can" or because of other reasons?

[WWTBAM]

I wanted to cross compile for windows as I have a working Windows environment now while I don't have a working DOS environment at the moment. I also figured cross compiling for Windows should be more straight forward than for DOS as cross compiling for Windows is done more regularly. I am on a 64 bit host.

[Transportman]

Why do you need to exclude the optional libraries? Do you get errors when not excluding them? Or does nothing happen at all when not excluding them?

[WWTBAM]

The build process assumes you want all the optional libraries that I have to exclude as some of them are almost not optional e.g. the compression libraries. Without zlib for example the nightly titlegame won't load.

[Transportman]

I think we have a small misunderstanding. I want to know why you are excluding them as it seems to me you want to include them (which would happen when not excluding them according to your post).

[WWTBAM]

I get errors when including them. The build process can't find them regardless if I have built them or not.

[Transportman]

If I read the commands here, you might try by pointing to the location of the libraries, instead of letting the system finding them.

[adf88]

If I read the commands here, you might try by pointing to the location of the libraries, instead of letting the system finding them.

This guide is outdated. I planned to update it, but I didn't found a solution for ICU crashing so I withdrew. See a new one that I attached few posts ago. It has no comments but instructions are similar to those on Wiki.