Topic: Windows 32bit builds

Tino Topic Opener Joined: 2009-02-20, 16:05 Posts: 252 Tribe Member Location: Somewhere in Germany...	Posted at: 2016-02-03, 17:07 Hey, i've managed to let Appveyor build 32bit binaries: https://ci.appveyor.com/project/widelands-dev/widelands/build/debug_builds-416/job/9sg16c3drrc2fc5p/artifacts I can run it fine on my Win7-64bit system, perhaps some users can test this build on native 32bit windows versions... Top Quote

GunChleoc Joined: 2013-10-07, 14:56 Posts: 3324 One Elder of Players Location: RenderedRect	Posted at: 2016-02-03, 20:32 This is excellent news indeed Busy indexing nil values Top Quote

kaputtnik Joined: 2013-02-18, 19:48 Posts: 2439 OS: Archlinux Version: current master One Elder of Players Location: Germany	Posted at: 2016-02-13, 10:08 I don't understand this appveyor thing Is the one artifact in appveyor always build from current trunk? Shouldn't we provide a link and some explanation in the Downloads/unofficial-development-builds-section? Fight simulator for Widelands: https://wide-fighter.netlify.app/ Top Quote

GunChleoc Joined: 2013-10-07, 14:56 Posts: 3324 One Elder of Players Location: RenderedRect	Posted at: 2016-02-13, 10:48 I agree it's a bit convoluted to access them - some form of permalink to master would be nice. What I do is go on the history, look for the last successful build of the branch that I want, then go on artifacts and pick my operating system and build type. Edited: 2016-02-13, 10:49 Busy indexing nil values Top Quote

kaputtnik Joined: 2013-02-18, 19:48 Posts: 2439 OS: Archlinux Version: current master One Elder of Players Location: Germany	Posted at: 2016-02-13, 11:22 Ok, now i have installed this build Widelands could not be installed to the predefined folder "c:\Program Files\Widelands" because the permission is denied. So one has to install it in the User forlder. The virus schield (avira here) checks the files libglbinding and libcc after starting widelands (no warining of course). Widelands itself is affected with the bug Text not displayd correct Thats all of my observations (want to quit windows as sson as possible, i don't like it anymore). If you have some specific questions, feel free to ask Edit: It was not possible for me to get the revision of the build. Somewhere i found something like "Widelands Version 0.19.0.1" Edited: 2016-02-13, 11:34 Fight simulator for Widelands: https://wide-fighter.netlify.app/ Top Quote

Tino Topic Opener Joined: 2009-02-20, 16:05 Posts: 252 Tribe Member Location: Somewhere in Germany...	Posted at: 2016-02-13, 12:28 The widelands windows clearly states exactly the version, e.g. "widelands_dev_widelands_bug_1395278_scripting_Relase_x86(Debug). This allows exactly to determine which appveyor job this was (525), from which branch (bug_1395278_scripting) and this can be further broken down to git branch,checkin and bzr commit... The naming on Appveyor is definitely not final. It is still a work in progress I will defenitely put a link from our download section to Appveyor. But it seems it does not provide a permanent link to "most recent artifact". Appveyor just has been working for a few days... These builds are not for "playing", but rather for testing! I am not sure, if there should be much advertising, we want the "normal" users to play releases, not constantly changing dev builds... I've recently removed the requirement for "Administrative privileges" from the Windows installer, because it is not necessary and i want to allow User with non elevated system privileges to install Widelands at all. If your user is not allowed to install into "C:\Program Files" but your Windows still advertises it as default location (the installer just grabs this from your system), there are two workarounds: Install to a different directory or run the installer with a right click -> Run as administrator. I've not figured out if there is a way in Innosetup to ask for elevated privileges during install. Top Quote

PeterPiper Joined: 2015-01-25, 20:44 Posts: 29 Pry about Widelands Location: Hannover Germany	Posted at: 2016-02-14, 00:30 Hi. Thanks for the 32 bit. After the installation I get "Der Prozedureinspringpunkt '_putenv_s' wurde in der DLL 'msvcrt.dll' nicht gefunden." My best tranlation is "The procedure jump_to point '_putenv_s' wan not found in the DLL 'msvcrt.dll'. Peter Top Quote

Tino Topic Opener Joined: 2009-02-20, 16:05 Posts: 252 Tribe Member Location: Somewhere in Germany...	Posted at: 2016-02-14, 09:28 Hi, yeah, that is known problem with Windows XP which has reached its end of lifecycle nearly two years ago[1]. I won't get again into the discussion why it is not advisable to use it any more (search this forum) and we won't do any builds running on XP any more, sorry. [1] http://windows.microsoft.com/de-de/windows/lifecycle Top Quote

PeterPiper Joined: 2015-01-25, 20:44 Posts: 29 Pry about Widelands Location: Hannover Germany	Posted at: 2016-02-14, 20:51 ok, thanks anyway Top Quote