You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We successfully use a similar pattern for other templated collection types but for this one the uint8_t seems to be giving us trouble. On build I get the error:
explicit specialization; 'swig::traits<std::pair<mscl::EnumIdentifier,mscl::uint8>>' has already been defined
and the generated wrap.cxx file contains a pair trait definition for both uint8_t and unsigned char:
I tried switching uint8_t to unsigned char in the template definitions, but that resulted in a bunch of unresolved externals. Switching uint8_t to uint16_t resulted in the same as the initial issue, but with unsigned short in the first generated traits def.
In case it's relevant, the same .i file was used to generate a .NET interface without issue. The actual .i file can be found here (ln 296-8).
What am I missing? Let me know if you need any clarification or additional information - thanks!
The text was updated successfully, but these errors were encountered:
I'd try explicitly std:: qualifying the things which are from the std namespace in the %template directives - ISTR there a problem with resolve such cases.
If it's not that, a small, self-contained reproducer would be helpful.
I'm hoping there's something simple to work around this that I'm missing, but I haven't been able to figure it out.
We're building a Python interface for a C++ project and have the following typedefs:
In our interface file (.i) we have the following template definitions:
We successfully use a similar pattern for other templated collection types but for this one the
uint8_t
seems to be giving us trouble. On build I get the error:and the generated wrap.cxx file contains a pair trait definition for both
uint8_t
andunsigned char
:I tried switching
uint8_t
tounsigned char
in the template definitions, but that resulted in a bunch of unresolved externals. Switchinguint8_t
touint16_t
resulted in the same as the initial issue, but withunsigned short
in the first generated traits def.In case it's relevant, the same .i file was used to generate a .NET interface without issue. The actual .i file can be found here (ln 296-8).
What am I missing? Let me know if you need any clarification or additional information - thanks!
The text was updated successfully, but these errors were encountered: