| Name | scargo JSON |
| Version |
2.3.0
JSON |
| download |
| home_page | None |
| Summary | C/C++ package and software development life cycle manager inspired by RUST cargo idea. |
| upload_time | 2024-04-11 09:15:03 |
| maintainer | None |
| docs_url | None |
| author | None |
| requires_python | >=3.8 |
| license | None |
| keywords |
scargo
package manager
c++
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
# Scargo
Scargo project was written by Spyrosoft team. Find more information at [spyro-soft.com](https://spyro-soft.com/career).
<p align="center">
<img src="https://raw.githubusercontent.com/Spyro-Soft/scargo/develop/docs/source/_static/spyrosoft_solutions_logo_color.png" alt="drawing" width="200"/>
</p>
# Overview
This is the documentation for scargo - a Python-based C/C++ package and software development life cycle manager inspired by RUST cargo idea.
scargo can:
- Create a new project (binary or library)
- Build the project
- Run static code analyzers
- Fix chosen problem automatically based on the checker analysis
- Run unit tests
- Generate documentation from the source code
- Work with the predefined docker environment depending on the chosen architecture
# Installation
Scargo is available on [pypi](https://pypi.org/project/scargo/), so you can install it with pip:
```pip install scargo```
If system does not find 'scargo' command after installing, add the installation directory to your env paths. On Ubuntu you can find installation directory by running:
```$ find / -name "scargo"```
Then add to PATH:
```$ export PATH=~/.local/bin:${PATH}```
# Working with scargo
You can find all information on how to work with scargo on official documentation webpage: https://spyro-soft.github.io/scargo/index.html
# Project dependencies
## Working with docker (recommended)
- docker
- docker-compose
- pip
- python3
## Working natively (not recommended, a lot of env setup)
Base:
- python >= 3.8
- cmake >= 3.24.2
- cppcheck lib32z1 clang clang-format clang-tidy gcovr doxygen libcmocka0 libcmocka-dev
- lizard
Depending on the architecture:
- compiler (e.g. gcc-arm-none-eabi-9-2020-q2-update gcc-arm-none-eabi)
- flashing tools
- uC HAL and dependent files
- much more....
# Work environment
You can always change work environment between docker or native after project is created.
Just edit the scargo.toml file ([project] -> build-env = "docker" or build-env = "native").
## Working in docker
1) If you create a new project, run `docker compose run scargo-dev` to run project development image depending on chosen architecture. All dependencies should be already there.
Run scargo commands as you would do natively.
2) If you create a project with --docker flag (`scargo new <my_proj> --docker ...`) or with any docker flag, by default each scargo command will be triggered in docker.
## Working natively
1) Create a project with --no-docker flag (`scargo new <my_proj> --no-docker ...`).
## Testing custom scargo generated project locally
You can make changes in scargo and install it locally using ```pip install .``` command when you are in the main project folder.
To test the custom scargo version and have this custom scargo available also inside the docker (crucial for testing), in created project update docker-compose.yaml:
volumes:
- ..:/workspace
- /dev:/dev
- ~/.local/lib/python3.10/site-packages/scargo:/usr/local/lib/python3.8/dist-packages/scargo
Where ```~/.local/lib/python3.10/site-packages/scargo``` is a path to scargo on your local machine. It the following path is not working, find installation dir using ```pip show scargo```.
To keep this setup between ```scargo update``` commands, in scargo.toml file update also ```update-exclude``` as in following example:
update-exclude = [".devcontainer/docker-compose.yaml"]
# Contributing
See contributing guide on https://spyro-soft.github.io/scargo/contributing.html
Raw data
{
"_id": null,
"home_page": null,
"name": "scargo",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.8",
"maintainer_email": null,
"keywords": "scargo, Package manager, C++",
"author": null,
"author_email": "\"Spyrosoft Solutions S.A.\" <aak@spyro-soft.com>",
"download_url": "https://files.pythonhosted.org/packages/56/f5/3886b73f60720e8b75a4ea6f5dbe7bce3750f1e4955825bca5e476c3c2e8/scargo-2.3.0.tar.gz",
"platform": null,
"description": "# Scargo\nScargo project was written by Spyrosoft team. Find more information at [spyro-soft.com](https://spyro-soft.com/career).\n<p align=\"center\">\n <img src=\"https://raw.githubusercontent.com/Spyro-Soft/scargo/develop/docs/source/_static/spyrosoft_solutions_logo_color.png\" alt=\"drawing\" width=\"200\"/>\n</p>\n\n# Overview\nThis is the documentation for scargo - a Python-based C/C++ package and software development life cycle manager inspired by RUST cargo idea.\n\nscargo can:\n\n- Create a new project (binary or library)\n- Build the project\n- Run static code analyzers\n- Fix chosen problem automatically based on the checker analysis\n- Run unit tests\n- Generate documentation from the source code\n- Work with the predefined docker environment depending on the chosen architecture\n\n# Installation\nScargo is available on [pypi](https://pypi.org/project/scargo/), so you can install it with pip:\n\n```pip install scargo```\n\nIf system does not find 'scargo' command after installing, add the installation directory to your env paths. On Ubuntu you can find installation directory by running:\n\n```$ find / -name \"scargo\"```\n\nThen add to PATH:\n\n```$ export PATH=~/.local/bin:${PATH}```\n\n# Working with scargo\nYou can find all information on how to work with scargo on official documentation webpage: https://spyro-soft.github.io/scargo/index.html\n\n\n# Project dependencies\n## Working with docker (recommended)\n- docker\n- docker-compose\n- pip\n- python3\n\n## Working natively (not recommended, a lot of env setup)\nBase:\n\n- python >= 3.8\n- cmake >= 3.24.2\n- cppcheck lib32z1 clang clang-format clang-tidy gcovr doxygen libcmocka0 libcmocka-dev\n- lizard\n\nDepending on the architecture:\n\n- compiler (e.g. gcc-arm-none-eabi-9-2020-q2-update gcc-arm-none-eabi)\n- flashing tools\n- uC HAL and dependent files\n- much more....\n\n# Work environment\nYou can always change work environment between docker or native after project is created.\nJust edit the scargo.toml file ([project] -> build-env = \"docker\" or build-env = \"native\").\n\n## Working in docker\n1) If you create a new project, run `docker compose run scargo-dev` to run project development image depending on chosen architecture. All dependencies should be already there.\nRun scargo commands as you would do natively.\n\n2) If you create a project with --docker flag (`scargo new <my_proj> --docker ...`) or with any docker flag, by default each scargo command will be triggered in docker.\n\n## Working natively\n1) Create a project with --no-docker flag (`scargo new <my_proj> --no-docker ...`).\n\n## Testing custom scargo generated project locally\nYou can make changes in scargo and install it locally using ```pip install .``` command when you are in the main project folder.\nTo test the custom scargo version and have this custom scargo available also inside the docker (crucial for testing), in created project update docker-compose.yaml:\n\n volumes:\n\n - ..:/workspace\n - /dev:/dev\n - ~/.local/lib/python3.10/site-packages/scargo:/usr/local/lib/python3.8/dist-packages/scargo\n\nWhere ```~/.local/lib/python3.10/site-packages/scargo``` is a path to scargo on your local machine. It the following path is not working, find installation dir using ```pip show scargo```.\n\nTo keep this setup between ```scargo update``` commands, in scargo.toml file update also ```update-exclude``` as in following example:\n\n update-exclude = [\".devcontainer/docker-compose.yaml\"]\n# Contributing\n\nSee contributing guide on https://spyro-soft.github.io/scargo/contributing.html\n",
"bugtrack_url": null,
"license": null,
"summary": "C/C++ package and software development life cycle manager inspired by RUST cargo idea.",
"version": "2.3.0",
"project_urls": {
"Documentation": "https://spyro-soft.github.io/scargo/index.html",
"Source": "https://github.com/spyro-soft/scargo",
"Tracker": "https://github.com/Spyro-Soft/scargo/issues"
},
"split_keywords": [
"scargo",
" package manager",
" c++"
],
"urls": [
{
"comment_text": null,
"digests": {
"blake2b_256": "b1f761b0b012fa6256ca7d0dcc1fff0c99a316ccb3ee8697b5ded03835cec34e",
"md5": "ddf437f271f0d8fe725d52432b21093f",
"sha256": "1b13d212587c2ef6211bcf38adabf2df3c5cca4c4fea31276633a9ab061765df"
},
"downloads": -1,
"filename": "scargo-2.3.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "ddf437f271f0d8fe725d52432b21093f",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.8",
"size": 112490,
"upload_time": "2024-04-11T09:14:45",
"upload_time_iso_8601": "2024-04-11T09:14:45.120577Z",
"url": "https://files.pythonhosted.org/packages/b1/f7/61b0b012fa6256ca7d0dcc1fff0c99a316ccb3ee8697b5ded03835cec34e/scargo-2.3.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": null,
"digests": {
"blake2b_256": "56f53886b73f60720e8b75a4ea6f5dbe7bce3750f1e4955825bca5e476c3c2e8",
"md5": "8211336cd91930d9c1bb86a8468482eb",
"sha256": "b15c4bdf87354dd6162c65799f10c5c2e0f8b2f5c40e33e761b3ea7715d29d21"
},
"downloads": -1,
"filename": "scargo-2.3.0.tar.gz",
"has_sig": false,
"md5_digest": "8211336cd91930d9c1bb86a8468482eb",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.8",
"size": 77915,
"upload_time": "2024-04-11T09:15:03",
"upload_time_iso_8601": "2024-04-11T09:15:03.512082Z",
"url": "https://files.pythonhosted.org/packages/56/f5/3886b73f60720e8b75a4ea6f5dbe7bce3750f1e4955825bca5e476c3c2e8/scargo-2.3.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-04-11 09:15:03",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "spyro-soft",
"github_project": "scargo",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "scargo"
}
