New freeciv master msys2 build from sources of 19-Apr-20 (3.0.92-dev-200419), commit '9bd7b9efb3', available at http://files.freeciv.org/packages/windo ... snapshots/
- Built against msys2 environment 200224
Msys2 based Windows Installer testing (freeciv-3.1 / msys2)
Re: Msys2 based Windows Installer testing (freeciv-3.1)
New freeciv master msys2 build from sources of 07-May-20 (3.0.92.1-dev-200507), commit '86c56eb57a', available at http://files.freeciv.org/packages/windo ... snapshots/
- Built against msys2 environment 200224
- Built against msys2 environment 200224
Re: Msys2 based Windows Installer testing (freeciv-3.1)
New freeciv master msys2 build from sources of 15-Jun-20 (3.0.92.1-dev-200615), commit 'edbe26097d', available at http://files.freeciv.org/packages/windo ... snapshots/
- Built against msys2 environment 200610
- Built against msys2 environment 200610
Re: Msys2 based Windows Installer testing (freeciv-3.1)
New freeciv master msys2 build from sources of 26-Jul-20 (3.0.92.1-dev-200726), commit '85459532aa', available at http://files.freeciv.org/packages/windo ... snapshots/
- Built against msys2 environment 200610
- Built against msys2 environment 200610
Re: Msys2 based Windows Installer testing (freeciv-3.1)
Possibly because of latest Windows updates, I'm having issues with any builds I make from master (curiously S3_0 builds seem unaffected). Windows defender blocks connection between the server and client and it doesn't even ask about it when client first tries to spawn the server. It only asks when the server is launched separately. Even then the permissions is given too late for that particular server instance. So one has to restart server and client after giving them permissions to network usage to actually use those permissions:
1. Launch server
2. When asked, give the server permission to use network
3. Relaunch server
4. Launch client and try to connect to the server ("Connect to Network Game")
5. When asked, give the client permission to user network
6. Relaunch client and connect to the server. This should now work.
7. Now that both server and client have required permissions, you should also be able to launch server from the client (e.g. "Start New Game")
1. Launch server
2. When asked, give the server permission to use network
3. Relaunch server
4. Launch client and try to connect to the server ("Connect to Network Game")
5. When asked, give the client permission to user network
6. Relaunch client and connect to the server. This should now work.
7. Now that both server and client have required permissions, you should also be able to launch server from the client (e.g. "Start New Game")
Re: Msys2 based Windows Installer testing (freeciv-3.1)
New freeciv master msys2 build from sources of 06-Oct-20 (3.0.92.1-dev-201006), commit 'c6000e1cad', available at http://files.freeciv.org/packages/windo ... snapshots/
- Built against msys2 environment 200906
- See earlier post about Windows Defender issue
- Built against msys2 environment 200906
- See earlier post about Windows Defender issue
Re: Msys2 based Windows Installer testing (freeciv-3.1)
New freeciv master msys2 build from sources of 04-Nov-20 (3.0.92.2-dev-201104), commit '5d75624c69', available at http://files.freeciv.org/packages/windo ... snapshots/
- Built against msys2 environment 200906
- See earlier post about Windows Defender issue
- Built against msys2 environment 200906
- See earlier post about Windows Defender issue
Re: Msys2 based Windows Installer testing (freeciv-3.1)
Microsoft software is a real mystery to me (and has always been so). My suspicions would be that MS test each new update against every known piece of community software and then write special code for each failure. In this case it is not just the S3_0 builds, but also existing software such as S2.6.x (since I have seen no problems). This is a long shot but would it be possible to contact MS about this?cazfi wrote:Possibly because of latest Windows updates, I'm having issues with any builds I make from master (curiously S3_0 builds seem unaffected). Windows defender blocks connection between the server and client and it doesn't even ask about it when client first tries to spawn the server. It only asks when the server is launched separately. Even then the permissions is given too late for that particular server instance. So one has to restart server and client after giving them permissions to network usage to actually use those permissions:
Re: Msys2 based Windows Installer testing (freeciv-3.1)
New freeciv master msys2 build from sources of 04-Dec-20 (3.0.92.3-dev-201204), commit '4b143e3c59', available at http://files.freeciv.org/packages/windo ... snapshots/
- Built against msys2 environment 200906
- See earlier post about Windows Defender issue
- Built against msys2 environment 200906
- See earlier post about Windows Defender issue
Re: Msys2 based Windows Installer testing (freeciv-3.1)
Now I again don't see Windows Defender issue. Maybe because some update, maybe because I already allowed earlier freeciv builds to function.