[Parted-edge] C++ bindings: directory structure
anant at kix.in
Wed Feb 21 17:21:04 UTC 2007
> a. Include/import files: include/partedpp to keep the C++ bindings' header
> files. A similar scheme can be followed for the PyParted headers also. An
> alternative can be include/parted/partedpp.
-1. Best not to mix up binding headers with the actual headers. All
bindings must be self-contained in their own directories. In the ideal
case, you should be able to build bindings by checking out only those
modules from git, and without the original parted sources.
> b. Other sources: The actual C (from PyParted) or C++ (from Libpartedpp) files
> can be kept in bindings/python and bindings/cpp. An alternative can be
> libparted/python and libparted/cpp.
Here's what would be a better scheme:
More information about the Parted-edge