Moin,

On Fri, 03 Feb 2023, 12:20:17 +0100, Henne Vogelsang wrote:
> Hey,
> 
> On 03.02.23 10:14, Manfred Hollstein wrote:
> 
> > I've been fighting with the package libheif not building in PMBS during
> > the past few days. I always fails due to the build directory being
> > stored in the built programs as an internal RPATH. The package is linked
> > from openSUSE.org:openSUSE:Factory where no error occurs. I found a
> > patch for it using "chrpath" to delete such RPATH elements in a program.
> > 
> > Can anyone explain why this is necessary when building in PMBS and it is
> > not needed when building in OBS? I fail to see a reason...
> 
> This has nothing to do with OBS instances. It's the repository that matters.
> Just because a repository is called openSUSE_Tumbleweed it isn't neccesarry
> openSUSE Tumbleweed. The name doesn't matter, the included paths do. In this
> case
> 
> Staging/openSUSE_Tumbleweed
> is Multimedia/openSUSE_Tumbleweed
> is Essentials/openSUSE_Tumbleweed
> is openSUSE.org:openSUSE:Tumbleweed/standard
> 
> While openSUSE.org:openSUSE:Factory builds only against the last path in
> your chain.

it's actually much easier... Due to the BUILD_ORIG macro being set to 1
on PMBS, it builds more than what is built on openSUSE:Factory, where
these additional arguments are passed to cmake:

  -DWITH_LIBDE265=OFF -DWITH_X265=OFF -DWITH_EXAMPLES=OFF

Note the -DWITH_EXAMPLES=OFF, which results in no executables being
built/installed at all. I think I need to send my patch to the
multimedia:libs project, so that we (PMBS) don't have to patch the
linked package for each update.

> Henne

Thanks for your help anyway!

Cheers.

l8er
manfred

Attachment: signature.asc
Description: PGP signature

_______________________________________________
Packman mailing list
[email protected]
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Antwort per Email an