undefined symbol: sipExportedExceptions_limacore

[Laurent Claustre]

in fact we do not use the sip module but we compile over the sip source 
file (sip_array.c sip_core.c sip_descriptors.c sip_enum.c 
sip_int_convertors.c sip_object_map.c sip_threads.c sip_voidptr.c). Idea 
is to build our project with sip other installed conda package which can 
use different version of sip.
Should we not do build like that or there are  missing build configuration?

Laurent

On 12/1/25 17:23, Phil Thompson wrote:
> Well there is something wrong with it. When a SIP generated module is 
> imported it registers itself with the sip module. processlib doesn't 
> seem to be doing that. When limacore is imported it imports processlib 
> and looks for it in the sip module registry.
>
> On 01/12/2025 15:59, Laurent Claustre wrote:
>> Yes we did it.
>>
>> On 12/1/25 15:58, Phil Thompson wrote:
>>> On 01/12/2025 14:47, Laurent Claustre wrote:
>>>> Hi,
>>>>
>>>> thanks the exceptions flag helps definitively.
>>>>
>>>> Now I have an other issue, this project limacore is using an other
>>>> module we bind with sip too, called processlib and I get this error
>>>> when importing limacore:
>>>>
>>>>>>> from Lima import Core
>>>> Traceback (most recent call last):
>>>>   File "<stdin>", line 1, in <module>
>>>>   File
>>>> "/opt/bliss/conda/miniconda/envs/lima_dev_sip6/lib/python3.12/site-packages/Lima/Core/__init__.py", 
>>>> line 24, in <module>
>>>>     from limacore import *
>>>> RuntimeError: the processlib module failed to register with the sip 
>>>> module
>>>
>>> Has processlib been ported to the latest SIP?
>>>
>>> Phil

-- 
Laurent Claustre

Beamline Control Unit
Instrumentation Services and Development Division
ESRF - The European Synchrotron
71, avenue des Martyrs
38000 Grenoble, FRANCE
Tel.: +33 (0)4.76.88.29.12