Dev-C++ is a free full-featured integrated development environment (IDE) distributed under the GNU General Public License for programming in C and C++. It is written in Delphi.

It is bundled with, and uses, the MinGW or TDM-GCC 64bit port of the GCC as its compiler. Dev-C++ can also be used in combination with Cygwin or any other GCC-based compiler.^[1]

This includes the entries in /dev/pts, which are console devices. This is why one is created for remote sessions; they are also created when you open a local GUI terminal. You can open them as files, although it's not of much use value. To get the /dev/pts node your shell is connected, use tty: tty /dev/pts/4 Now switch to some other console.

Dev-C++ is generally considered a Windows-only program, but there are attempts to create a Linux version: header files and path delimiters are switchable between platforms.

Devpaks[edit]

An additional aspect of Dev-C++ is its use of DevPaks: packaged extensions on the programming environment with additional libraries, templates, and utilities. DevPaks often contain, but are not limited to, GUI utilities, including popular toolkits such as GTK+, wxWidgets, and FLTK. Other DevPaks include libraries for more advanced function use. Users of Dev-C++ can download additional libraries, or packages of code that increase the scope and functionality of Dev-C++, such as graphics, compression, animation, sound support and many more. Users can create Devpaks and host them for free on the site. Also, they are not limited to use with Dev-C++ - the site says 'A typical devpak will work with any MinGW distribution (with any IDE for MinGW)'.

Development status[edit]

From February 22, 2005 to June 2011 the project was not noticeably active, with no news posted nor any updated versions released. In a 2006 forum post, lead developer Colin Laplace stated that he was busy with real-life issues and did not have time to continue development of Dev-C++.^[2]

There are two forks of Dev-C++ since then: wxDev-C++ and the Orwell version.

wxDev-C++ is a development team that has taken Dev-C++ and added new features such as support for multiple compilers and a RAD designer for wxWidgets applications.

On June 30, 2011 an unofficial version 4.9.9.3 of Dev-C++ was released by Orwell (Johan Mes), an independent programmer,^[3] featuring the more recent GCC 4.5.2 compiler, Windows' SDK resources (Win32 and D3D), numerous bugfixes, and improved stability. On August 27, after five years of officially being in a beta stage, version 5.0 was released.^[4] This version also has its own separate SourceForge^[5] page since version 5.0.0.5, because the old developer isn't responding to combining requests. On July 2014, Orwell Dev-C++ 5.7.1 was released featuring the more recent GCC 4.8.1 which supports C++11.

Notable uses[edit]

On May 4, 2015, The Singapore Prime Minister Lee Hsien Loong posted his Sudoku solver program in C++ on Facebook. In his screen shot, he's using Microsoft Windows and Dev-C++ as his IDE.^[6]

See also[edit]

References[edit]

1. ^'Bloodshed Software - Providing Free Software to the internet community'. bloodshed.net. Retrieved 8 September 2015.
2. ^'Dev-C++'. sourceforge.net. Retrieved 8 September 2015.
3. ^Orwell. 'Dev-C++ Blog'. orwelldevcpp.blogspot.com. Retrieved 8 September 2015.
4. ^Orwell. 'Dev-C++ Blog'. orwelldevcpp.blogspot.com. Retrieved 8 September 2015.
5. ^orwelldevcpp. 'Dev-C++'. SourceForge. Retrieved 8 September 2015.
6. ^'Prime Minister of Singapore shares his C++ code for Sudoku solver'. Ars Technica. Retrieved 8 September 2015.

External links[edit]

• Official website
• Dev-C++ on SourceForge.net
• Dev-C++ Portable on SourceForge.net

Tells the preprocessor to treat the contents of a specified file as if they appear in the source program at the point where the directive appears.

Syntax

#include 'path-spec'
#include <path-spec>

Remarks

You can organize constant and macro definitions into include files and then use #include directives to add them to any source file. Include files are also useful for incorporating declarations of external variables and complex data types. The types may be defined and named only once in an include file created for that purpose.

The path-spec is a file name that may optionally be preceded by a directory specification. The file name must name an existing file. The syntax of the path-spec depends on the operating system on which the program is compiled.

For information about how to reference assemblies in a C++ application that's compiled by using /clr, see #using.

Both syntax forms cause that directive to be replaced by the entire contents of the specified include file. The difference between the two forms is the order in which the preprocessor searches for header files when the path is incompletely specified. The following table shows the difference between the two syntax forms.

The preprocessor stops searching as soon as it finds a file that has the given name. If you enclose a complete, unambiguous path specification for the include file between double quotation marks (' '), the preprocessor searches only that path specification and ignores the standard directories.

If the file name that's enclosed in double quotation marks is an incomplete path specification, the preprocessor first searches the 'parent' file's directory. A parent file is the file that contains the #include directive. For example, if you include a file named file2 in a file named file1, file1 is the parent file.

Include files can be 'nested': An #include directive can appear in a file that's named by another #include directive. For example, file2 could include file3. In this case, file1 would still be the parent of file2, but it would be the 'grandparent' of file3.

When include files are nested and when compiling occurs on the command line, directory searching begins in the directories of the parent file. Then it proceeds through the directories of any grandparent files. That is, searching begins relative to the directory that contains the source that's currently being processed. If the file isn't found, the search moves to directories that are specified by the /I (Additional include directories) compiler option. Finally, the directories that are specified by the INCLUDE environment variable are searched.

From the Visual Studio development environment, the INCLUDE environment variable is ignored. For information about how to set the directories that are searched for include files and library files, see VC++ Directories Property Page.

This example shows file inclusion by using angle brackets:

This example adds the contents of the file named STDIO.H to the source program. The angle brackets cause the preprocessor to search the directories that are specified by the INCLUDE environment variable for STDIO.H, after it searches directories that are specified by the /I compiler option.

The next example shows file inclusion by using the quoted form:

This example adds the contents of the file that's specified by DEFS.H to the source program. The quotation marks mean that the preprocessor first searches the directory that contains the parent source file.

Nesting of include files can continue up to 10 levels. When the nested #include is processed, the preprocessor continues to insert the enclosing include file into the original source file.

Microsoft Specific

To locate includable source files, the preprocessor first searches the directories that are specified by the /I compiler option. If the /I option isn't present, or if it fails, the preprocessor uses the INCLUDE environment variable to find any include files within angle brackets. The INCLUDE environment variable and /I compiler option can contain multiple paths, separated by semicolons (;). If more than one directory appears as part of the /I option or within the INCLUDE environment variable, the preprocessor searches them in the order in which they appear.

For example, the command

causes the preprocessor to search the directory D:MSVCINCLUDE for include files such as STDIO.H. The commands

Dev C++ Themes

have the same effect. If both sets of searches fail, a fatal compiler error is generated.

Dev C++ 5.11

If the file name is fully specified for an include file that has a path that includes a colon (for example, F:MSVCSPECIALINCLTEST.H), the preprocessor follows the path.

For include files that are specified as #include 'path-spec', directory searching begins with the directory of the parent file and then proceeds through the directories of any grandparent files. That is, searching begins relative to the directory that contains the source file that contains the #include directive that's being processed. If there is no grandparent file and the file has not been found, the search continues as if the file name were enclosed in angle brackets.

Dev C Themes Youtube

END Microsoft Specific

See also

Dev C++ Them Essentials

Preprocessor directives
/I (Additional include directories)