Topic: Usage of the --homedir option
fuchur Topic Opener |
Posted at: 2019-05-07, 18:00
Yesterday I installed the new build20. As I didn't want to uninstall or overwrite my other installations (build19 and intermediate versions) I installed it to a different folder. And I made a backup of the old settings folder. Then I created a new folder for the build20 settings and added I remember that I managed to get it running with build-8670, but there have been similar problems at the beginning, too. Unfortunately I don't remember what I did to get it working Any hints what to do are greatly appreciated. System: Windows 7 64 Bit Edited: 2019-05-07, 18:02
Top Quote |
kaputtnik |
Posted at: 2019-05-07, 18:31
I guess you need forward slashes for the path:
? Fight simulator for Widelands: |
fuchur Topic Opener |
Posted at: 2019-05-07, 22:12
Thanks for the quick response. Unfortunately that doesn't change anything. In my other configuration for build8670 it works with backslashes. I checked the rights of the folder, but there is nothing suspicious. I'm owner and have full access. I will investigate it further when I have more time. Top Quote |
ModellbahnerTT |
Posted at: 2019-05-07, 23:12
Maybe it helps to set \\ instead of \ because one \ is an special sign for windows. Edited: 2019-05-07, 23:13
Top Quote |
fuchur Topic Opener |
Posted at: 2019-05-08, 21:37
No, that doesn't help. Well, it shouldn't help anyway. \ is used at the beginning of a path in certain cases, like a network path (\server\share\folder), but not for a folder starting with c:... Of course in C you need \ to output a single \ because it is otherwise used for special characters like \n odr \t. I had a look at the source where the homedir option is processed in wlapplication.cc. That happens quite early in
I think that means the following:
Well, that's what I read, but I can't tell if all these commands work as expected. There are some output messages using And as I already mentioned, the following works for an older build (after trying a bit, and maybe creating the folder manually):
Has anybody used that homedir option sucessfully with build 20? Is it possible to get those debugging messages somewhere? BTW the stdout.txt file of build8670 contains as second line Top Quote |
GunChleoc |
Posted at: 2019-05-09, 08:46
Changes since build8670 that possibly affect this:
I have created a bug report so that we can track this https://bugs.launchpad.net/widelands/+bug/1828355 Edited: 2019-05-09, 08:49
Busy indexing nil values Top Quote |
fuchur Topic Opener |
Posted at: 2019-05-09, 22:13
Thanks GunChleoc! I didn't create a bug report because I wasn't (and still am not) sure if the problem is on my side (PC, ...) or a general one. It seems the --homedir option isn't used much. But I'd say it's the best way to have several versions in parallel. Ok, now I tried to use the datadir option instead. Just out of curiosity. And this works with build 20. Is it difficult to set up a build environment for Windows? I don't need to create a full installer. It would be sufficient to be able to compile and link to widelands.exe. Then I could try add some more debug output and see if I can find what's wrong. I had a quick look at the corresponding wiki page (https://wl.widelands.org/wiki/BuildingWidelandsUnderWindowsNew/). Is that still valid for build20? When I look at the mentioned changes in Top Quote |
GunChleoc |
Posted at: 2019-05-10, 07:48
Yes, that page is still valid for Build 20. You can even use the The way that logging works is that the logger will write everything into We only use The reason that we do it like that is that one could install widelands into the Program Files and play without needing administrator privileges. Busy indexing nil values Top Quote |
fuchur Topic Opener |
Posted at: 2019-05-10, 21:01
Ok, thanks a lot, I'm about to try to build widelands. Installing Msys2, the toolchain and packages was no problem. Then I didn't use the bzr command but copied the source directory I already downloaded as .bzip file (and of course extracted it) somewhere. But then the configuration of cmake resulted in errors.
There were a lot of them, concerning always the same function but with a different call stack. The function in WLfunctions.cmake looks the following:
Should I try to clone the repository using bzr? And if yes, how do get build20 instead of trunk? I tried to call ninja afterwards, but it complained about the missing build.ninja. I guess that was not created because of the cmake errors. Update: Now I used bzr and downloaded trunk. But the same cmake errors appear. Edited: 2019-05-11, 09:41
Top Quote |
GunChleoc |
Posted at: 2019-05-11, 11:42
You will need to downgrade boost - CMake does not have a rule for detecting Boost version 1.70 yet. Yes, the error messages for this suck and are totally non-obvious, but I didn't find a way to make them better.
Do not mix your downloaded zip with the bzr command, that can leave you with a state that doesn't match the branch and also makes it more difficult for us to help you if you should end up in an unexpected state. To get the Build 20 branch:
Launchpad displays these commands for every branch, see https://code.launchpad.net/~widelands-dev/widelands/build20 Busy indexing nil values Top Quote |