[Slackbuilds-users] issue with openimageio after pybind11 update

[Christoph Willing]

On 20/1/24 19:11, Tim Dickson via SlackBuilds-users wrote:
> thanks for the heads up chris, I wondered if that might be the case.
> Maybe a note in the opencolorio readme to temporarily uninstall 
> openimageio if present before building the package would be useful?
> regards, Tim

The problem with that is that while it solves the problem you had, it's 
not necessarily true in all situations.

Usually, after building opencolorio successfully, you would use that new 
build to rebuild openimageio. Having done that (new openimagio based on 
successful opencolorio), you will find that you can now rebuild 
opencolorio while leaving openimgeio in place. Now there will be some 
new optimisations in opencolorio using components available in 
openimageio. At that point you could rebuild openimageio against the 
updated opencolorio, presumably resulting in an optimised openimageio.

I'm unsure how to express all that simply enough without causing 
confusion for the average user who is probably just passing through on 
their way to a build of Blender. I'll think of something ...


chris


> On 20/01/2024 01:31, Christoph Willing wrote:
>> On 20/1/24 08:56, Tim Dickson via SlackBuilds-users wrote:
>>> since the pybind11 update opencolorio is no longer building for me.
>>> []
>>>
>>> I don't know why it's trying to link to libOpenImageIO files when it 
>>> is not marked as a dependency (I do have openimageio-2.2.21.0-4 
>>> installed)
>>> anyone else seeing this or got a fix?
>>> thanks,Tim
>>
>> openimageio and opencolorio will each try to link against the other 
>> if present. It's an unfortunate "natural" recursive dependency which 
>> I try to minimise in the .info files by setting opencolorio as a 
>> dependency of openimageio but _not_ setting openimageio as a 
>> dependency of opencolorio. This attempted minimisation fails in the 
>> case where openimageio is already installed when building 
>> opencolorio, which is exactly your situation.
>>
>> If a clean VM for building is not available, I would recommend that 
>> you temporarily remove openimageio, then build opencolorio, then 
>> reinstall (or even better: rebuild & install) openimageio.
>>
>> chris
>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>