CMake Converter
Introduction
This project aims to facilitate the conversion of Visual Studio solution to CMake projects. The goal is to give to a Python script, a *.sln file, and output a set of CMakeLists.txt that may be used for generating visual studio solution backward as perfect as possible. Project is useful for porting VS projects into CMake build system.
Note : Actually, it’s only works with C/C++ (*.vcxproj) and Fortran (*.vfproj) projects.
Install & Run
Install package from PyPI
Install last stable release of cmake-converter:
pip install cmake-converter
Note : If you found an issue in the package installed from pip, please, do not create github issue at once and check for pre-release version (pip -pre) or last source from develop first. It might be has fixed already and ready to release.
Install package from source code
Simply clone or download the repository and type the following command to install it:
# Inside repository folder. pip install .
Run
After install library, just run the script as below. Your *.sln file is of course required:
cmake-converter -s <path/to/file.sln>
Note : If you satisfied with conversion, give a star to the project and consider to donate, please.
Documentation
Documentation for CMake Converter is available on Read The Docs.
Bugs, issues and contributing
Contributions to this project are welcome and encouraged … Issues in the project repository are the common way to raise an information.
Note: if you have an issue, please provide me if possible the visual studio project involved.
Donations
If you appreciate my efforts related to this project, give me a gift. I’ll be glad to get some money working for free ;) To make a donation - please press the button below.
Metadata
Release files for cmake-converter 2.2.0
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 |
|---|---|---|---|---|
| cmake_converter-2.2.0.tar.gz | 60.8 kB | Without provenance | Details for cmake_converter-2.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cmake_converter-2.2.0-py3-none-any.whl | Python 3 | none | any | Details for cmake_converter-2.2.0-py3-none-any.whl |
Total release size: 140.3 kB
Release files / cmake_converter-2.2.0.tar.gz
| Download URL | cmake_converter-2.2.0.tar.gz |
|---|---|
| Size | 60.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
88315027f773c6a7cf621e0c98862577a6e95d9d7f3b386111e711c461b9f888
|
|
BLAKE2b-256 checksum How to use checksums |
4056144dda346604ab4d96163860996e685980438cd505b61389c348e823d282
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.2.0 requests-toolbelt/0.8.0 tqdm/4.33.0 CPython/3.6.6
|
Release files / cmake_converter-2.2.0-py3-none-any.whl
| Download URL | cmake_converter-2.2.0-py3-none-any.whl |
|---|---|
| Size | 79.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b07c662d2baf19d19dea2d05654222a1cba6b1d251a65c9f721dc3cf2f90dc3b
|
|
BLAKE2b-256 checksum How to use checksums |
efb3eae2b6c2159d807245e2b581979a2ae1dc560b51f49219f7560de7b97584
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.2.0 requests-toolbelt/0.8.0 tqdm/4.33.0 CPython/3.6.6
|
Security for cmake-converter 2.2.0
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.