Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

igate: forcetype and dup signatures #722

Closed
pmp-p opened this issue Sep 3, 2019 · 3 comments
Closed

igate: forcetype and dup signatures #722

pmp-p opened this issue Sep 3, 2019 · 3 comments
Labels
Milestone

Comments

@pmp-p
Copy link
Contributor

@pmp-p pmp-p commented Sep 3, 2019

When using forcetype to re-export C++ headers toward C bindings
with ( -S includes removed)
interrogate -promiscuous -string -fnames -assert -c -v -S /usr/include --oc ./build/interrogate_temp.cpp -srcdir ./lib -nomangle -od ./build/interrogate.in -module -library -DINTERROGATE -DCPPPARSER -D__STDC__=1 -D__cplusplus=201103L -D__attribute__\(x\)= -D__x86_64__ -D_LP64 lib.h lib.cxx

export often breaks on those kind of error :

forcetype NodePath

Internal error! Function signature NodePath::get_node(int, Thread *) const repeated!

forcetype PandaSystem

Internal error! Function signature PandaSystem::get_system(std::size_t) const repeated!

forcetype ConfigPage

Internal error! Function signature ConfigPage::modify_declaration(std::size_t) repeated!

forcetype Camera

Internal error! Function signature Camera::get_display_region(std::size_t) const repeated!

is it at least possible to let exports continue, skipping the dup, since anyway using C ffi bindings would probably operate on a reduced api set and a simplified framework ?

use case: micropython ffi bindings with https://github.com/pmp-p/panda3d-interrogator

@rdb rdb added the interrogate label Sep 3, 2019
@rdb

This comment has been minimized.

Copy link
Member

@rdb rdb commented Sep 3, 2019

Ah, I think it has to do with the MAKE_SEQ_PROPERTY system, since all of those are properties used in a MAKE_SEQ_PROPERTY. As a workaround, you can redefine MAKE_SEQ_PROPERTY to nothing.

@rdb rdb added the bug label Sep 3, 2019
@rdb

This comment has been minimized.

Copy link
Member

@rdb rdb commented Sep 3, 2019

This was actually caused by some vestigial code in interrogate that can be removed. I can get a fix into 1.10.5.

@rdb rdb added this to the 1.10.5 milestone Sep 3, 2019
rdb added a commit that referenced this issue Sep 3, 2019
@pmp-p

This comment has been minimized.

Copy link
Contributor Author

@pmp-p pmp-p commented Sep 3, 2019

fix is good

@pmp-p pmp-p closed this Sep 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.