Fede.tft: Created page with "= IDEs = Miosix does not require any specific IDE, so you can pick the one you prefer, so long as it supports the C/C++ languages and supports building with either make or CMake. If possible, try to configure your IDE so that it '''does not''' automatically add ''#include'' directives while coding, as it often causes issues with IDEs automatically including wrong headers. This happens because Miosix supports multiple architectures and thus the implementation of chip- a..."

2026-05-09T14:42:53Z

Created page with "= IDEs = Miosix does not require any specific IDE, so you can pick the one you prefer, so long as it supports the C/C++ languages and supports building with either make or CMake. If possible, try to configure your IDE so that it '''does not''' automatically add ''#include'' directives while coding, as it often causes issues with IDEs automatically including wrong headers. This happens because Miosix supports multiple architectures and thus the implementation of chip- a..."

New page

= IDEs =

Miosix does not require any specific IDE, so you can pick the one you prefer, so long as it supports the C/C++ languages and supports building with either make or CMake.

If possible, try to configure your IDE so that it '''does not''' automatically add ''#include'' directives while coding, as it often causes issues with IDEs automatically including wrong headers. This happens because Miosix supports multiple architectures and thus the implementation of chip- and board-specific functions occurs multiple times in the Miosix source tree, a matter which confuses IDEs and sometimes makes them include the wrong headers.
Moreover, IDEs usually don't understand that some headers should be accessed from application code through the headers in the ''miosix/interfaces'' directory instead of directly including a header of a specific board.

Development of Miosix (and of applications using Miosix) can also be done with just a plain text editor and a terminal to call make/CMake and git. This is the current choice of the Miosix core developers.

Following is a list of contributions by Miosix users sharing suggestions about specific IDEs.

== Visual Studio Code ==

Visual Studio Code is known to work properly on the Miosix source tree with the standard C/C++ and Makefile extensions. After installing these extensions, you need to configure IntelliSense in the C/C++ extension to use the include paths found from the Makefile by setting the ''Configuration provider'' for the workspace to <code>ms-vscode.makefile-tools</code>.

Integration with GDB/openocd has not been tested but you can run GDB/openocd manually in the integrated terminal.

== Netbeans IDE ==

Many years ago, Miosix used to include project files for Netbeans, as this was the IDE used by Miosix core developers at the time. Unfortunately, when Netbeans switched from being a Sun product to an Apache project, support for C/C++ became less maintained, and netbeans project files were removed from the Miosix source tree.

These old pages are kept for reference, but are known to be outdated.

* [[Linux Netbeans configuration]]
* [[Windows Netbeans configuration]]

== Other IDEs ==

* [[VisualStudio Quick Start|Windows Visual Studio configuration]] using VisualGDB which integrates in-circuit debugging support.
* [[Linux Eclipse configuration|Eclipse]], which has the added feature to allow in-circuit debugging directly from the IDE.
* [[Linux QtCreator configuration]]
* [[Windows QtCreator configuration]]

[[Category:Installation and Configuration]]

IDEs - Revision history