pEp.foundation
/
pEpACIDgen
2
0
Fork 0
Code Pull Requests Releases Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
575 Commits
1 Branch
0 Tags
15 MiB
 
 
Tree: 1b452adcc4
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '1b452adcc4'
${ noResults }
heck 1b452adcc4
Array Support added. 		5 years ago
examples lib_test: add vars for: structs containing arrays, typedefs for structs containing arrays. Array versions of all vars so far. AnD vars for all typedefs of arrays of typedefs. 5 years ago
pEpACIDgen Array Support added. 5 years ago
tests Array Support added. 5 years ago
.editorconfig .editorconfig more filetype specifics 5 years ago
.gitignore gitignore debug files 5 years ago
AUTHORS.txt pEpACIDgen - INITIAL COMMIT 5 years ago
LICENSE.txt adding LICENSE.txt - this adapter is under the GNU Affero General Public License 9 years ago
MANIFEST.in pEpACIDgen - INITIAL COMMIT 5 years ago
Makefile pEpACIDgen - INITIAL COMMIT 5 years ago
README.md pEpACIDgen - INITIAL COMMIT 5 years ago
pyproject.toml pEpACIDgen - INITIAL COMMIT 5 years ago
setup.cfg pEpACIDgen - INITIAL COMMIT 5 years ago
setup.py pEpACIDgen - INITIAL COMMIT 5 years ago

README.md

pEpACIDgen

pEpACIDgen stands for "pEp Abstract C Interface Description Generator"

pEpACIDgen generates an Abstract C Interface Defintion file (json or yml2) given the inputs:

  • headerfile
  • list of function names needed
  • list of var names needed

The generator searches each function/var in the headerfile (recursively) and collects all the types needed (var type, return type, parm types).
As structs can contain further types, these dependent types need to be collected recursively.
Finally, all the collected types will be resolved to their final underlying type. If a type is primitive, nothing needs to be done, cause its already defined. But types of typekind struct or enum need to be defined. Their definition will be searched for in the headerfile and included in the interface definition The ACID file (yml2) contains all the information needed to represent:

  • functions
  • vars
  • structs
  • enums

well enough so they can be expressed in pyBind11.
use "pyBind11-CID" to generate the pyBind11 code out of the ACID file.