VS does generate its own internal manifest file, but since we're using cmake now instead of proper VS projectfiles
we don't have the ability to just tick a box to enable HDPI support (or any other change we want). There are ways
to merge manifest files (mt.exe) which might be preferable to this, but I can't figure out how to use them.
* Convert server_base class to use coroutine instead of handlers
* Rework wesnothd's client login to use coroutine
* Merge 3 player handling functions into a single coroutine
* update cmakelists too
* Implement send_doc_queued in terms of coroutine
* Use brace initialization for making asio buffers
* Implement campaignd's request handling in coroutine
* Brace-initialize entire vector
* Remove old handler based send/receive helpers
* Document coroutine send/receive helpers
* Made coro_send_doc() helper take wml doc by reference
In most cases there is no need to rely on shared pointers to ensure
object lifetime if using coroutines since even when coroutine is
suspended args are still kept alive by its context.
* Document coro_send_file()
* Silence deprecation warning to fix build on earlier versions of boost
* Explicitly check for boost.context to allow linking against static boost libs
* Add boost.coroutine to flatpak manifest
* Port winapi TransmitFile codepath to coroutines
* Exception safety fix
* Add boost.scope_exit to vcpkg
* Fix build with pre-1.66 boost
* Move coro_* helpers into server_base class
Those helpers were in .ipp solely because they were templated on handler
types, this is no longer true after coroutine based rework.
* Make server_base::coro_send_file non-inline
* CleanUp Xcode project
Co-authored-by: Martin Hrubý (hrubymar10) <hrubymar10@gmail.com>
This whole textdomain is dedicated to localized strings revolving around the
game's AI engine and the AI demos/test scenarios, with around 370 strings in
it.
Other than a few strings near the start of the catalogue template, none of these
have any value for regular players since they are sourced from AI demos and
test scenarios in data/ai/micro_ais/ and data/ai/scenarios/. None of them will
be displayed to people who aren't tinkering with WML or contributing to AI
development as part of the Wesnoth dev team, and some of the language used in
them is very technical in nature.
This commit leaves the "#textdomain wesnoth-ai" lines in the AI demos, but
drops the .po and .pot catalogues for wesnoth-ai. The few strings that are
seen by regular players move to the wesnoth-lib textdomain.
Currently both on jenkins and locally building Wesnoth's flatpak gives the warning:
scons: warning: parallel builds are unsupported by this version of Python;
ignoring -j or num_jobs option.
This is apparently due to an issue between scons 3.0.1 and python 3.7+, which was reported at https://github.com/SCons/scons/issues/3145, fixed in https://github.com/SCons/scons/pull/3150, and is therefore first included in scons 3.0.2.
This Address is not shown in the store. It's used to contact us in case of
issues or upstream changes regarding this file.
In the past it has been used for a mass email by hughsie, an developer for
appstream related things.
[ci skip]
One must compile wesnoth with -DLOCALEDIR=/usr/share/locale, as that's the place
where the system looks for translations.
(One can test it with gettext -s -d wesnoth "poisoned")
This is according to the docs, needs more testing if it works.
Doesn't work with Arch, though Arch doesn't support software centres well.
[ci skip]
(cherry-picked from commit 60f2158dfaa88eca47e4f2bdb0a4a64f28db8ba1)
They are as well used in the software centre.
Having keywords is a bonus, even if they are not matched.
[ci skip]
(cherry-picked from commit 76e7c8d19f8626dca5edd33b8c66ef3a0385f93f)
So it may not be saved in ~/.xession-errors
or cluttering up disk space another way
(cherry-picked from commit c998f13a4526d89840b3bf7e36e6a4ffd57d7c80)
