-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Xcode16 build fix #2585
Open
marchcat
wants to merge
28
commits into
develop
Choose a base branch
from
marchcat/xcode-16
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+330
−424
Open
Xcode16 build fix #2585
Changes from 1 commit
Commits
Show all changes
28 commits
Select commit
Hold shift + click to select a range
576c558
Xcode16 build fix
marchcat 705fd68
Make `LLPointer` equality comparisons accept not-identical types.
nat-goodspeed 1a682de
LLConstPointer<T> is the same as LLPointer<const T>.
nat-goodspeed 98c829a
Use copy-and-swap idiom for LLPointer's assignment operators.
nat-goodspeed 5d7b3ab
Explain why apparently redundant LLPointer methods are necessary.
nat-goodspeed 4b2b94f
Merge pull request #2681 from secondlife/nat/xcode-16
marchcat 55df732
Merge branch 'develop' into marchcat/xcode-16
nat-goodspeed dc0c6d3
Adapt `fsyspath` for C++20 conventions.
nat-goodspeed 988a0fd
Fix a few more fsyspath conversions, removing explicit u8string().
nat-goodspeed 015ff3d
#include <cmath> rather than "math.h" to avoid lerp() conflict.
nat-goodspeed 6400284
Ditch our own (conflicting) definition of the lerp() function.
nat-goodspeed 6ac59d1
Fix GCC ambiguous-reversed-operator errors for `LLKeyData` compares.
nat-goodspeed d7f6b96
Reinstate our lerp() function, avoid "math.h" header.
nat-goodspeed 15dad13
Set continue-on-error for linux builds
marchcat 452e074
Remove whitespace for pre-commit
marchcat 8a6da4d
Rename our lerp() to flerp(); call where MSVC balks at std::lerp().
nat-goodspeed b043ed4
Merge remote branch 'develop' into marchcat/xcode-16
nat-goodspeed fcfcca9
Ditch last instances of LL_LIBRARY_INCLUDE.
nat-goodspeed d3833b6
Fix lerp issues and eliminate flerp in favor of std::lerp (#2712)
Ansariel a2b76b6
Migrate ~LLPointer()'s peculiar warning case to llpointer.cpp.
nat-goodspeed d39c862
Automate memory management in JPEG2KEncode and JPEG2KDecode.
nat-goodspeed c7cef95
Allow Windows and Mac builds to succeed despite Linux failure.
nat-goodspeed 51fb298
Try again to let Windows and Mac succeed despite Linux failure.
nat-goodspeed ecc2ada
lltexlayerparams.h uses std::atomic<bool>, so #include <atomic>
nat-goodspeed 5c9d60c
Linux GCC prefers the explicit std::string::assign() call.
nat-goodspeed 1c78829
Introduce owning_ptr<T>; use it for JPEG2KEncode and JPEG2KDecode.
nat-goodspeed cf2f482
Slightly streamline owning_ptr class definition.
nat-goodspeed 71e89d6
Merge pull request #2714 from secondlife/nat/xcode-16
nat-goodspeed File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's pull in Ansariel's free functions to compare
(T* == LLPointer<T>)
and!=
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They are already in the
develop
branch (d91d39f). The problem here is that obj is aLLVOVolume
pointer and mDragHoveredObject is anLLPointer<LLViewerObject>
, so the overloaded operator doesn't work.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we're comparing pointers to different types in the same class hierarchy, shouldn't we formally be downcasting one of them to match the other? We don't use a lot of multiple inheritance, but a pointer to object A's base class doesn't necessarily have the same bit pattern as a pointer to A.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That would probably be a smart thing to do.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I should have realized the language takes care of that.
That being the case, I'll try tweaking the
(T* == LLPointer<T>)
comparisons to accept a raw pointer to arbitrary type, letting the compiler produce an error if the two pointer types can't be compared.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#2681