|Description:||A project builder made easy for C/C++.|
|Build Scripts:||Coming soon...|
|License:||N/A | You are currently permitted to use, copy, modify, and redistribute the published executable binary files only, and any files generated by them.|
At the moment, CarePackage is just a raw binary file that your browser may or may not let you download. It is only available for Linux with Windows support in mind for the future.
The easiest way to install it is simply moving the cpkg executable into /usr/bin/ directory.
When it comes to installing cpr, clone the GitHub repository and run the following.
$ cmake .
$ make .
$ sudo make install
Alternatively, cpr is available on the AUR under the package name
Initializing a project
You can initialize a CarePackage project by running the following command.
$ cpkg init .
This will create a care.pkg file and a packages directory.
Currently the packages directory has no purpose, though that is planned to change in the future.
The care.pkg file is your project configuration file. The C and CC flags are your C and C++ compilers respectively - configured to work with the GNU C compiler flags (i.e. gcc/g++). For publishing purposes, it is recommended that you remove these flags as they will be automatically interpreted on the new system, or can be manually configured.
The only other flags you should worry about are your cflags (C), cppflags (C++), and linkflags (both). These are your respective compiler flags.
Building a project
It's super easy building a project. All you have to do is run the following after configuring your care.pkg file.
$ cpkg build .
This will generate a lot of object (.o) files that will then be linked together with your C++ compiler. These will not automatically be cleaned up after a successful build.
Cleaning a project
Cleaning a project is just as easy and building and initializing one. Again, just run the following command.
$ cpkg clean .
Note: This will recursively delete your build directory. There is a check to make sure it is not your current working directory, but you should not rely on this. It is recommended you designate a specific directory, like ./outDir/ for example, to place the build files.
MORE TO COME!
There is a lot more to come in CarePackage:
- Build Scripts - Automatically add/update/remove dependencies + automatically adjust build configuration. This will operate similarly to the AUR where a user creates a repository, and can designate a Build Script for a specific version of a dependency, or a generic Build Script for the latest stable version.
- Normal Scripts - Universal scripts to run specifically designed for project management.
- Open Source - Right now the project is not open-source. However, it should be released in the future.