Is not a standard header. Most commonly it refers to the header for Borland's BGI API for DOS and is antiquated at best. However it is nicely simple; there is a Win32 implementation of the BGI interface called. It is implemented using Win32 GDI calls - the lowest level Windows graphics interface. As it is provided as source code, it is perhaps a simple way of understanding how GDI works. WinBGIm however is by no means cross-platform.
There is a modern port for this Turbo C graphics interface, it's called WinBGIM, which emulates BGI graphics under MinGW/GCC. I haven't it tried but it looks promising. [graphics.h] appears to something once bundled with Borland and/or Turbo C++, in the 90's. Generally we run graphics program in Turbo C on windows platform. If you are addicted to gcc compiler then it is not providing inbuilt facility to run graphics.h library. So you are not able to run graphics in C language, to run 'graphics.h' library in Ubuntu, following are some simple steps. Turbo C, followed by Turbo C++, was a popular compiler in the late eighties and early nineties. Version 3.0, with Windows compatibility, was released in 1991. Although other versions followed, Turbo 3.0 was almost universally considered to be the most stable - always an important consideration when programming!
If all you want are simple graphics primitives, most of the higher level GUI libraries such as wxWidgets and Qt support that too. There are simpler libraries suggested in the possible duplicate answers mentioned in the comments. There is a modern port for this Turbo C graphics interface, it's called, which emulates BGI graphics under MinGW/GCC. I haven't it tried but it looks promising.
Declaration Of Graphics.h In Turbo C
Graphics.h In Turbo C For Mac Free
For example creates a window, and from this point you can draw into that window using the good old functions, at the end deletes the window. It also has some more advanced extensions (eg.
Mouse handling and double buffering). When I first moved from DOS programming to Windows I didn't have internet, and I begged for something simple like this. But at the end I had to learn how to create windows and how to handle events and use device contexts from the offline help of the Windows SDK.