This page collects information on platforms (operating systems), compilers andsource code languages that are supported by the latest released ccacheversion, currently 3.7.9. The information below aims to becorrect, but new versions of e.g. an OS or a compiler may introduce newbehavior that breaks some of ccache's assumptions.
If you want to contribute with new or updated information, pleaseopen anissue or maybe even create a pull request forthe web siterepository.
Support levels
| Level | Description |
|---|---|
| A | Supported. Built and tested regularly and before new releases. Highattention to bug reports. |
| B | Probably works, may work or is partially supported. Not part of the testprocedure before a new release. Bug fixing and testing largely depend oncontributions from the community. |
| C | Not supported. |
Run-time support (i.e., using ccache)
Nov 29, 2016 Delphi is the ultimate IDE for creating cross-platform, natively compiled apps. Are you ready to design the best UIs of your life? Our award winning VCL framework for Windows and FireMonkey (FMX) visual framework for cross-platform UIs provide you with the foundation for intuitive, beautiful.
Platforms
| Level | Platform | Notes |
|---|---|---|
| A | Linux (GNU/Linux) | Regularly tested on Ubuntu 16.04 and 19.10. |
| A | macOS (OS X) | Regularly tested on thecurrent macOSversion supported by Travis CI. |
| B | Other Unix-like platforms | See also the ccachepage on Repology. |
| B | Windows with MSYS2 | |
| B | Windows native | Regularly built with Mingw-w64 but notregularly tested. However, it seems to work quite well in practiceaccording to users. |
Want to add or correct something?Open anissue.
Compilers
| Level | Compiler | Notes |
|---|---|---|
| A | GCC | |
| A | Clang | Not clang-cl,though. |
| A | NVCC(Nvidia CUDA compiler) | |
| B | ICC (Intel C++compiler) | |
| B | Other GCC-like compilers | |
| C | EDG-based,e.g. GHS (GreenHills) | Will get B-level support in ccache 4.0. See issue#460. |
| C | MSVC (Microsoft VisualC++) | May get partial B-level support in ccache 4.0. See pull request#506. |
| C | clang-cl(MSVC compatibility for Clang) |
Want to add or correct something?Open anissue.
Source code languages
| Level | Language | Notes |
|---|---|---|
| A | Assembler (.s, .sx, .S) | .sx and .S are assembler with a C preprocessorpass. |
| A | C (.c) | |
| A | C header (.h) | For precompilation. |
| A | C preprocessed (.i) | |
| A | C++(.cc, .cpp, .cp, .cxx,.c++, .C) | Also uppercase variants of extensions. |
| A | C++ header(.hh, .hpp, .hp, .hxx,.h++, .H) | For precompilation. Also uppercase variants of extensions. |
| A | C++ preprocessed(.ii) | |
| A | CUDA(.cu) | |
| B | Objective-C (.m) | |
| B | Objective-C preprocessed (.mi) | |
| B | Objective-C++ (.mm, .M) | |
| B | Objective-C++ preprocessed (.mii) | |
| C | CUDA header(.cuh) |
Want to add or correct something?Open anissue.
Build-time support (i.e., building ccache itself)
Building ccache requires a C99-compliant compiler such as GCC or Clang.
Platforms
| Level | Platform | Notes |
|---|---|---|
| A | Linux (GNU/Linux) | Regularly tested on Ubuntu 16.04 and 19.10. |
| A | macOS (OS X) | Regularly tested on thecurrent macOSversion supported by Travis CI. |
| B | Other Unix-like platforms | See also the ccachepage on Repology. |
| B | Windows with MSYS2 | |
| B | Windows native with Mingw-w64 | Regularly built. |
| C | Windows native withMSVC (Microsoft VisualC++) |
Want to add or correct something?Open anissue.
Compilers
| Level | Compiler | Notes |
|---|---|---|
| A | GCC | GCC 4.8.5+ |
| A | Clang | |
| B | Other C++-11 compilers on Unix-like systems | |
| C | MSVC (Microsoft VisualC++) |
Want to add or correct something?Open anissue.
What is Dev-C++?
Dev-C++, developed by Bloodshed Software, is a fully featured graphical IDE (Integrated Development Environment), which is able to create Windows or console-based C/C++ programs using the MinGW compiler system. MinGW (Minimalist GNU* for Windows) uses GCC (the GNU g++ compiler collection), which is essentially the same compiler system that is in Cygwin (the unix environment program for Windows) and most versions of Linux. There are, however, differences between Cygwin and MinGW; link to Differences between Cygwin and MinGW for more information.
Bloodshed!?
I'll be the first to say that the name Bloodshed won't give you warm and fuzzies, but I think it's best if the creator of Bloodshed explains:
There's also a reason why I keep the Bloodshed name. I don't want people to think Bloodshed is a company, because it isn't. I'm just doing this to help people.
Here is a good remark on the Bloodshed name I received from JohnS:
I assumed that this was a reference to the time and effort it requires of you to make these nice software programs, a la 'Blood, Sweat and Tears'.
Peace and freedom,
Colin Laplace
Getting Dev-C++
The author has released Dev-C++ as free software (under GPL) but also offers a CD for purchase which can contain all Bloodshed software (it's customizable), including Dev-C++ with all updates/patches.
Link to Bloodshed Dev-C++ for a list of Dev-C++ download sites.
You should let the installer put Dev-C++ in the default directory of C:Dev-Cpp, as it will make it easier to later install add-ons or upgrades.
Using Dev-C++
This section is probably why you are here.
All programming done for CSCI-2025 will require separate compilation projects (i.e. class header file(s), class implementation file(s) and a main/application/client/driver file). This process is relatively easy as long as you know what Dev-C++ requires to do this. In this page you will be given instructions using the Project menu choice. In another handout you will be given instructions on how to manually compile, link and execute C++ files at the command prompt of a command window. See here.
Step 1: Configure Dev-C++.
We need to modify one of the default settings to allow you to use the debugger with your programs.
- Go to the 'Tools' menu and select 'Compiler Options'.
- In the 'Settings' tab, click on 'Linker' in the left panel, and change 'Generate debugging information' to 'Yes':
- Click 'OK'.
Step 2: Create a new project.
A 'project' can be considered as a container that is used to store all the elements that are required to compile a program.
- Go to the 'File' menu and select 'New', 'Project...'.
- Choose 'Empty Project' and make sure 'C++ project' is selected.
Here you will also give your project a name. You can give your project any valid filename, but keep in mind that the name of your project will also be the name of your final executable. - Once you have entered a name for your project, click 'OK'.
- Dev-C++ will now ask you where to save your project.
Step 3: Create/add source file(s).
You can add empty source files one of two ways:
- Go to the 'File' menu and select 'New Source File' (or just press CTRL+N) OR
- Go to the 'Project' menu and select 'New File'.
Note that Dev-C++ will not ask for a filename for any new source file until you attempt to:- Compile
- Save the project
- Save the source file
- Exit Dev-C++
- Go to the 'Project' menu and select 'Add to Project' OR
- Right-click on the project name in the left-hand panel and select 'Add to Project'.
| EXAMPLE: Multiple source files In this example, more than 3 files are required to compile the program; The 'driver.cpp' file references 'Deque.h' (which requires 'Deque.cpp') and 'Deque.cpp' references 'Queue.h' (which requires 'Queue.cpp'). |
Step 4: Compile.
Once you have entered all of your source code, you are ready to compile.
- Go to the 'Execute' menu and select 'Compile' (or just press CTRL+F9).
It is likely that you will get some kind of compiler or linker error the first time you attempt to compile a project. Syntax errors will be displayed in the 'Compiler' tab at the bottom of the screen. You can double-click on any error to take you to the place in the source code where it occurred. The 'Linker' tab will flash if there are any linker errors. Linker errors are generally the result of syntax errors not allowing one of the files to compile.
'. At this point, you may click 'Close'. Step 5: Execute.
You can now run your program.
- Go to the 'Execute' menu, choose 'Run'.
Disappearing windows
If you execute your program (with or without parameters), you may notice something peculiar; a console window will pop up, flash some text and disappear. The problem is that, if directly executed, console program windows close after the program exits. You can solve this problem one of two ways:
- Method 1 - Adding one library call:
On the line before the main's return enter:system('Pause');
- Method 2 - Scaffolding:
Add the following code before any return statement in main() or any exit() or abort() statement (in any function):/* Scaffolding code for testing purposes */
This will give you a chance to view any output before the program terminates and the window closes.
cin.ignore(256, 'n');
cout << 'Press ENTER to continue...'<< endl;
cin.get();
/* End Scaffolding */ - Method 3 - Command-prompt:
Alternatively, instead of using Dev-C++ to invoke your program, you can just open an MS-DOS Prompt, go to the directory where your program was compiled (i.e. where you saved the project) and enter the program name (along with any parameters). The command-prompt window will not close when the program terminates.
For what it's worth, I use the command-line method.
Step 6: Debug.
When things aren't happening the way you planned, a source-level debugger can be a great tool in determining what really is going on. Dev-C++'s basic debugger functions are controlled via the 'Debug' tab at the bottom of the screen; more advanced functions are available in the 'Debug' menu.
Using the debugger:
The various features of the debugger are pretty obvious. Click the 'Run to cursor' icon to run your program and pause at the current source code cursor location; Click 'Next Step' to step through the code; Click 'Add Watch' to monitor variables.
Setting breakpoints is as easy as clicking in the black space next to the line in the source code.
See the Dev-C++ help topic 'Debugging Your Program' for more information.
Dev C++ Work With G++ Compiler Download
Dev-C++ User F.A.Q.
Why do I keep getting errors about 'cout', 'cin', and 'endl' being undeclared?
It has to do with namespaces. You need to add the following line after the includes of your implementation (.cpp) files:
How do I use the C++ string class?
Again, it probably has to do with namespaces. First of all, make sure you '#include <string>' (not string.h). Next, make sure you add 'using namespace std;' after your includes.
Example:
That's it for now.I am not a Dev-C++ expert by any means (in fact, I do not teach C++ nor use it on a regular basis), but if you have any questions, feel free to email me at jaime@cs.uno.edu
Dev C++ Gcc Compiler
Happy coding!