Age | Commit message (Collapse) | Author |
|
For now it's when there's no GTK, to minimise diff.
They should all just use SDL.
|
|
since we don't have any web browser there either.
|
|
|
|
|
|
source for viewer 6.6.16.6566955269
|
|
This reverts commit 658ff1a0a14af93b96de22d3def56b93c0a5abd2.
|
|
This reverts commit b6574337ed3fd7749db6185501cd444305d44905.
|
|
clang has gotten smart enough to recognize an inline attempt to store to
address zero. Fool it by storing to an address passed as a parameter, and pass
nullptr from a different source file.
|
|
Even though LLVersionInfo::getBuild() already returns a 64-bit int, various
consumers assumed it could fit into 32 bits. It was especially bad to pass it
to a classic C style varargs function. Only on a little-endian CPU, and only
because it was the last argument, the damage was limited to truncation --
instead of arbitrary undefined behavior.
Where the consumer doesn't support 64-bit ints, pass as string instead.
|
|
|
|
|
|
At runtime it hasn't worked anyway. And now we can get an ARM build
without having to build libvlc for ARM first.
|
|
The header file documents that no llrand function should ever return a value
equal to the passed extent, so the one test in llrand_test.cpp that checked
less than or equal to the high end of the range was anomalous.
But changing that to an exclusive range means that we no longer need separate
exclusive range and inclusive range functions. Replace
ensure_in_range_using(), ensure_in_exc_range() and ensure_in_inc_range() with
a grand unified (simplified) ensure_in_range() function.
|
|
We're not even redistributing Vivox yet (if we ever will).
|
|
Since we're not distributing licenses.txt yet (not using the Python script).
|
|
to avoid any "Stop camming me" from happening.
Showing Look At is something advanced anyway.
|
|
Necessary on some platforms.
|
|
It's frustrating and unactionable to have a failing test report merely that
the random value was greater than the specified high end. Okay, so what was
the value? If it's supposed to be less than the high end, did it happen to be
equal? Or was it garbage? We can't reproduce the failure by rerunning!
The new ensure_in_exc_range(), ensure_in_inc_range() mechanism is somewhat
complex because exactly one test allows equality with the high end of the
expected range, where the rest mandate that the function return less than the
high end. If that's a bug in the test -- if every llrand function is supposed
to return less than the high end -- then we could simplify the test logic.
|
|
This branch cleans up crufty code in build.yaml, build.sh and
viewer_manifest.py that was packaging, signing and uploading installers before
the SL-19242 work.
|
|
|
|
This is referenced after running the packaging.
|
|
|
|
which includes another misleading indentation, and a double use of the
variable is_asset_knowable.
|
|
It was okay on FreeBSD's Clang, but an error on AppleClang and GCC too.
|
|
for Mac and Windows. That's now done by subsequent jobs in the GitHub build.
Remove workflow step to upload installers before signing and packaging jobs.
Remove from viewer_manifest.py conditionals for 32-bit Windows or Mac.
Also bump to actions/checkout@v4, per dependabot.
|
|
source for viewer 6.6.15.581961
|
|
following promotion of DRTVWR-567
|
|
We were creating the tarball with the app bundle stored as the whole
'Users/someone/.../newview/Release/Second Life Mumble.app' path. Don't.
|
|
|
|
|
|
actions/upload-artifact doesn't preserve symlinks, which are important for our
Mac viewer and its embedded frameworks. But tar does, so pack up the whole
bundle as a tarball before posting as a GitHub artifact.
|
|
|
|
|
|
|
|
|
|
The viewer_manifest.py logic to determine the name of the viewer installer
.dmg is a little convoluted. Make it tell viewer-build-util/sign-pkg-mac that
name, rather than passing it all the relevant inputs and composing it
redundantly.
sign-pkg-mac also wants the viewer channel to determine the application name.
|
|
|
|
|
|
|
|
at least for now.
|
|
|
|
Others are fine without the error turned off, and the flag might not
even be available on some other's Clang.
|
|
|
|
|
|
|
|
|
|
|
|
Copying from GTK users part though.
|
|
|
|
If they do, NSIS takes it as line continuation.
|