https://github.com/bezarhere/hivec
Deploying your library should be no more then a post-build command
https://github.com/bezarhere/hivec
build-tool c command-line cplusplus cpp open-source opensource
Last synced: about 2 months ago
JSON representation
Deploying your library should be no more then a post-build command
- Host: GitHub
- URL: https://github.com/bezarhere/hivec
- Owner: BezarHere
- Created: 2023-09-09T09:35:55.000Z (almost 3 years ago)
- Default Branch: master
- Last Pushed: 2023-10-15T16:19:11.000Z (over 2 years ago)
- Last Synced: 2025-10-10T06:35:45.579Z (9 months ago)
- Topics: build-tool, c, command-line, cplusplus, cpp, open-source, opensource
- Language: Python
- Homepage:
- Size: 52.7 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: readme.md
Awesome Lists containing this project
README
# HiveCpp
### summary:
A compacted library of variouse tools, useful (at least for me)
### HOW to use
---
### | from the command line you use `py -m hivecpp [, /f, /c] `
if the switch `/f` is used, then all laters arguments should be paths to argument files. this is the only way to execute batch-like builds with multible argument files
otherwise, if the switch `/c` is used or if no switch is used at all, then all the build arguments should be passed into the command line, at the place of ``
EX for the first method:
```
C:\Users\James>py -m hivecpp /f my_args.args
```
the `my_args.args` path is reletive, so it's more like `C:\Users\James\my_args.args`
then you have in your `my_args.args` file (*read the coments*):
```cmake
# the args file supports comments!
# smart argument reading!
# but not single qouts :(
# the project path
project "C:\Users\James\Desktop\MyProject"
# the source folder, '__proj__' will be replaced by the 'project' path
source "__proj__\src"
# the output for all headers in the source folder
output "C:\Users\James\Documents\MyLib\include"
# defining a macro with name 'lib_folder' that will replace every '__lib_folder__'
define:lib_folder "C:\Users\James\Documents\MyLib"
# copy operation, '/o' at the end so it will overwrite the destination
copy # Arguemnts can be passed one or more values at one line
"__proj__\output\my_lib.lib" "__lib_folder__\lib\lib-64.lib"
/o # this will be parsed as a part of copy
# delete operation (not sure if it will be moved to the trashbin or completly erased)
delete "__proj__\temp"
# adds a new files type to be treated like a header, e.g. copied to the source_output
include_file_type "bat"
```
### i want the second method, to pass all arguments into the command line!
**Firstly**: just why? it's much cleaner to use a hive args file
**Secondly**: Alrigh, you can pass arguments to the command line, just remove the comments and replace every new line with a space to make the entire file as *one* line (you might need to add `/c` as the first argument)
## Why not CMake?
hivecpp is smaller and easier, given you have (wich most of you have) python installed
# FAQs
### Why can't this be a standalone executable?
becuse a value a transparent script that hides nothing, **but** if you wanted a standalone executable, just make it, there is a lot of tools that can convert a python script(s) to a standalone executable *and don't violate my copyright/licence*
### Where there be support for more languages?
Hopefuly, [contact me](https:\\tweeter.org\BotatoDev) if you want to contribute something
open source doesn't mean open to *all* contributions, any random merge requests will not be accepted.
---
*god bless*