Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
Move towards packaging artifacts with xz, which offers higher compression ratios and faster decode time.
|
|
Drop python version from matrix configuration as it's always 3.11.
|
|
|
|
# Conflicts:
# indra/llrender/llgl.cpp
# indra/newview/lloutfitslist.cpp
|
|
* Enable CEF browser for Linux
* Disable the update for Linux, we don't have that one right now
* Update build_linux.yaml
We need libpulse-dev for volume_catcher Linux
* Add linux_volum_catcher* files
* Enable OpenAL for Linux-ReleaseOS
* Linux: Update OpenAL
* Update SDL2
* Add libsndio-dev to the dependencies.
* Update CEF to an official LL version
* Remove dupe of emoji_shortcodes
* Reording autobuild does because it can and wants to
* Linux: Disable NDOF for the time being. After updating the ndof 3P needs to be rebuilt and we do not have a fresh one from LL yet.
Forcefully undefine LIB_NDOF, it gets defined in the build variables no matter if it is safe to define.
* Remove wrestling with mutliarch and LIBGL_DRIVERS_PATH
* Remove tcmalloc snippet, tcmalloc is a very faint bad dream of the past
* Putting out a warning this viewer ran on a x64 arch and then suggesting to install 32 bit compat packages makes no sense at all
* CEF resources need to be in lib
* It;'s okay to warn about missing plugins
* Linux: CEF keyboard handling
* Remove old gstreamer 0.10 implementation
* Linux DSO loading always had been very peculiar due to macro magic.
At least now it is peculiar shared magic with only one implementation.
* Remove -fPIC. We get that one from LL_BUILD
* /proc/cpuinfo is not reliable to detrmine the max CPU clock. Try to determine this by reading "/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq".
Only if this fails go back to /proc/cpuinfo
* Cleanup
* Cleanup common linker and compiler flags, make it more obvious which flags are for which OS/compiler
* Switch to correct plugin file
* Install libpulse-dev for volume catcher.
* And the runner needs libsndio-dev as well.
* check for runner.os=='linux'. matrix.os is the full name of the image (limux-large).
|
|
* Linux GHA builds
Add Ubuntu 22.04 runner and Linux dependencies
Do not even try to touch ReleaseFS for Linux yet (this needs KDU, Havok, FMOD)
* Lets play a game of 'guess the havok source url'
* Move to linux-large runner.
* ReleaseOS used OpenAL, not fmod studio (which otherwise is the default)
* - Correction for Linux build dir
- HAVOK / CrashReporting wrestling. HAVOK is always turned on, even for OS builds Turn this off for Linux-ReleaseOS
Same with crashreporting, we need it off for now
* Add missing brace
* When doing a GHA build pack right into RUNNER_TEMP and then signal the created archive as our "viewer_app"
* Upload Linux-ReleaseOS after build
* - Need to use os.path.join and not hyst join
- set_github_output_path can be called unconditionally
* Remove Linux GHA build example.
|
|
Co-authored-by: AiraYumi <aira.youme@airanyumi.net>
|
|
|
|
This reverts commit 52945758c479c403f86026f36276d7d805b87af3.
|
|
This reverts commit beea0c55dd68a1584300a02333f8be9ffcac0476.
|
|
This reverts commit f738df6c147a84c17f28b8326c5bc1eb54e4519f.
|
|
This reverts commit c83d93becdee899736a121cbb8eae5c0c9d37c09.
|
|
# Conflicts:
# .github/workflows/build.yaml
|
|
|
|
|
|
|
|
From https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions#using-secrets-in-a-workflow :
"Secrets cannot be directly referenced in if: conditionals. Instead, consider
setting secrets as job-level environment variables, then referencing the
environment variables to conditionally run steps in the job."
|
|
The previous construct produced:
Unrecognized named-value: 'secrets'. Located at position 1 within expression:
secrets.AZURE_KEY_VAULT_URI && ...
|
|
Specifically, when secrets aren't available (e.g. for external PRs), skip the
affected steps.
|
|
Mark issues as stale but do not close them.
|
|
|
|
instead of the branch that got pulled.
(cherry picked from commit b42e01d7acf5d4c55612c3a7df0e1ff6ee5ed951)
|
|
instead of on the current tag 7.1.2-release.
(cherry picked from commit 27b298d8bc720ff315c8e74cc5bff9ff9ead0552)
|
|
This should (!) allow us to generate full release notes relative to the
previous viewer release, instead of letting action-gh-release guess
incorrectly.
Also try again to add to the release page a back-link to the specific build.
(cherry picked from commit 88ebb92f05dade00cc8fc519cc062a458ecd48f2)
|
|
(cherry picked from commit 4edd78f2e54b3cd2e0b0a4b9300dfc669231dd98)
|
|
Using github.ref as action-gh-release's target_commitish produces:
⚠️ GitHub release failed with status: 422
[{"resource":"Release","code":"invalid","field":"target_commitish"}]
(cherry picked from commit c6a6db8488a8b3e7ea6534fbf5e2fe2b17864421)
|
|
Also try to cross-reference release page and build page.
(cherry picked from commit a908b4cfa98716d4a838fc1e5a6789faa15d16cf)
|
|
Put whatever release notes we retrieve into the generated release page.
(cherry picked from commit ff543b744ee0b0fd4dd90b46419ae50a570572ab)
|
|
Now that which_branch.py has moved to viewer-build-util, so has the PyGithub
dependency.
(cherry picked from commit dd0ec112fe5ded8ed5f69b72b3df26343ca12d35)
|
|
which_branch.py has moved to viewer-build-util as a reusable action.
(cherry picked from commit 09f66828ba573515c3766cce32f4746b8189efcf)
|
|
(cherry picked from commit 2c5066f1fcc0c9f145698ef3aaec72d27bce7181)
(cherry picked from commit ff1741cecae0fac6d94507fa4a6e4662219af707)
|
|
in viewer's autobuild-package.xml.
Ensure that AUTOBUILD_VCS_BRANCH is set before the build.
(cherry picked from commit b782ab73e640e434e4ed67fa8dfc951f09757585)
(cherry picked from commit 6e8d4f48466a5bbad2fcc27bc2877a30e575d4ce)
|
|
The release job has been dependent on sign-and-package-windows and
sign-and-package-mac, each of which depends on build. But that indirect
dependency doesn't convey access to ${{ needs.build.outputs.xxx }}. Add the
build job to direct dependencies so release can access its outputs.
(cherry picked from commit 819604d2cee6d4527cc436bebfacddf8642635ff)
|
|
(cherry picked from commit 6654ad14eed674e894d2903e0f2ea37c4e806c0f)
|
|
(cherry picked from commit 59eeaed1187e7592fd83380045916f2d8b9d58e7)
|
|
For a tag build that generates a release page, try to deduce the git branch to
which the tag we're building corresponds and add that to release notes.
(cherry picked from commit 9e99bb04a32f2ecc0f0b99686ce5a7adb356596d)
|
|
(cherry picked from commit f71662225eadf1589f5331e763e02e0bb1b72137)
|
|
instead of the branch that got pulled.
|
|
instead of on the current tag 7.1.2-release.
|
|
This should (!) allow us to generate full release notes relative to the
previous viewer release, instead of letting action-gh-release guess
incorrectly.
Also try again to add to the release page a back-link to the specific build.
|
|
|
|
Using github.ref as action-gh-release's target_commitish produces:
⚠️ GitHub release failed with status: 422
[{"resource":"Release","code":"invalid","field":"target_commitish"}]
|
|
Also try to cross-reference release page and build page.
|
|
|
|
Put whatever release notes we retrieve into the generated release page.
|