OSDEV IN WINDOWS?

01000101 · Post by **01000101** » Sun Jun 01, 2008 6:44 am

NASM - Assembler
DJGPP - C Compiler
WinRawWrite - raw floppy sector writer
VS2008 - IDE
BOCHS + QEMU + VPC2007 - emulators

ollie123 · Post by **ollie123** » Sun Jun 01, 2008 9:22 am

I Use MinGW For Compiling (Includes GCC, G++, LD)
http://www.mingw.org/
I Use NASM For Assembling (Includes NASM

)
http://nasm.sourceforge.net/
I Use Notepad++ For Coding (Includes

Notepad++!!)
http://notepad-plus.sourceforge.net/
I Use WinImage For Virtual Floppy - Unfortunately It's Not Free

http://www.winimage.com/
I Use Bochs For Emulation
http://bochs.sourceforge.net/

Hope this helps,
Ollie.

ollie123 · Post by **ollie123** » Sun Jun 01, 2008 9:23 am

01000101 wrote:NASM - Assembler
DJGPP - C Compiler
WinRawWrite - raw floppy sector writer
VS2008 - IDE
BOCHS + QEMU + VPC2007 - emulators

Cool, could you tell me how to set up VS2008 for that?

thooot · Post by **thooot** » Sun Jun 01, 2008 11:34 am

ollie123 wrote: Cool, could you tell me how to set up VS2008 for that?

I'm using nasm in VS2008. To do it:
1. Right click on the project
2. Custom Build Rules
3. New Rule File
4. Add Build Rule
5. For the values:
Command line = c:\nasm\nasm.exe [inputs] [Format] [Output]
Display name = nasm
File extensions = *.asm
Name = nasm
Outputs = $(IntDir)\$(InputName).bin
For the properties:
1. Format
Type = string
Default value = bin
Description = Format
Display Name = Format
Name = Format
Switch = -f [value]
2. Output
Type = string
Default value = $(IntDir)\$(InputName).bin
Description = Output
Display Name = Output
Name = Output
Switch = -o [value]

The $(IntDir) will go to either Debug or Release depending on your current configuration. You should be able to create a similar rule for the compiler & linker. You will also probably need to play around with the Tool Build Order (right click on the project to get to it). If you have multiple projects you should be able to create the rules once and then import them into other projects.

elderK · Post by **elderK** » Sun Jun 01, 2008 12:29 pm

My development toolchain is identical on all platforms...

For compiling, assembly, linking...
GCC 3.4.x, Binutils 2.16x

For makefiles...
Any GNU Make ive tested with ...

For image generation (fdd, raw or fat12)
My own Image generation programs...

RAMDisk / Boot Package generation
Again, my own programs ...

Emulation
BOCHS!!!

Editing?
Vi (vi, nvi, elvis, vim... whatever is there)

~Z

sakuya84 · Post by **sakuya84** » Mon Jun 02, 2008 5:05 pm

Thx you guys for all the answer now i'll try the different combination the you told to me!!!

when i can rebuild all the os i'll post a screenshot XD

sakuya84 · Post by **sakuya84** » Tue Jun 03, 2008 8:57 am

sorry guy i have another problem... i used minigw for compiling all .... but to replace the command cat(linux) which command i must use in windows?

AJ · Post by AJ » Tue Jun 03, 2008 9:01 am

This command simple concatenates 2 files. In windows, you just use the copy command:

Code: Select all

copy file1.txt+file2.txt

Will append file2.txt to file1.txt.

Cheers,
Adam

sakuya84 · Post by **sakuya84** » Tue Jun 03, 2008 9:13 am

Ok guys you can kille me now.....
when launching this command

Code: Select all

ld  -Bstatic --oformat binary  -o kernel.bin main.o functions/printk.o interrupt/idt.o functions/io_port.o interrupt/pic8259.o functions/keyboard.o  functions/string.o functions/shell.o -Ttext 0x10000 -Map kernel.map

an error occour

Code: Select all

ld: cannot perform PE operation on non PE output kernel.bin

where i'm wrong?

AJ · Post by AJ » Tue Jun 03, 2008 9:24 am

Time to build a GCC Cross-Compiler

Cheers,
Adam