Age | Commit message (Collapse) | Author |
|
since it doesn't have GL_MULTISAMPLE_EXT.
|
|
This reverts commit e600f6504cd7edd9d2883ea7dc17c2574b1ff468.
|
|
They weren't compiled with the previous commit, and it affected a lot.
|
|
|
|
|
|
|
|
|
|
so non implementors won't try to compile the code.
|
|
|
|
to minimise difference from upstream, as it's certain it's not FreeBSD
anyway due to the removal of LL_FREEBSD on the containing scope.
|
|
|
|
since the latter is less portable.
I'm guessing 1st arg is 0 since the condition is when mTex is empty.
|
|
for those that don't implement the 8 suffixed ones.
|
|
|
|
before compiling its code.
|
|
|
|
|
|
|
|
|
|
replacing its APPLE counterpart.
|
|
|
|
|
|
So that, especially modern, GL implementations that do have vertex array
but don't have the legacy GL_ARB_vertex_array_object defined have such
code compiled too.
|
|
replacing its EXT suffixed counterpart.
|
|
|
|
so the macros can be used on platforms that don't have ARB specs.
|
|
preprocessed so it doesn't get compiled on non implementors.
|
|
replacing their legacy ARB counterparts.
|
|
replacing their legacy ARB counterparts.
|
|
|
|
replacing legacy ARB versions.
|
|
replacing legacy ARB versions.
|
|
Whether to create/delete, or take the program object as an argument.
Include ones for attaching & detaching shaders too, ones that deal with
attributes & uniforms and so on, etc..
Replacing legacy ARB versions.
|
|
replacing legacy ARB versions.
|
|
to replace the less portable ARB versions.
|
|
(cherry picked from commit 3d2da2b2c09fc637c2eaccac1607e3480bede145)
|
|
so that implementations that don't include a certain GL implementation
won't fail trying to compile the code.
|
|
at the same time revert to less difference from upstream.
|
|
which are mostly ARB ones, and instead we define GLEXT prototypes to be
true so we still get access to the functions.
|
|
in the path passed as the macOS viewer_exe GitHub output.
|
|
On Mac, in the CMake USE_BUGSPLAT logic, we created both xcarchive.zip (which
is what BugSplat wants to see) and secondlife-symbols-darwin -64.tar.bz2 (which
we don't think is used for anything). The tarball was posted to codeticket --
but why? If the point is to manually re-upload to BugSplat in case of failure,
we'll do better saving xcarchive.zip to codeticket.
For SL-19243, posting xcarchive.zip directly supports the goal of breaking out
the upload to BugSplat as a separate step.
Anyway, since xcarchive.zip is a superset of the tarball, the tarball can be
recreated from the zip file, whereas the zip file can't be recreated from the
tarball without opening the .dmg installer and extracting the viewer executable.
If the xcarchive.zip file exists (that is, on Mac), post that to codeticket or
GitHub, as applicable, instead of the tarball. In fact, in the USE_BUGSPLAT
case, don't even bother creating the tarball since we're going to ignore it.
Make the new build.sh logic that insists on BUGSPLAT_USER and BUGSPLAT_PASS
conditional on BUGSPLAT_DB.
|
|
|
|
|
|
Use a retry loop very like the code-signing retry loop.
|
|
A test executable on a GitHub Windows runner failed with C00000FD, which
reports stack overflow.
(cherry picked from commit aab7b4ba3812e5876b1205285bcfd8cff96bcac9)
|
|
Upload a new Windows-exe artifact containing just the executable (needed by
BugSplat) separately from the artifact containing the whole NSIS installer.
This requires a new viewer_exe step output set by viewer_manifest.py.
Define viewer_channel and viewer_version as build job outputs.
Set viewer_channel in build.yaml when tag is interpreted.
Set viewer_version in build.sh at the point when it would have posted
viewer_version.txt to codeticket.
Add a post-windows-symbols job dependent on the build job that engages
secondlife/viewer-post-bugsplat-windows, which in turn engages
secondlife/post-bugsplat-windows. We keep the actual upload code in a separate
repo in case we need to modify that code before rerunning to resolve upload
errors. If we kept the upload code in the viewer repo itself, rerunning the
upload with modifications would necessarily require rerunning the viewer
build, which would defeat the purpose of SL-19243.
Because of that new upload job in build.yaml, skip Windows symbol uploads
in build.sh.
Use a simple (platform name) artifact name for metadata because of
flatten_files.py's filename collision resolution.
Use hyphens, not spaces, in remaining artifact names: apparently
download-artifact doesn't much like artifacts with spaces in their names.
Only run the release job when in fact there's a tag. Without that, we get
errors. We need not create flatten_files.py's output directory beforehand
because it will do that implicitly.
|
|
|
|
The line that enables it in when on external TOS was only present in a
similar scope which doesn't seem to be reachable. It must have been missed
when the condition checking was moved.
|
|
Add DEBUG log output to try to diagnose.
|
|
|