Topic: Usage of the --homedir option
fuchur Topic Opener |
Posted at: 2019-05-11, 12:26
Thanks a lot GunChleoc, downgrading boost solved the issue. I just had to replace I'll take care not to mix up the several sources. I never worked with bzr and the like, so thanks for your hints. Now ninja aborted with the following error.
That looks more like an error in boost. Do I need to downgrade to another older version? I tried that with current trunk, not with build20. And I run a debug build. But the same happens for the build20 source from the downloaded archive. Downgraded boost to 1.68, but I need to leave now. Will try later to compile again. Top Quote |
hessenfarmer |
Posted at: 2019-05-11, 15:13
You need to Patch libintl.h the Patch is available in utils i think. Top Quote |
fuchur Topic Opener |
Posted at: 2019-05-12, 14:24
Thanks hessenfarmer. As it compiles now with boost 1.68 I'll keep that at the moment. But I'll keep your information in mind in case I need it some time. The good news is I can build a widelands.exe from trunk. The bad news is it won't run. Ok, in more detail:
Edit:
Ok, I think I found the reason for the segmentation fault. In
Commenting this line solves my homedir problem. Ok, I think the best way is to change it to Edited: 2019-05-12, 14:43
Top Quote |
hessenfarmer |
Posted at: 2019-05-12, 15:21
the .exe you get by MSYS2 is dynamically linked which means you need to copy all relevan dll files to the installation directory. With all of them present you should be able to do so. Normally I install a trunk version from Appveyor and exchange the exe in this folder with my own compiled exe. So i am sure I have all dll present. Top Quote |
hessenfarmer |
Posted at: 2019-05-12, 15:23
Just forgot to mention. On appveyour we use Innosetup to collect all dlls and compile an installer. at list you can have a look at utils folder and search for the .iss file to see which dll are needed. You need to copy the datadir to the installation folder as well. Top Quote |
GunChleoc |
Posted at: 2019-05-12, 16:12
I have fixed the homedir code directly in trunk, Regarding Edited: 2019-05-12, 16:12
Busy indexing nil values Top Quote |
fuchur Topic Opener |
Posted at: 2019-05-12, 20:18
Your're welcome. And thanks for fixing it so quickly. Regarding your comment on launchpad: I'll try to get rid of the other problems which should be no problem due to the hints of hessenfarmer. Then I'll report if it's ok. Unfortunately the next days I'll be quite busy with other things.
Yes, it exists in my copy of trunk. It was my fault. I simply copied the built widelands.exe to the installation folder of build20. I assumed as the release was only a few days old there wouldn't be much changes. But obviously I was wrong as there (in build20) is no @hessenfarmer Thanks for clarifying the differences between static and dynamic linking of the different builds. I will follow your advice and install an appveyor build to have a working base for testing. It seems there are a lot of traps one can fall in. So unfortunately I need to ask all those beginner questions. Top Quote |
hessenfarmer |
Posted at: 2019-05-13, 12:53
You're welcome. The Problem with the MSYS2 environment is that it tries to keep up to date libraries which means the windows builds (either in your own MSYS2 or in Appveyor) do experience any problem in our third party libraries first. Top Quote |
GunChleoc |
Posted at: 2019-05-13, 18:57
You can assume more changes to the data directory in the coming days. The workareas are the fancy new overlay that Nordfriese programmed for us Busy indexing nil values Top Quote |
fuchur Topic Opener |
Posted at: 2019-05-13, 21:33
Ok, short update. I installed an Appveyor build to get the needed DLLs. Using these I can run and test widelands directly from windows command line or a shortcut. Now the --homedir option works like expected, thanks GunChleoc Edited: 2019-05-13, 21:35
Top Quote |