Thomas Guillem authored 3 years ago and Hugo Beauzée-Luyssen committed 3 years ago

Converting 0 frames to 0 ticks is valid.

Pierre Lamot authored 3 years ago and Hugo Beauzée-Luyssen committed 3 years ago

system theme may implicitly define some padding to the base Control (KDE)

Pierre Lamot authored 3 years ago and Hugo Beauzée-Luyssen committed 3 years ago

Platform qml theme (on KDE for instance) can pre-define some padding on the
Contol leading to misalignment

Pierre Lamot authored 3 years ago and Hugo Beauzée-Luyssen committed 3 years ago

Misalignment may occur if the system QQC theme defines implicit padding (KDE)

Pierre Lamot authored 3 years ago and Hugo Beauzée-Luyssen committed 3 years ago

Misalignment may occur if the system QQC theme defines implicit padding (KDE)

Pierre Lamot authored 3 years ago and Hugo Beauzée-Luyssen committed 3 years ago

Labels may have some custom font size defined in pointSize in the system theme
(KDE), this would conflicts with our pixelSize definition and generate a warning

Pierre Lamot authored 3 years ago and Hugo Beauzée-Luyssen committed 3 years ago

this was causing wrong sizing on some plateforms

Also match the semantics of both functions.

No effective functional or ABI changes.

(No functional changes.)

Marvin Scholz authored 3 years ago and Hugo Beauzée-Luyssen committed 3 years ago

The function does _not_ copy the data.

Alexandre Janniaux authored 3 years ago and Hugo Beauzée-Luyssen committed 3 years ago

With latest SDK, arm64 is returned as architecture name for aarch64
machine targets from Apple, which is not recognized by autoconf, and
breaks compilation of multiple contribs.

We still need to indicate that we want an arm64 SDK, but replace arm64
by aarch64 in build triplets until autoconf fixes this.

Rémi Denis-Courmont authored 3 years ago and Hugo Beauzée-Luyssen committed 3 years ago

As of c0f0d085, waiting on a condition
variable is no longer a cancellation point. So these cleanup handlers
no longer serve any purpose.

Martin Finkel authored 3 years ago and Hugo Beauzée-Luyssen committed 3 years ago

In LibVLC 3, passing a NULL media was supported. In LibVLC 4, it currently crashes.
Fixes vlc-unity#123

Zhao Zhili authored 3 years ago and Jean-Baptiste Kempf committed 3 years ago

refs #22391

Fatih Uzunoğlu authored 3 years ago and Jean-Baptiste Kempf committed 3 years ago

This reverts commit 38a3fb64.

Fatih Uzunoğlu authored 3 years ago and Jean-Baptiste Kempf committed 3 years ago

This reverts commit 1f4113bd.

Rémi Denis-Courmont authored 3 years ago and Hugo Beauzée-Luyssen committed 3 years ago

As defined in RFC2397.

Thomas Guillem authored 3 years ago and Hugo Beauzée-Luyssen committed 3 years ago

cf. https://developer.apple.com/library/archive/documentation/DeveloperTools/Conceptual/DynamicLibraries/100-Articles/DynamicLibraryUsageGuidelines.html#//apple_ref/doc/uid/TP40001928-SW12

"""
When the library name is a filename (that is, when it doesn’t include
directory names), the dynamic loader searches for the library in several
locations until it finds it, in the following order:

 - $LD_LIBRARY_PATH
 - $DYLD_LIBRARY_PATH
 - The process’s working directory
 - $DYLD_FALLBACK_LIBRARY_PATH

When the library name contains at least one directory name, that is,
when the name is a pathname (relative or fully qualified), the dynamic
loader searches for the library in the following order:

 - $DYLD_LIBRARY_PATH using the filename
 - The given pathname
 - $DYLD_FALLBACK_LIBRARY_PATH using the filename
 """

Conclusion: DYLD_LIBRARY_PATH on macOS behave like LD_LIBRARY_PATH on
Linux but LD_LIBRARY_PATH on macOS has a different behavior than
LD_LIBRARY_PATH on Linux, so DYLD_LIBRARY_PATH should be used on macOS.
Specially since we can't really control if the library name will include
a path or not (relative or absolute).