That's bad again, firstly it's quite possible that the "pre compiled" compiler may not integrate well with your environment, secondly building a cross compiler it teaches you a lot of things you will need in your later stages and thirdly, it makes you familiar with your environment.StartOS wrote:Ok. I will use a cross compiler.
Can someone point me to a ready binary for windows or share theirs?
I am a newbie in OS Development and don't quite understand what to in the GCC cross compiler tutorial.
It is just not written as a series of steps. And I am a real begginer. I never before did low-level programming I just did make some useful windowed programs like a text editor, basic mail client.Bender wrote:The tutorial is very verbose, detailed and well written. Some of best people on this forum have worked on it. Read it carefully step by step, and you should be able to get a working cross compiler.
How the **** did this reached there. The Ghost Kernel is one of max's projects. You should not use it! Don't misunderstand me; max is an excellent developer, but precompiled binaries are the hell on Earth.StartOS wrote:I tried using ghost-i686-elf-tools from http://wiki.osdev.org/GCC_Cross-Compile ... Toolchains, but it requires some dll for the dependencies listed in http://www.ghostkernel.org/documentation/toolchain
. Before proceding, remember to read all the post before doing anything, specially the caveats at the end.First of all, get the lastest GCC sources. Extract them somewhereThe Holy OSDev Wiki wrote: You need to use a cross-compiler unless you are developing on your own operating system. The compiler must know the correct target platform (CPU, operating system), otherwise you will run into trouble. If you use the compiler that comes with your system, then the compiler won't know it is compiling something else entirely. Some tutorials suggest using your system compiler and passing a lot of problematic options to the compiler. This will certainly give you a lot of problems in the future and the solution is build a cross-compiler.
. Do the same with the lastest binutils sources. Do not mix both extracted folders!Code: Select all
cd gcc-src
./contrib/download_prerequisites
Code: Select all
cd ..
mkdir gcc-bld
mkdir binutils-bld
. If, by some reason, your terminal session is closed (power outage, etc..), you must refollow the following paragraph again.Code: Select all
export PREFIX="$HOME/cross"
Code: Select all
export TARGET="i686-elf"
):
Code: Select all
cd binutils-bld
../binutils-src/configure --target=$TARGET --prefix="$PREFIX" --with-sysroot --disable-nls --disable-werror
make
make install
) can understand.Code: Select all
cd ../gcc-bld
../gcc-src/configure --target=$TARGET --prefix="$PREFIX" --disable-nls --enable-languages=c,c++ --without-headers
make all-gcc all-target-libgcc
make install-gcc install-target-libgcc
. GCC's build is much more propense to disasters, so be aware for any errors! Again, I'll explain the flags. The first three are the same than for binutils. --enable-languages is pretty trivial; it creates compilers for C and C++. --without-headers alerts GCC that there won't be any runtime C(++) standard support library for the target. These commands also build libgcc, a library that GCC can generate calls to without any way to avoid it!. All GCC-compiled programs will be linked with libgcc. It implements some software-computed features that the target hardware is unable to handle, such as 64-bit division in i686-elf.Code: Select all
export PATH="$PREFIX/bin:$PATH"
?)
recipe for target 'all-binutils' failedIncoming "Windows vs. Linux" war?iansjack wrote:I still think that you would find life easier if you stopped messing about with Windows and CygWin and used Linux to do your development. But perhaps you enjoy a challenge.
.
. GNU justifies all this with the false fact that GNU Software is only intended to run on a GNU system (compile that on BSD, or even Sortix 0.9 if you like ).