Topic: Appveyor broken

Furthermore it might be worth trying to remove the --nodeps command from line 22 in appveyor.yml as well

Top

Quote

This thread seems to be about missing dlls, while compiling on windows. Since that was my first error message, I'm posting it here.

I'm following BuildingWidelandsUnderWindowsNew from the top, git fork, with Debug installing into D: drive, so I had to change some path names. I did the path export, downgraded boost, cmake worked, ninja worked, tests worked. I put the path export into the .login file so I wouldn't have to repeat it everytime.

The first time I ran it, there were three popups about missing various dlls. The first one was for GLEW, so I repeated(?) the pacman for glew I didn't write down the other two.
Somewhere there was a complaint about missing data directory, so I created that.

The next time I ran it, using windows console to start mingw64 console first, I get this error from the calling console, no popups.

joelg@DESKTOP-1V4FGF6 MINGW64 ~/widelands/build/src
$ ./widelands.exe
This is Widelands Version r1[6118f81@Wide_jj_branch] (Debug)
Log output will be written to: C:\Users\joelg\.widelands\stdout.txt
terminate called after throwing an instance of 'LuaScriptNotExistingError'
  what():  [../src/scripting/lua_errors.cc:22] The script 'i18n\fonts.lua' was not found!

stdout.txt file shows this:
This is Widelands Version r1[6118f81@Wide_jj_branch] (Debug)
Set home directory: C:\Users\joelg\.widelands
Set configuration file: C:\Users\joelg\.widelands/config
Widelands executable directory: D:\msys64\home\joelg\widelands\build\src
Adding directory: D:\msys64\home\joelg\widelands\build\src\data
selected language: (system language)

I looked at src/scripting/lua_errors.cc but it doesn't seem to be a text file.
I searched for 'fonts' from build/src and didn't find any.

I searched for i18n and found 
build/src/base/CMakeFiles/base_i18n.dir/libbase_i18n.a
build/src/base/CMakeFiles/base_i18n.dir/i18n.cc


Update:  I repeated  cmake
 ~/widelands/build
$ cmake -G "Ninja" -DCMAKE_C_COMPILER=D:/msys64/mingw64/bin/gcc.exe -DCMAKE_CXX_COMPILER=D:/msys64/mingw64/bin/g++.exe -DCMAKE_BUILD_TYPE=Release -DOPTION_USE_GLBINDING=OFF -DOPTION_BUILD_WEBSITE_TOOLS=OFF -DOPTION_ASAN=OFF  -DOPTION_BUILD_TRANSLATIONS=OFF ..

and ninja,
the new error is slightly different.
 ~/widelands/build/src
$ ./widelands.exe
This is Widelands Version r1[6118f81@Wide_jj_branch] (Release)
Log output will be written to: C:\Users\joelg\.widelands\stdout.txt

Caught exception (of type '25LuaScriptNotExistingError') in outermost handler!
The exception said: [../src/scripting/lua_errors.cc:22] The script 'i18n\fonts.lua' was not found!

This should not happen. Please file a bug report on version r16118f81@Wide_jj_branch. and remember to specify your operating system.

Suggestions?

Top

Quote

Hi JJG,
the reason for the errors is exactly what Nordfriese describes. You can't run widelands.exe directly from the Build folder. But you don't need to run it from the msys console as well. Widelands can be run from any folder which contains the data directory from the build process (build process adds translations to the datadir) and all dll needed. this (collecting all needed files for the widelands folder) is exactly what is done on our Continous Integration environment on appveyor by utilisation of InnoSetup and the corresponding ISS Script located in /utils/win32/innosetup/.
For convenience I normally install a latest master build from appveyor and just copy my freshly build widelands.exe in this folder so I don't need to collect everything from scratch. As appveyor works pretty good building yourself is only necessary to test own chages to the code. For just playing and testing I prefer using the latest appveyor builds.
for your MSYS2 environment downgrading boost is currently not necessary if you use the -DBoost_NO_BOOST_CMAKE=ON option on cmake. I didn't have the time to update the wiki yet. However looking into the appveyor.yml is always good to see the currently working cmake options.

Top

Quote

Hi JJG,
As you have seen on windows widelands needs a lot of dll if compiled with dynamic linking. From our installer provided on appveyor these dll are copied to the widelands folder as well as the data dir is copied to that folder.
Innosetup is a tool to compile a selfextracting installer.exe which is the artifact that is provided on Appveyor after a successful build. If you run this installer all the files collected there will be written to a specified widelands folder plus some links will be created.
Innosetup needs a file which tells it what files to collect into this installer.exe. This is the content of this .iss script to be used by InnoSetup.

As you have figured out widelands is always using the same user folder to save games and maps and to write the stout.txt. This is located at <Username>/.widelands.

To get a normal runnable windows installation (instead of running it out of MSYS) I normally go to the appveyor summary page https://ci.appveyor.com/project/widelands-dev/widelands/history and pick the latest master branch (you need to check the little grey font to get the correct one) then choose a build (x64 or x86, release or debug) and click on artifacts tab. there you can find the installer. After installing this into a new folder I copy my selfcompiled widelands.exe to that folder to test it. (if you have changed something in the data folder you should copy that as well or you can use the datadir option to run with a different datadir.

Anyhow if you have any specific questions don't hesitate to ask. We are always glad to see new devs on the project and try to support them best we can.
BTW: I updated the Build under Windows page yesterday

Top

Quote