Cwc is a front-end C++ compiler made for programmers who want to make their life easier.
It use a straightforward language -> command line injection
It can be used as a direct replacement for GCC or Clang.
Say goodbye to the huge mess of C++ compilation. This tool will become your best friend !
It can be seen as a smart compiler, easy to use with many additions. It can be connected to any IDE and enjoy of all its features.
Cwc, is not a compiler in itself, like a chameleon, it redirects inputs / outputs with any back-end compiler.
The main principle is to send several commands simultaneously, with the following separators:
| : Allows you to send commands simultaneously in multi-process. The output is guaranteed to be in the same order,
so it's always the same result that is displayed
>: To make sequences, when it's necessary to wait for previous orders
So we can do something like "buildObj | buildObj > Link"
Example: "-c Src1.cpp -o Src1.o | -c Src2.cpp -o Src2.o > -o App.exe Src1.o Src2.o"
All backend compiler or lib that is required for a project will be automatically downloaded and will have its own compilation toolchain and arguments
To speed up the compilation it is important not to recompile the already created object files. Many IDEs are unable to correctly detect changes (which file depends on which) and often result in an erroneous executable, some of which has not been up to date, causing serious errors that are difficult to pinpoint.
Cwc has a concrete detection, it checks all the dependencies of each file, it also checks for file change as well as any change of command line. A command like "clean" is thus practically obsolete.
It is possible to send a whole directory in one command line. It will process all the files inside, which greatly simplify the command list.
We can insert variables in our commands, using braces {} There are a lot of build-in vars to simplify compilation processs like the build type (x86, x64, Debug, O2, O3) which requires different folder.
Connect to DrMemory, you can comb through all possible memory errors.
Cwc use the universal DBGP common Debugger prorotocol.
So you can debug in your prefered IDE, see the notepad++ plugin: DBGpPluginMx
GDB interaction, auto-loading symboles (sending a SIGINT / switching thread / show backtrace)
Cwc can export binary files to any platform without any modification of your makefile or your code
Here are the supported toolchains for now:
| Toolchain | From | Target |
|---|---|---|
| LibRT | Windows | Windows, Linux |
| WebRT | Windows | Web (Wasm/JS) |
| Droid | Windows | Android |
| DJGPP_RT | Windows | DOS / OSdev |
| Elf_RT | Windows | Linux / OSdev |
| PS2_RT | Windows | PS2 |
Any other custom toolchain can be added easily with a Github repo, possibilities are limitless.
See the wiki:
See some demos: