OSDev.org

People say there is no IDE for OS development.
So I'm gonna make one.
You can write code in it and compile it to a .bin file.
I can't do more yet.

This is the one that I use. [Link]

If that doesn't suit you, there's always one from a long list here.

syntropy wrote:This is the one that I use. [Link]

If that doesn't suit you, there's always one from a long list here.

IDE dousn't means only a editor and highlighter.
An IDE includes the linker, compiler, project maneger ...
And the download link for windows is broken.
[edit]pfffffff, I worked on it for 10 minutes and I'm already borred...[edit]

Axalto wrote:

syntropy wrote:This is the one that I use. [Link]

If that doesn't suit you, there's always one from a long list here.

IDE dousn't means only a editor and highlighter.
An IDE includes the linker, compiler, project maneger ...
And the download link for windows is broken.
[edit]pfffffff, I worked on it for 10 minutes and I'm already borred...[edit]

Quote the birth
Doth flame burns bright
Turns all to ashes
Far too soon.

I find that any system with a compiler by itself works almost like an IDE. You just need to put a good text editor next to a terminal emulator and you can do anything. Makefiles make a very nice and portable automatic build system as well.

I am pretty sure anything you make quickly could not even come close to the features of Notepad++, if so, then it is only a copy.

Axalto wrote:IDE dousn't means only a editor and highlighter.
An IDE includes the linker, compiler,

:make

Axalto wrote: project maneger ...

http://www.vim.org/scripts/script.php?script_id=69

Axalto wrote: And the download link for windows is broken.

No it isn't.

Also, scriptability, indentation rules, and split windows are just some of the extra features that makes my life liveable.

<3 VIM, it's those eight extra KILOBYTES you just need.

People say there is no IDE for OS development.

There is alot of IDEs that can be used. Not sure where you got the information that there is no IDE available from. I use MSVC++ 2008 myself (Compiler, Linker, and editor+highlighter before you say anything...)

I used to use Dev-C++ and that worked just fine for me. I don't use it anymore because I thought writing my own makefiles would be more portable. It did work out for me, though. People on this forum have mentioned using a lot more than the 3 ones we just did. Basically, any IDE could be used if it is a bit configurable.

I just stick with GEdit with a terminal window open next to it. GEdit is great and all, but I wish I could figure out how to get NASM-syntax highlighting... or at least some sort of customizable highlighting.

01000101 wrote:I just stick with GEdit with a terminal window open next to it. GEdit is great and all, but I wish I could figure out how to get NASM-syntax highlighting... or at least some sort of customizable highlighting.

KDE's equivalent Kate has easily customisable highlighting - it's also an excellent text editor. I use it when I'm not using emacs. You should have a look at it - it's gedit-like so may tick all of your boxes.

01000101 wrote:I just stick with GEdit with a terminal window open next to it. GEdit is great and all, but I wish I could figure out how to get NASM-syntax highlighting... or at least some sort of customizable highlighting.

Use MASM-syntax as base, and edit it. Just change the assigned file extensions (add .s and .S)

I use Code::Blocks with GCC, LD, make, nasm and a terminal

// PHP

01000101 wrote:I just stick with GEdit with a terminal window open next to it. GEdit is great and all, but I wish I could figure out how to get NASM-syntax highlighting... or at least some sort of customizable highlighting.

Ditto. I had to compile a new version of GTK and compile GEdit to get it onto xubuntu (xfce, not gnome) but I use it for all things OSdev on Linux. Otherwise it's VC++ and a command prompt!

If anyone wants it, I've made two assembly syntax-highlighting .lang files for GEdit (Intel and ATT syntax). I'm sure they're very incomplete, but they give the building blocks to anyone that wants to add more features later.

*.s/S files use asm-att.lang by default and *.asm files use asm-intel.lang by default.

Instructions: Change the file extensions from .txt to .lang. Then (in Ubuntu at least) move those files into /usr/share/gtksouceview*.0/language-specs/ (with * being the highest version number you have). Then the next time you open an assembly file it should auto-detect and use them.

:Warning: I haven't tested the ATT-syntax one very much (as most of my code is for NASM). Feedback and fixes are very much welcome!

01000101 wrote:I'm sure they're very incomplete, but they give the building blocks to anyone that wants to add more features later.

Just did some awk/sed magic on Wikipedia's x86 instruction list, and it now highlights instructions.