Add the ABI files generated by libabigail abidw tool (note that
--no-corpus-path --no-comp-dir-path options were used to avoid having
system-specific object file paths in these files and the source file
paths were edited to remove the system-specific prefix from them too)
and a script comparing the current ABI with these files.
Also update the documentation to describe using libabigail tools as
abi-compliance-checker doesn't seem to work under the recent systems any
longer: it gives some warnings and doesn't detect ABI-incompatible
changes.
Closes#22634.
We probably could change inc_release to do this too, but considering the
frequency of our minor (let alone major) releases, it doesn't seem to be
worth it.
And upgrade the submodule after performing the change documented here in
it to avoid link conflicts between the bundled zlib version and another
copy of zlib potentially used in the application due to the name clashes
between crc32_combine_xxx functions new in 1.2.12 that upstream forgot
to add to zconf.h.
Closes#22280.
Put steps in the chronological order.
Also put library-specific instructions in the same section, but in
different subsections instead of combining 2 of them in one section and
having a separate section for another one as before.
Using numbers prevented the headings from being interpreted as such and
we instead got numbered item followed by a horizontal separator when
rendering Markdown as HTML.
Just remove the numbers to fix this.
Remove the instructions for applying the cherry-picked commit on
docs.wxwidgets.org as it's not used any more.
These instructions are probably insufficiently detailed, but we'll
probably switch to using GitHub Actions for updating the documentation
soon, so they won't be necessary for much longer anyhow and it's not
worth expanding them.
Also don't duplicate this information in both how-to-add-new-sample.md
and how-to-add-files-to-build-system.md, just reference the former in
the latter instead.
Also fix some Markdown markup.
It may not be obvious how to build the tests, so add a section
explaining this to the existing file containing the instructions about
writing the tests and add a README to the tests directory itself to
increase chances that this file will be found -- hopefully anybody
interested in the tests will look at the README in the directory
containing them.
Note that this support is still incomplete, notably we don't have
*_vc17.sln files yet and the official build scripts haven't been updated
to build MSVS 2022 binaries neither.
As shown by the fact that no other platform-specific translations were
ever added since the initial version of locale/msw/it.po added way back
in 4d931bcca0 (Translate '&Help' to '&' for italian Windows only,
2005-08-12), this is not especially useful, so just handle this
particular case specially in wxGetStockLabel() and remove support for
platform-specific translations.
This allows to simplify the makefiles and the catalog loading code as
there is no need to deal with the files in subdirectories any more.
Warning about gettext versions earlier than 0.10.35 is pointless,
as even 0.10.35 is from 2001, and so old it isn't even available
on GNU mirrors anymore. We shall not recommend a specific version in
the first place.
The proper way to start a new translation is to use msginit to initialize
a .po file -- just copying the .pot leaves many fields to their default
values, which the translator would need to fill in manually (the
Plural-Forms: field in particular).
Also remove the part about updating version.bkl from the pre-release
section, as this is done after the release.
As this leaves only 2 items in the numbered list of the things to do,
remove the list entirely.
Document bakefile version needed and the commands for regenerating the
files generated by it.
Also update instructions for changing C:R:A values.
Closes https://github.com/wxWidgets/wxWidgets/pull/1838
This is now done automatically in the GitHub action of wxWidgets/website
repository.
Do mention that rebuilding the web site requires the release to be
available.
Mention that we use the legacy 0.2 bakefile branch.
Also use https://www.bakefile.org/ as Bakefile home page location.
Finally, use backticks around more files names, especially those
containing asterisks, that break Markdown syntax highlighting in Vim
otherwise.
