We are planning to use Git to detect the current version of Tenacity, instead
of depending on a hardcoded variable, as that is an approach that is far from
foolproof. We already depended on it for Windows and macOS builds, as vcpkg
uses Git to fetch a couple of dependencies. The vcpkg has also been
appropriately adjusted and cleaned up.
It may seem a bit excessive, but the operating systems we support all have
a version of Git that is available and it is not a runtime dependency. We
assume that people who can gain access to the source code can also install
a copy of Git. If we actually come across some sort of an extreme edge case
where this is not true, we can set the versions to `9999` just like in
`win/tenacity.rc`, in order to ensure portability, at a later point in time.
This change is a measure that will ensure that we are going to avoid mistakes
that we will not be able to undo later.
Signed-off-by: Panagiotis Vasilopoulos <hello@alwayslivid.com>
Doesn't change anything functionality-wise for now, particularly because of
my hesitation with this change as far as hard-coding the version again as a
fallback is concerned.
Audacity's version variable was also reverted in contrast to
56c953a14d for compatibility reasons with older
project files or for project file compatibility with newer versions of
Audacity.
Signed-off-by: Panagiotis Vasilopoulos <hello@alwayslivid.com>
The VST plugin done via GTK for non-apple & non-windows pulls
<gdk/gdkx.h>, which is specific to X11 and thus isn't available in a
pure-wayland system.
Reference-to: https://github.com/tenacityteam/tenacity/pull/620
This commit contains a workaround for git describe command using only
annotated tags and not all tags known to repository when generating its
output. Adding such parameter to git command line should change its
behavior to more proper one.
Signed-off-by: Juozas <juozaspo@gmail.com>
Reference-to: https://github.com/tenacityteam/tenacity/pull/586
Wrote down some unspoken rules, such as the waiting times before a maintainer
is supposed to merge a change, and added some exceptions to those said rules
that make the development process of Tenacity more tedious and unproductive.
The said exceptions concern documentation-related changes.
Signed-off-by: Panagiotis Vasilopoulos <hello@alwayslivid.com>
Reference-to: https://github.com/tenacityteam/tenacity/pull/627
The VST plugin done via GTK for non-apple & non-windows pulls <gdk/gdkx.h>,
which is specific to X11 and thus isn't available in a pure-wayland system.
This disables it automatically.
Closes: https://github.com/tenacityteam/tenacity/issues/614
Signed-off-by: Haelwenn (lanodan) Monnier <contact@hacktivis.me>
Stop setting it globally and make it wxwidgets build specific
Use CMAKE_OSX_DEPLOYMENT_TARGET instead of the env var name
Signed-off-by: Emily Mabrey <emabrey@tenacityaudio.org>
Package writing was not working correctly due to permissions misconfiguration
Change NuGet cache writing scenarios
Always write to NuGet cache when building within a tenacityteam repository
Signed-off-by: Emily Mabrey <emabrey@tenacityaudio.org>
Skip duplicate CI runs with the same content
Skip concurrent CI runs of the same content
Cancel old CI runs when a newer commit is pushed on top of a branch
Skip CI builds which change documentation and non-build related config files
Signed-off-by: Emily Mabrey <emabrey@tenacityaudio.org>
This is consistent with the BUILDING.md documentation.
Doing redundant Windows builds wastes resources. GitHub Actions
gives us 20 concurrent jobs but adding 2 unnecessary jobs to every
push will push us to that limit more often.
Signed-off-by: Be <be@mixxx.org>
Signed-off-by: Panagiotis Vasilopoulos <hello@alwayslivid.com>
Modify `cmake_build.yml` to populate Github Packages Nuget cache via CI builds
Modify `CMakeLists.txt` to read from Github Packages Nuget cache during builds
Add `nuget.config` to enable nuget cache for contributors without configuration
Signed-off-by: Emily Mabrey <emabrey@tenacityaudio.org>
There were two problems:
1. The vamp-sdk vcpkg port added a `d` suffix for debug builds
that upstream did not.
2. The vamp-sdk vcpkg port used the same file name for libraries
on every OS but that is not what upstream does.
Signed-off-by: Be <be@mixxx.org>
wxWidgets 3.1 can be explicitly selected by setting the WX_CONFIG
environment variable.
Signed-off-by: Be <be@mixxx.org>
Signed-off-by: Mart Raudsepp <leio@gentoo.org>
wxWidgets 3.0 doesn't support context in wxGetTranslation yet, so don't
use the context, similar to existing DoChooseFormat handling.
This will lead to some untranslated strings or wrong context translations
(if we have equal strings that one specifies the context, but the other
doesn't), which isn't great, but better than not being able to compile
the application at all against a stable wxWidgets library version.
Signed-off-by: Mart Raudsepp <leio@gentoo.org>
