What OS and programming enviroment do you use?

[mystran]

The operating system is irrelevant as long as it can run firefox, vim, xchat, gcc, gdb, make, bash, grep, sed, awk, python&perl, at least one scheme-interpreter and one common lisp interpreter, man, info, valgrind (check this out, it rules the world), cvs and apache (for viewcvs, which is nicer for figuring out stuff) and php/postgresql (for my home-made not-yet-released bug-manager).

X11 and evilwm also need to be supported, and I'd prefer GNU versions of grep/sed/awk. Gimp is a plus.

What?

[Solar]

Re: cross-compiler... it's not only the PE format, in fact I strongly recommend building a cross-compiler on Linux/x86, too.

For one, your system compiler "knows" many things that it shouldn't: It knows standard include files, which you don't have available for your kernel. In knows about C runtime, which applies to your host OS but not the OS you're developing for. It knows about OS-specific stuff (like alloca()) that likewise doesn't apply to your hobby OS. Building a cross-compiler helps to get warnings early instead of wondering why it doesn't work this time.

The other reason is that, sooner or later, you'll have a kernel, a C library and a C runtime for your OS, and at that point you'll likely want to continue your cross-compiler setup to the point where you can compile applications for your hobby OS. Yet later, you'll want to bootstrap a native GCC. The

The cross-compiler described in the Wiki is a logical first step.

Thanks for the compliments on the Wiki page (*bows*, *points-to-Candy-who-wrote-the-AMD64-part*), and nice to see another DOpus user around.

[Candy]

For one, your system compiler "knows" many things that it shouldn't: It knows standard include files, which you don't have available for your kernel. In knows about C runtime, which applies to your host OS but not the OS you're developing for. It knows about OS-specific stuff (like alloca()) that likewise doesn't apply to your hobby OS. Building a cross-compiler helps to get warnings early instead of wondering why it doesn't work this time.

For Linux systems you can even get quite far without a cross compiler. However, as you will want to make programs for your OS conform to your memory ideas, you will need to make a new GCC that outputs your programs as default..

Solar, do you know how to make a new default target output with default flags? Possibly permanently using a selfmade link file?

Thanks for the compliments on the Wiki page (*bows*, *points-to-Candy-who-wrote-the-AMD64-part*), and nice to see another DOpus user around.

*bows* *points to Solar who did all the rest*

[Solar]

(Answering Candy by private message as it's OT.)

[Al]

I personally use the following:

2 computers: 1 development 1 test
Visual Studio .NET as my editor, running on WinXP
GCC compiler, along with make
partcopy

I suppose it would be even easier for me if I was not to lazy to add all of my OS files to a VS project so IntelliSense would work, and remind me when I typed something wrong, which I always do, but...

My development PC is as cheap as you can get, an old 200 MHZ processor, a floppy drive, the worst keyboard and mouse I could find

The GCC compiler I use is DJGPP

It works great, but I wish I did not have to make my own makefile, it gets annoying.

[jinksys]

I use SuSE 9.1, been using SuSE since version 7. I do have
WIN2000 installed, although its not for kerneling, just for
UT2004 level design . I use the GCC toolchain for development, GAS for assembly, GCC for C/C++. I also use
Bochs for testing my OS.

[srg_13]

I use Visual C++ 6.0, GCC, NASM and PARTCOPY to compile my OS, under Windows XP. I find Windows XP to be both user-friendly and stable (unlike win98).

I use bochs to test my OS.

[glow=green,2,300]Stephen [/glow]

[Legend]

I switched from Linux (SuSe Linux Professional 8.0 afaik) to Windows XP with Visual C++ 6.0 as the IDE and DJGPP as the compiler.
Next step would be Eclipse/DJGPP, however, planned then is either DevC++/DJGPP (if this somehow may work someday) or DevC++/MinGW (if this works somehow for other reasons )

[mystran]

I never really understood the IDEs. At some point I tried to work with Visual Studio, but quite fast switched to a setup using Visual Studio only to compile and debug, and editing the code in ViM instead.

Every IDE has I've seen has so bad editor that it's not even funny. Most don't even support basic regular expressions.

[Legend]

On the contrary I avoid vi + similiar editors where I can.
I can live without any regular expression if I get an easy accessiable (obvious I mean) simple find/replace.

And where I don't have to switch between insert and normal mode to edit and remove a line that I inserted by accident.

To summarize it, I prefer notepad.exe over vi(m)

EDIT: And on a ssh-shell joe over vi

[AxelDominatoR]

Mmm...
Gentoo linux
GNU Nano
GNU utilities
Hexedit to modify binaries...
and that's all!

[Gnome]

I told myself I wouldn't reply to this... but here I am.

Here's a screenshot of a typical coding session: http://flyswatter.dyndns.org/~michael/screenshot.png.

That's Gentoo Linux, with Enlightenment for the window manager, Eterm for the terminal, and ViM for the editor. My source tree uses Arch (recently switched) for source control, and the GNU build system (Autoconf, Automake, etc.).

One thing the screenshot doesn't show (that I've hidden with terminals) is that there are RSS feeds and system logs plastered all over the background in the form of gDesklets and xrootconsoles.

Note the pager in the bottom left: that's 8 workspaces. I often use at least 6 of them, the left one is used for IRC (XChat) and IM (Gaim), the following one normally for reference or conversation windows, the third one for coding, the forth for more reference, web browsing, or more coding. The remaining ones are for various stuff.

[NetBSD-User]

I use NetBSD because it's fast, clean, and the most stable system I have ever used. Toolchain: GNU. Bootloader: GRUB. (There's no way I'm ever gonna bother to write a freakin' bootloader.

[chris]

Nice to see another NetBSD user ..

[Arto]

Here's a screenshot of a typical coding session: http://flyswatter.dyndns.org/~michael/screenshot.png.

That's Gentoo Linux, with Enlightenment for the window manager, Eterm for the terminal, and ViM for the editor. My source tree uses Arch (recently switched) for source control, and the GNU build system (Autoconf, Automake, etc.).

Very slick Since DR16.7.1 was released, I've been thinking of trying out Enlightenment. Well, here goes, "emerge enlightenment"... ;D