cppgsh by Python Library
Overview
This Program Inspired by Quom I made.
Goal
- Automation Build Single header for C++.
Implementation
What is different from the original Quom?
-
It is automatically looks for the root header or source and creates a single header in the proper order.
-
Put the include file at the beginning to eliminate duplication.
Install
$ pip install cppgsh
UnInstall
$ pip uninstall cppgsh
Requirement
- python3.6 later.
Liscense
run command Environment
- Windows
- Linux
- Mac OSX
Usage
usage: cppgsh [-h] [--include_guard format]
[--include_directory INCLUDE_DIRECTORY]
[--source_directory SOURCE_DIRECTORY]
[--exclude_patterns EXCLUDE_PATTERNS]
[--license_files LICENSE_FILES] [--del_extern_C]
[--linesep LINESEP] [--encoding ENCODING] [--quiet]
output
Single header generator for C++ libraries.
positional arguments:
output Output file path of the generated single header file.
optional arguments:
-h, --help show this help message and exit
--include_guard format, -g format
Regex format of the include guard. Default: None
--include_directory INCLUDE_DIRECTORY, -I INCLUDE_DIRECTORY
Add include directories for header files.
--source_directory SOURCE_DIRECTORY, -S SOURCE_DIRECTORY
Set the source directories for source files. Use ./ or
.\ in front of a path to mark as relative to the
header file.
--exclude_patterns EXCLUDE_PATTERNS, -E EXCLUDE_PATTERNS
Set the source directories for source files. Use ./ or
.\ in front of a path to mark as relative to the
header file.
--license_files LICENSE_FILES, -L LICENSE_FILES
Set headline writing License text file path
--del_extern_C delete define "extern "C""
--linesep LINESEP, -l LINESEP
line separator of output file.
--encoding ENCODING, -e ENCODING
The encoding used to read and write all files.
--quiet, -q no print progress info
Example
TODO
Libraries used
Metadata
Release files for cppgsh 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cppgsh-0.2.1.tar.gz | 8.4 kB | Without provenance | Details for cppgsh-0.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cppgsh-0.2.1-py3-none-any.whl | Python 3 | none | any | Details for cppgsh-0.2.1-py3-none-any.whl |
Total release size: 16.3 kB
Release files / cppgsh-0.2.1.tar.gz
| Download URL | cppgsh-0.2.1.tar.gz |
|---|---|
| Size | 8.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f2f252ae9166be585e7a5204571ebe698ebf18a611a2b75a67eea985b8ca148d
|
|
BLAKE2b-256 checksum How to use checksums |
a618cc2865ad78e110e2e71adb43bf6747554803b510daf8840a155319996d7c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.10.1 pkginfo/1.8.2 requests/2.22.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.10
|
Release files / cppgsh-0.2.1-py3-none-any.whl
| Download URL | cppgsh-0.2.1-py3-none-any.whl |
|---|---|
| Size | 7.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f19f91088cfce91417b2de7aa5a50517d417a6d6be323a8fe2860924b9e0d492
|
|
BLAKE2b-256 checksum How to use checksums |
65ecdd0cb2ad01079b84b74eee0cfeb206ec2fd660ad8a6431f0749284860e8c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.10.1 pkginfo/1.8.2 requests/2.22.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.10
|
Security for cppgsh 0.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.