OSDev.org

1) Compilers, translators ( C, ASM ).

DJGPP and NASM, I use Eclipse for my IDE with the CDT plugin for working with C/C++, its great and has built in support for CVS which works great as I use cvs on sourceforge.org

I also use binutils for DJGPP to build ELF binarys, and objdump them.

2) Loaders (self-written or third-party).

GRUB

3) PC Emulators.

VMWare and Bochs

4) PC Emulators.

Bochs debugger

5) Other tools

mtools to create my os disk image upon a new build.

CopperMan wrote:1) Compilers, translators ( C, ASM ).

gcc 3.4.1, nasm.

2) Loaders (self-written or third-party).

GRUB.

3) PC Emulators.

VMWare

4) Debuggers.

kprintf?

5) And any other tool types that I may miss.

GNU make for building, Doxygen, ConTEXT for editing, Perforce for change management, Poseidon UML for designing stuff. GNU tools all run in Cygwin. Everything runs on XP (but I also build on Linux).

GCC / binutils (GNU as) only. GRUB, Bochs, no debugger (adding screen output ad hoc). Oh, and make of course.

As for OpenWatcom, I recently got a "bug" report for PDCLib regarding OpenWatcom only accepting 8.3 file names. Show stopper right there.

Besides, the "big goal" is to port the toolchain to native sooner or later, so why bother with a compiler you don't have sources for?

Eh, by the name OpenWatcom I assume that the source is freely available?

edit:

The Open Watcom development team has released version 1.3. You can download the source and binaries here.

I stand corrected. Leaves the question why they're still stuck with 8.3 naming...

Solar wrote: I stand corrected. Leaves the question why they're still stuck with 8.3 naming...

"Let's assume a 12-byte buffer for all filenames in every bit of the program. Nobody's ever going to need more than 8.3."

I guess that should sum it up.

I guess that they have to few developers, and that most people settle for GCC *yuck* and don't even look for something else..

It doesn't have to be good, as long as you're with the majority in using it. Windows, GCC, GPL, eBay, PayPal, Google... can't go wrong by swimming with the stream. :-[

CopperMan wrote:1) Compilers, translators ( C, ASM ).

1. NASM, might be going YASM in the future....

2) Loaders (self-written or third-party).

2. Self-written loader (0.02)

3) PC Emulators.

3. Bochs

4) Debuggers.

4. I just dump everything to screen, if I want to... but I'm planning of having a kernel-debugger (you know, a little shell which can dump the registers' value)..

5) And any other tool types that I may miss.

5. No other tools, except dd/rawwritewin and my compile script.

It doesn't have to be good, as long as you're with the majority in using it. Windows, GCC, GPL, eBay, PayPal, Google...

This especially seems to be the case with Windows. Google for example has proven to be one of the better search engines (IMHO). I almost never visit eBay as well.. don't use GPL as license for my projects (non)..

I'm just the type of person who ignores the mainstream and finds alternatives... prolly the reason why I use NetBSD for one of my computers instead of Linux ;D .

I'm just the type of person who ignores the mainstream and finds alternatives... prolly the reason why I use NetBSD for one of my computers instead of Linux ;D .

I think we are all like you DennisCGc, thats why we are making our own OS's .

Again about OpenWatcom C/C++.

Last released version does'nt support AMD64 platform !
This is a main reason why i'am use GCC.
( In past I was using OpenWatcom )

CopperMan wrote: 1) Compilers, translators ( C, ASM ).
2) Loaders (self-written or third-party).
3) PC Emulators.
4) Debuggers.
5) And any other tool types that I may miss.

1. fasm
2. self-written
3. Bochs
4. jmp $
5. texteditor, test-PC and some freetime

1) Compilers, translators ( C, ASM ).

GCC 4.02, LD 2.16.91.2
LCC 3.6 (soon 4.0), ldrdf
NASM 0.9X
specially written driver compilation tool

2) Loaders (self-written or third-party).

I use GRUB to load my OS, as of late.
The kernel has an RDOFF2 object loader (soon ELF)

3) PC Emulators.

qemu, mostly

4) Debuggers.

stack trace printout upon every exception + addr2line

5) And any other tool types that I may miss.

CVS + cervisa for version management
kate/kwrite for editing
ant for compilation
rdf tools to inspect driver objects

1) Compilers, translators ( C, ASM ).

GCC, NASM, LD

2) Loaders (self-written or third-party).

GRUB

3) PC Emulators.

What's that?

4) Debuggers.

kprintf();

5) And any other tool types that I may miss.

My dev tools are on a machine with Zipslack (slackware mini-distro), and I use BASH scripts extensively to build my OS.

1) Compilers, translators ( C, ASM ).

GCC, NASM, LD

2) Loaders (self-written or third-party).

kinda self written - my own code patched together with other various bits and peices

3) PC Emulators.

Bochs

4) Debuggers.

bochs debugger, and output (not that experienced yet though). And the good old 'cli'+'hlt' to help trace errors.

5) And any other tool types that I may miss.

I use dev-cpp for c and c++ editing, on windows. Also I use notepad for most other files, or dev-cpp when I need line numbers.

I use make to build my OS, dos 'debug' command to write bootloader to disk, and also a tool named 'image' to grab an image from a disk.