) and the good thing is : wxWidgets brings these abstractions for many different platforms (Windows, Linux, Apple. ĬB uses wxWidgets, next to GUI abstraction, wxWidgets brings many more abstractions (strings, files, streams, sockets. This is provided by means of the MinGW port, more specifically the "mingwm10.dll", in every post announcing a new nightly build you can find a link to download this dll.ĬB has a GUI, there are several ways to create a GUI, you can code by using the core Windows API (works only on Windows) or you can use MS-MFC (works only on Windows) or you can use some 3rd party abstraction of GUI's, like QT, wxWidgets, Tk. Since CB is a multi-threaded application it needs supporting routines providing it the multi-threading functionalities. For example, you can plug-in the GCC compiler and GDB debugger and compile and debug your hand written applications.ĬB itself is being compiled with GCC, on windows this is done by using the MinGW port. However several of the mentioned development components can be combined to work together nicely through CB. So CB is NOT a compiler (nor MS, nor Borland, nor GCC), it is not a debugger (nor MS, nor GDB), it is not a makefile system ! So these components are NOT part of CB, and therefor they are also not part of the nightly build distributions. Well it's an IDE (Integrated Development Environment), it means it integrates different tools and makes them work together. For starters ask yourself the question : what is Code::Blocks ? īefore we describe what the builds contain, it might be better to start of with what the nightly builds DO NOT contain. Normally they are pretty stable, but however they can introduce new bugs, regressions, and on the other hand they can introduce new features, bug fixes.
They are "binary" distributions, normally provided daily, representing the latest and greatest state of the codeblocks sources.
0 kommentar(er)
