From leaf at real-time.com Thu Jan 2 01:43:11 2020 From: leaf at real-time.com (Rick Tanner) Date: Thu, 2 Jan 2020 07:43:11 +0000 Subject: [crossfire] Fwd: Accepted crossfire-client 1.74.0-1 (source) into unstable In-Reply-To: References: Message-ID: <7b41c890-f908-a2d8-ee07-dc27aba78286@real-time.com> FYI Version 1.74.0 of the GTKv2 Client is about to make it in to the Debian code repository and soon after that Ubuntu, Mint, et al. repo. I am not sure the status for other distributions. -------- Forwarded Message -------- Subject: Accepted crossfire-client 1.74.0-1 (source) into unstable Date: Wed, 01 Jan 2020 14:49:03 +0000 From: Kari Pahula To: debian-devel-changes at lists.debian.org Format: 1.8 Date: Wed, 01 Jan 2020 16:25:57 +0200 Source: crossfire-client Architecture: source Version: 1.74.0-1 Distribution: unstable Urgency: medium Maintainer: Kari Pahula Changed-By: Kari Pahula Changes: crossfire-client (1.74.0-1) unstable; urgency=medium . * New upstream release * Standards-Version 4.4.1 and dh compat 12 - Switch debian/rules to dh * Rename debian/NEWS.Debian -> debian/NEWS Checksums-Sha1: 1cb470b5ad47d50511f19a88d999577329b9cb12 1967 crossfire-client_1.74.0-1.dsc 9b40f1b1202b9fb7b08765a0f86bbbd3febb10f4 819251 crossfire-client_1.74.0.orig.tar.bz2 4324c6be181a2695c53a07b110110856d2c996d8 9284 crossfire-client_1.74.0-1.debian.tar.xz 3e16f1a02e91b3d1c3bc7d66684c80b852695299 15098 crossfire-client_1.74.0-1_source.buildinfo Checksums-Sha256: 0d55658d739820e0ab1545a65579e4e773cd4869e7884ec213068ca5811a6d8b 1967 crossfire-client_1.74.0-1.dsc 8a9b215e6f4d6e1c42dea7fc6abb8ea54fbb52eead0c3c3c2f64da6d09af79e1 819251 crossfire-client_1.74.0.orig.tar.bz2 37833cb52659affab24b69db9cda00c7ab3712cb2d0328550cf27554dda04e58 9284 crossfire-client_1.74.0-1.debian.tar.xz acf4d1e016cdcc3a1a85d63a08d778009044fb6ec8753a5cfde0e1fc3a4fd89e 15098 crossfire-client_1.74.0-1_source.buildinfo Files: 9cbe7fcd9783ab65ef300a80e3fe838e 1967 games optional crossfire-client_1.74.0-1.dsc 244e507793178a54c1e0c576a2699ef7 819251 games optional crossfire-client_1.74.0.orig.tar.bz2 8534ad0e49354bbd73512646471b765b 9284 games optional crossfire-client_1.74.0-1.debian.tar.xz 4a8e6ce7b4648945f8f3b165b973713c 15098 games optional crossfire-client_1.74.0-1_source.buildinfo -- Rick Tanner | Phone : (952) 943-8700 http://www.real-time.com | Fax : (952) 943-8500 From nkipps at gmail.com Sun Jan 5 12:47:06 2020 From: nkipps at gmail.com (Nathaniel Kipps) Date: Sun, 5 Jan 2020 13:47:06 -0500 Subject: [crossfire] Trouble building Windows client Message-ID: Hi all, I've recently been attempting to get the Windows client built, and have been having a number of issues. Thanks to the instructions at http://xob.kapsi.fi/~makegho/trash/crossfire-win32.txt, and the generous help of the folks in IRC, I am finally able to build a client that works, but has one remaining flaw. When the built client is run in it's own development environment, everything is fine. But, when I pull the binaries, DLLs, and supporting files out into another environment, such as a test machine, the Preferences window no longer opens. There's no error, or message in the console, no indication of problems, just that the dialog does not actually appear. If anyone has any input, that would be much appreciated. Also, if anyone wants to try it for themselves, feel free to grab a rolled up package here: https://drive.google.com/open?id=14ej1Hw37mxABcd60ZD7ULL5AKNmelTU_ --DraugTheWhopper From kevinz5000 at gmail.com Mon Jan 6 06:41:23 2020 From: kevinz5000 at gmail.com (Kevin Zheng) Date: Mon, 6 Jan 2020 21:41:23 +0900 Subject: [crossfire] Trouble building Windows client In-Reply-To: References: Message-ID: Hi Nathaniel, On 1/6/20 3:47 AM, Nathaniel Kipps wrote: > When the built client is run in it's own development environment, > everything is fine. But, when I pull the binaries, DLLs, and > supporting files out into another environment, such as a test machine, > the Preferences window no longer opens. There's no error, or message > in the console, no indication of problems, just that the dialog does > not actually appear. > > If anyone has any input, that would be much appreciated. Also, if > anyone wants to try it for themselves, feel free to grab a rolled up > package here: https://drive.google.com/open?id=14ej1Hw37mxABcd60ZD7ULL5AKNmelTU_ Rick has reported a similar issue, and I remember experiencing it before as well. There's no doubt there's a real issue somewhere. Unfortunately, it will be some time before I get around to getting my Windows build set up again. In the meantime, could you try re-building with debugging symbols and getting a backtrace from the crash? -- Kevin Zheng kevinz5000 at gmail.com | kevinz at berkeley.edu XMPP: kevinz at eecs.berkeley.edu From nkipps at gmail.com Mon Jan 6 17:40:24 2020 From: nkipps at gmail.com (Nathaniel Kipps) Date: Mon, 6 Jan 2020 18:40:24 -0500 Subject: [crossfire] Trouble building Windows client In-Reply-To: References: Message-ID: Hi Kevin, > On Mon, Jan 6, 2020 at 7:41 AM Kevin Zheng wrote: > There's no doubt there's a real issue somewhere. I find it most interesting that the issue only manifests once I remove the binaries from the build environment, and execute them elsewhere. This indicates to me that I'm missing something simple, and that it's not just a regular bug. > try re-building with debugging symbols Some quick googling shows that this may be as simple as setting "CMAKE_BUILD_TYPE" to equal "Debug". Shouldn't be to hard to try. > getting a backtrace from the crash Since the client doesn't actually crash, just behaves anomalously, is there an alternate way to get a backtrace? Perhaps some function in windbg that may help? --DraugTheWhopper From leaf at real-time.com Wed Jan 8 01:02:34 2020 From: leaf at real-time.com (Rick Tanner) Date: Wed, 8 Jan 2020 07:02:34 +0000 Subject: [crossfire] Fwd: Accepted crossfire-client 1.74.0-1 (source) into unstable In-Reply-To: <7b41c890-f908-a2d8-ee07-dc27aba78286@real-time.com> References: <7b41c890-f908-a2d8-ee07-dc27aba78286@real-time.com> Message-ID: FYI -------- Forwarded Message -------- Subject: crossfire-client 1.74.0-1 MIGRATED to testing Date: Wed, 08 Jan 2020 04:39:17 +0000 From: Debian testing watch FYI: The status of the crossfire-client source package in Debian's testing distribution has changed. Previous version: 1.73.0-1 Current version: 1.74.0-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information From kevinz5000 at gmail.com Tue Jan 14 14:35:25 2020 From: kevinz5000 at gmail.com (Kevin Zheng) Date: Tue, 14 Jan 2020 12:35:25 -0800 Subject: [crossfire] Trouble building Windows client In-Reply-To: References: Message-ID: <2abd6b6d-9571-2c64-1414-9694081920b8@gmail.com> On 1/6/20 3:40 PM, Nathaniel Kipps wrote: > I find it most interesting that the issue only manifests once I remove > the binaries from the build environment, and execute them elsewhere. > This indicates to me that I'm missing something simple, and that it's > not just a regular bug. That is an interesting observation that I didn't realize before. >> try re-building with debugging symbols > > Some quick googling shows that this may be as simple as setting > "CMAKE_BUILD_TYPE" to equal "Debug". Shouldn't be to hard to try. That should be right. >> getting a backtrace from the crash > > Since the client doesn't actually crash, just behaves anomalously, is > there an alternate way to get a backtrace? Perhaps some function in > windbg that may help? This, I don't know. What compiler did you use? If you used MinGW's gcc, then gdb should be available as well. Regards, Kevin -- Kevin Zheng kevinz5000 at gmail.com | kevinz at berkeley.edu XMPP: kevinz at eecs.berkeley.edu From nkipps at gmail.com Thu Jan 16 22:39:49 2020 From: nkipps at gmail.com (Nathaniel Kipps) Date: Thu, 16 Jan 2020 23:39:49 -0500 Subject: [crossfire] Trouble building Windows client In-Reply-To: <2abd6b6d-9571-2c64-1414-9694081920b8@gmail.com> References: <2abd6b6d-9571-2c64-1414-9694081920b8@gmail.com> Message-ID: In a bizarre twist, a debug build makes the issue vanish. I simply cannot reproduce it once the CMAKE build type is set to "Debug". For the adventurous, a copy of the debug build can be found here: https://drive.google.com/file/d/1QobJhgkMLkBtq4uYhU8G72B2PEbWxYRR/ > This, I don't know. What compiler did you use? If you used MinGW's gcc, > then gdb should be available as well. I do use gcc, or at least, whatever comes with MinGW. --DraugTheWhopper From kevinz5000 at gmail.com Tue Jan 21 18:21:41 2020 From: kevinz5000 at gmail.com (Kevin Zheng) Date: Tue, 21 Jan 2020 16:21:41 -0800 Subject: [crossfire] Trouble building Windows client In-Reply-To: References: <2abd6b6d-9571-2c64-1414-9694081920b8@gmail.com> Message-ID: <51994eb3-900d-6f91-6699-b0930bc9a7f5@gmail.com> On 1/16/20 8:39 PM, Nathaniel Kipps wrote: > In a bizarre twist, a debug build makes the issue vanish. I simply > cannot reproduce it once the CMAKE build type is set to "Debug". For > the adventurous, a copy of the debug build can be found here: > https://drive.google.com/file/d/1QobJhgkMLkBtq4uYhU8G72B2PEbWxYRR/ That's interesting. That means there's definitely a bug somewhere. In the meantime, we can work around by providing a debug build! -- Kevin Zheng kevinz5000 at gmail.com | kevinz at berkeley.edu XMPP: kevinz at eecs.berkeley.edu From nkipps at gmail.com Tue Jan 21 19:09:00 2020 From: nkipps at gmail.com (Nathaniel Kipps) Date: Tue, 21 Jan 2020 20:09:00 -0500 Subject: [crossfire] Trouble building Windows client In-Reply-To: <51994eb3-900d-6f91-6699-b0930bc9a7f5@gmail.com> References: <2abd6b6d-9571-2c64-1414-9694081920b8@gmail.com> <51994eb3-900d-6f91-6699-b0930bc9a7f5@gmail.com> Message-ID: On Tue, Jan 21, 2020 at 7:21 PM Kevin Zheng wrote: > > That's interesting. That means there's definitely a bug somewhere. In > the meantime, we can work around by providing a debug build! > Are there any "partial debug" options I should try (since I notice a little stuttering with the main debug build)? Any guidance on how it should be packaged for an "impromptu" release? I suppose a zipfile is much easier to build than a full installer package. --DraugTheWhopper From kevinz5000 at gmail.com Tue Jan 21 19:12:52 2020 From: kevinz5000 at gmail.com (Kevin Zheng) Date: Tue, 21 Jan 2020 17:12:52 -0800 Subject: [crossfire] Trouble building Windows client In-Reply-To: References: <2abd6b6d-9571-2c64-1414-9694081920b8@gmail.com> <51994eb3-900d-6f91-6699-b0930bc9a7f5@gmail.com> Message-ID: <592fddd0-d574-2448-5a34-47ffb384e47a@gmail.com> On 1/21/20 5:09 PM, Nathaniel Kipps wrote: > On Tue, Jan 21, 2020 at 7:21 PM Kevin Zheng wrote: >> >> That's interesting. That means there's definitely a bug somewhere. In >> the meantime, we can work around by providing a debug build! >> > > Are there any "partial debug" options I should try (since I notice a > little stuttering with the main debug build)? Build "RelWithDebInfo" in CMake. Make sure to make clean. > Any guidance on how it should be packaged for an "impromptu" release? > I suppose a zipfile is much easier to build than a full installer > package. A zip file with the binary and the runtime files is fine, like the previous release. -- Kevin Zheng kevinz5000 at gmail.com | kevinz at berkeley.edu XMPP: kevinz at eecs.berkeley.edu From nkipps at gmail.com Tue Jan 21 23:06:16 2020 From: nkipps at gmail.com (Nathaniel Kipps) Date: Wed, 22 Jan 2020 00:06:16 -0500 Subject: [crossfire] Trouble building Windows client In-Reply-To: <592fddd0-d574-2448-5a34-47ffb384e47a@gmail.com> References: <2abd6b6d-9571-2c64-1414-9694081920b8@gmail.com> <51994eb3-900d-6f91-6699-b0930bc9a7f5@gmail.com> <592fddd0-d574-2448-5a34-47ffb384e47a@gmail.com> Message-ID: On Tue, Jan 21, 2020 at 8:12 PM Kevin Zheng wrote: > > Are there any "partial debug" options I should try (since I notice a > > little stuttering with the main debug build)? > > Build "RelWithDebInfo" in CMake. Make sure to make clean. The build is here, for those who wish to try it: https://drive.google.com/file/d/1mmFb1zpB3OaWKXlwtJwd4YXY5ca41j4L/view It seems to have correct behavior with the Preferences window. I will do more tests to see if any other issues are apparent. On a side note, has anyone devised any clever ways to do benchmark tests of the client's rendering speed, or full end-to-end latency testing of client-to-server communication? I think such was once talked about on IRC, but it was some months ago. --DraugTheWhopper From kevinz5000 at gmail.com Tue Jan 21 23:53:20 2020 From: kevinz5000 at gmail.com (Kevin Zheng) Date: Tue, 21 Jan 2020 21:53:20 -0800 Subject: [crossfire] Trouble building Windows client In-Reply-To: References: <2abd6b6d-9571-2c64-1414-9694081920b8@gmail.com> <51994eb3-900d-6f91-6699-b0930bc9a7f5@gmail.com> <592fddd0-d574-2448-5a34-47ffb384e47a@gmail.com> Message-ID: On 1/21/20 9:06 PM, Nathaniel Kipps wrote: > On a side note, has anyone devised any clever ways to do benchmark > tests of the client's rendering speed, or full end-to-end latency > testing of client-to-server communication? I think such was once > talked about on IRC, but it was some months ago. Nothing clever, but there is now: --profile-latency Log command acknowledgement latency to stdout --profile-redraw Print map redraw times to stdout This was used to measure the major server latency improvement committed not too long ago. -- Kevin Zheng kevinz5000 at gmail.com | kevinz at berkeley.edu XMPP: kevinz at eecs.berkeley.edu