609
edits
FGCom-mumble: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 8: | Line 8: | ||
{{caution|The plugin relies on '''Mumble 1.4.0''' which is not yet released. | {{caution|The plugin relies on '''Mumble 1.4.0''' which is not yet released. | ||
To test FGCom-mumble, you thus need to self compile Mumble and Murmur. | |||
* '''Linux''': | |||
** I wrote a small guide on how to do that on Debian (Bullseye): https://github.com/hbeni/fgcom-mumble/wiki#compiling-mumble-140-plugin-branch-from-krzmbrzl-on-a-debian-testing-bullseye-system. | |||
** You may also try a binary build of that branch (mumble deps like QT must be installed manually): http://fgcom.hallinger.org/mumble-fgcom-test.tar.gz | |||
* '''Windows''': You can use a snapshot build. To access the current one, go to the branchs pull request page and scroll down. There you can click the "details" tab of the windows check and that leads you to the overview. In the middle you see a grey "View more details on Azure Pipelines" link that yields a "1 artifact produced" link to the EXE. }} | |||
{{note| This is currently in development and has no stable release for productive use yet. Expect lots of bugs! }} | {{note| This is currently in development and has no stable release for productive use yet. Expect lots of bugs! }} | ||