Re: What's your toolchain
Posted: Fri May 08, 2009 1:02 am
No. I think a majority of people probably use one.Tomaka17 wrote:Am I the only one using an emulator for O/S developpment?
When I want to work on my project I use VirtualBox to start a text-mode Debian virtual machine which contains all the stuff for compilation (GCC, binutils, etc.)
...and I edit the sourcecode on Windows with SciTE
This is what I'd expect in a tool chain:
Preprocessor
Compilers
Assembler
Linker
Librarian
grep
touch
make
Debugger
Profiler
Debug Info Stripper
Binary Dumper (Borland tdump, Microsoft dumpbin)
Relatively Compulsory Tools for Windows Development:
Resource Compiler (rc, brc/brc32)
IDL Compiler (midl)
Import Librarian (i.e. implib)
ImpDef
Archiving Tool (cabarc)
Sometimes a DOS Extender, esp. if you are working with a DOS clone like FreeDOS. OpenWatcom packages DOS Extenders as part of its tool chain. Digital Mars also, but you have to download it from another page not on their website (X32).
Editors and IDEs are convenience tools to me. I hardly work strictly from the command-line (because mastering a particular toolchain - no matter which - takes more than a few hours), but that's still what I consider them.
Borland used to have a totally complete tool chain (many clones of common Unix tools like grep and touch). Microsoft overtook them, though, or at least caught up.
GNU, obviously, has a complete toolchain suitable for OSDev.
All that other stuff is Fluff to me - including Virtual Machine Emulators. However, they are useful; and, you should use whatever helps!
I do think piling on tools on top of tools (many of which not made to work with other toolchains) adds unneded complexity, especially for a rookie developer of any type.