[ISSUE] can't start warsow

[ISSUE] can't start warsow

[curiousjunior]

[-- Attachment #1: Type: text/plain, Size: 241 bytes --]

New issue by curiousjunior on void-packages repository

https://github.com/void-linux/void-packages/issues/35822

Description:
![image](https://user-images.githubusercontent.com/79333625/155435326-40502e7e-a2bd-41c5-b64c-f094dae5012e.png)

Re: can't start warsow

[Anachron]

[-- Attachment #1: Type: text/plain, Size: 199 bytes --]

New comment by Anachron on void-packages repository

https://github.com/void-linux/void-packages/issues/35822#issuecomment-1049464695

Comment:
Whats printed in the console if you run it from there?

Re: can't start warsow

[curiousjunior]

[-- Attachment #1: Type: text/plain, Size: 612 bytes --]

New comment by curiousjunior on void-packages repository

https://github.com/void-linux/void-packages/issues/35822#issuecomment-1049469189

Comment:
literally nothing, qfusion doesn't print anything to standard output unless you patch its source code so that it prints to stdout/stderr everything it prints to the in-game console, I forgot which function is responsible for that, I guess it's one of `Com_DPrintf`, `Com_Printf` or `Q_snprintfz`, I know it'll print useful output because I had to deal with that when I ported this game to *bsd, it's just I no longer have computer which can compile c++ code fast

Re: can't start warsow

[curiousjunior]

[-- Attachment #1: Type: text/plain, Size: 349 bytes --]

New comment by curiousjunior on void-packages repository

https://github.com/void-linux/void-packages/issues/35822#issuecomment-1049471251

Comment:
alternative solution is to statically link *.so files it produces, I have a patch for that https://github.com/TeamForbiddenLLC/warfork-qfusion/pull/22/commits/3bc0880b4a1e9df74ee5a24b0fbe5ff8db475eba

Re: can't start warsow

[curiousjunior]

[-- Attachment #1: Type: text/plain, Size: 303 bytes --]

New comment by curiousjunior on void-packages repository

https://github.com/void-linux/void-packages/issues/35822#issuecomment-1049475100

Comment:
I forgot to mention that patch doesn't touch `snd_qf` because I removed that module before I made that patch, to get rid of `snd_qf` you need this patch:

Re: can't start warsow

[curiousjunior]

[-- Attachment #1: Type: text/plain, Size: 1489 bytes --]

New comment by curiousjunior on void-packages repository

https://github.com/void-linux/void-packages/issues/35822#issuecomment-1049475100

Comment:
I forgot to mention that patch doesn't touch `snd_qf` because I removed that module before I made that patch, to get rid of `snd_qf` you need this patch:
```
diff --git a/source/CMakeLists.txt b/source/CMakeLists.txt
index 48e37dd094..7c24451bda 100644
--- a/source/CMakeLists.txt
+++ b/source/CMakeLists.txt
@@ -228,7 +228,6 @@ if (NOT GAME_MODULES_ONLY)
     add_subdirectory(irc)
     add_subdirectory(ref_gl)
     add_subdirectory(snd_openal)
-    add_subdirectory(snd_qf)
     add_subdirectory(ui)
     add_subdirectory(steamlib)
     add_subdirectory(server)
diff --git a/source/client/CMakeLists.txt b/source/client/CMakeLists.txt
index 249add1643..daaa242024 100644
--- a/source/client/CMakeLists.txt
+++ b/source/client/CMakeLists.txt
@@ -197,7 +197,7 @@ else()
 endif()
 
 add_executable(${QFUSION_CLIENT_NAME} ${CLIENT_BINARY_TYPE} ${CLIENT_HEADERS} ${CLIENT_PLATFORM_HEADERS} ${CLIENT_COMMON_SOURCES} ${CLIENT_PLATFORM_SOURCES} ${BUNDLE_RESOURCES})
-add_dependencies(${QFUSION_CLIENT_NAME} angelwrap cgame cin ftlib game irc ref_gl snd_openal snd_qf steamlib ui)
+add_dependencies(${QFUSION_CLIENT_NAME} angelwrap cgame cin ftlib game irc ref_gl snd_openal steamlib ui)
 
 if (APPLE)
     set_target_properties(${QFUSION_CLIENT_NAME} PROPERTIES MACOSX_BUNDLE_INFO_PLIST ${QFUSION_MAC_INFO_PLIST})
```

Re: can't start warsow

[curiousjunior]

[-- Attachment #1: Type: text/plain, Size: 884 bytes --]

New comment by curiousjunior on void-packages repository

https://github.com/void-linux/void-packages/issues/35822#issuecomment-1049482301

Comment:
I'm sure this error is caused by unnecessary dynamic loading, that's why I'm proposing a patch that just statically links everything except `game` and `cgame` which are built in `modules_21.pk3` from `warsow-data`, the `libcgame_x86_64.so` and `libgame_x86_64.so` you install from `warsow` are loaded only if you disable "pure checks" https://github.com/TeamForbiddenLLC/warfork-qfusion/pull/22/commits/a23c9b818029c390663a16d20528a1a8b368d259 which is useful if you either care about CPU archs beyond x86 or OSes beyond windows, macos and glibc linux or you simply want to add cheats to `cgame` (I did both actually), so if you don't apply a patch that removes "pure checks", warsow won't run on non-x86 archs and musl flavor of void

Re: can't start warsow

[curiousjunior]

[-- Attachment #1: Type: text/plain, Size: 425 bytes --]

New comment by curiousjunior on void-packages repository

https://github.com/void-linux/void-packages/issues/35822#issuecomment-1049487773

Comment:
I couldn't run warsow after statically linking `game` and `cgame` modules because they conflict in global variable naming and duplicating code with different variables and functions names is a tedious task, so I recommend leaving those two as is after disabling "pure checks"

Re: can't start warsow

[paper42]

[-- Attachment #1: Type: text/plain, Size: 178 bytes --]

New comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/issues/35822#issuecomment-1049944396

Comment:
Please fill out the issue template

Re: can't start warsow

[angrygay]

[-- Attachment #1: Type: text/plain, Size: 328 bytes --]

New comment by angrygay on void-packages repository

https://github.com/void-linux/void-packages/issues/35822#issuecomment-1073983870

Comment:
@paper42
```
$ xuname
Void 5.15.30_1 x86_64 GenuineIntel uptodate rrrmFFF
$ xbps-query -p pkgver warsow
warsow-2.1_2
$ xbps-query -p pkgver warsow-data
warsow-data-2.1.2_1
```

Re: can't start warsow

[github-actions]

[-- Attachment #1: Type: text/plain, Size: 293 bytes --]

New comment by github-actions[bot] on void-packages repository

https://github.com/void-linux/void-packages/issues/35822#issuecomment-1166172020

Comment:
Issues become stale 90 days after last activity and are closed 14 days after that.  If this issue is still relevant bump it or assign it.

Re: [ISSUE] [CLOSED] can't start warsow

[Duncaen]

[-- Attachment #1: Type: text/plain, Size: 236 bytes --]

Closed issue by ghost on void-packages repository

https://github.com/void-linux/void-packages/issues/35822

Description:
![image](https://user-images.githubusercontent.com/79333625/155435326-40502e7e-a2bd-41c5-b64c-f094dae5012e.png)

Re: can't start warsow

[ztx-lyghters]

[-- Attachment #1: Type: text/plain, Size: 223 bytes --]

New comment by ztx-lyghters on void-packages repository

https://github.com/void-linux/void-packages/issues/35822#issuecomment-1491244572

Comment:
This is still a problem, and yet the version from the site works perfectly