However we stumbled upon this ssue 74120 in our project. We package libiomp5.dylib in our project with original ID of @rpath/libiomp5.dylib . We run delocate on our wheel and delocate changes this ID to /DLC/torch/.dylibs/libiomp5.dylib
When a developer tries to use our wheel and load our lib from Java code. And it fails see issue 74120
This issue can bi mitigated by running install_name tool like this:
1) Is it possible to add an option argument parameter to delocate to not make install name ids unique ? So we can deal with issues like the above.
2) Do you have any suggestion for us on how to deal with this use case, without having to fork delocate code ?
Hi,
This issue is a followup to this discussion that explain this code in delocate :
Ref: https://github.com/matthew-brett/delocate/blob/master/delocate/delocating.py#L669
However we stumbled upon this ssue 74120 in our project. We package libiomp5.dylib in our project with original ID of
@rpath/libiomp5.dylib
. We run delocate on our wheel and delocate changes this ID to/DLC/torch/.dylibs/libiomp5.dylib
When a developer tries to use our wheel and load our lib from Java code. And it fails see issue 74120
This issue can bi mitigated by running install_name tool like this:
Based on the above I have following questions:
1) Is it possible to add an option argument parameter to delocate to not make install name ids unique ? So we can deal with issues like the above. 2) Do you have any suggestion for us on how to deal with this use case, without having to fork delocate code ?
cc @malfet