I'm currently working on building a new operating system, but i need help with it. I'm currently working on the shell, but i realized that i need a new interpriter for it. the file extensions for the applications are going to be .app. can anyone help me with building the interpriter for dev-c++. and also help me with linking the interpriter to dev-c++. let me know you have any ideas.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Do you really mean a "new operating system" and all that entails - i.e. booting up from the BIOS, initialising all hardware etc.? Or do you rather simply mean a command shell running on Windows?
I ask because the MinGW toolchain builds Win32 programs. It is probably unsuited to building an OS proper; whatever it builds runs on Windows. However, much of what makes it Windows specific is the linker, so you could still use the compiler, but your OS would have to know how to load and execute the object code.
Either you don't have the expertise to understand what you are doing, or I don't have the expertise to understand what you are doing. You have to realise that what you are doing is unusual, and experts are hard to find. This may not be teh best forum for you.
What is this interpreter going to interpret? What is the language definition and syntax?
What do you mean by "linking the interpriter to dev-c++"?
Your question is not very specific and lacks clarity. It sounds like a very short/vague question for a very large/complex project, and the answer is probably very long. But in short, yes, I can help; my consultancy rates are 200USD per hour - and you've already had $17 dollars worth for free! ;-)
When I say "build a new OS", I mean a new OS. my problem is that the interpriter and linker makes it a win32 program. and when i said "linking the interpriter to dev-C++", i meant setting up dev-c++ to use the interpriter.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It is the "interpriter" bit that has thrown me. What is that? I assume that you mean the compiler? An interpreter (correct spellling) is a different thing altogether.
Setting up Dev-C++ to use an alternate tool chain is easy, and is done in teh Tools->Compiler dialog. It only generates GCC command line options though, so it will need ot be a GCC toolchain. Alternatively you can use a custom make file - it is likly that you will need ot do that in any case since you wil be generating a non-standard build. There is a PDF document on setting and older version of Dev-C++ up for ARM development which is similar in principle.
You will I believe need a retargetted cross compiler, i.e. a compiler that is hosted on Windows, but targets an OS-less x86 PC board. http://wiki.osdev.org/GCC_Cross-Compiler . Unfortunately GCC is not straightforward ot build on Windows, MinGW does it, but information on building a MinGW hosted cross-compiler is sparse. Your best bet is either to use Linux or Cygwin and build the cross-compiler within that. You can use Dev-C++ for Cygwin, but obviously not on Linux.
To be honest, using Dev-C++ is the least of your worries. Get the tool chain first. I suggest that you take a look at the links I posted, there are some great resources there.
Speaking as an embeded systems developer, I suggest that you rather consider building an RTOS for an embedded system. Low cost ARM boards and toolchains are readily available, and while no one will be interested in your x86 OS, there is a ready market for code for resource constrained embedded systems.
Clifford.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm currently working on building a new operating system, but i need help with it. I'm currently working on the shell, but i realized that i need a new interpriter for it. the file extensions for the applications are going to be .app. can anyone help me with building the interpriter for dev-c++. and also help me with linking the interpriter to dev-c++. let me know you have any ideas.
Do you really mean a "new operating system" and all that entails - i.e. booting up from the BIOS, initialising all hardware etc.? Or do you rather simply mean a command shell running on Windows?
I ask because the MinGW toolchain builds Win32 programs. It is probably unsuited to building an OS proper; whatever it builds runs on Windows. However, much of what makes it Windows specific is the linker, so you could still use the compiler, but your OS would have to know how to load and execute the object code.
Either you don't have the expertise to understand what you are doing, or I don't have the expertise to understand what you are doing. You have to realise that what you are doing is unusual, and experts are hard to find. This may not be teh best forum for you.
What is this interpreter going to interpret? What is the language definition and syntax?
What do you mean by "linking the interpriter to dev-c++"?
Your question is not very specific and lacks clarity. It sounds like a very short/vague question for a very large/complex project, and the answer is probably very long. But in short, yes, I can help; my consultancy rates are 200USD per hour - and you've already had $17 dollars worth for free! ;-)
I suggest that you study a bit and get your terminology straight - these may help:
http://visopsys.org/osdev/index.html
http://www.codeproject.com/KB/system/MakingOS.aspx
http://www.osnews.com/story/2691
Clifford
When I say "build a new OS", I mean a new OS. my problem is that the interpriter and linker makes it a win32 program. and when i said "linking the interpriter to dev-C++", i meant setting up dev-c++ to use the interpriter.
It is the "interpriter" bit that has thrown me. What is that? I assume that you mean the compiler? An interpreter (correct spellling) is a different thing altogether.
Setting up Dev-C++ to use an alternate tool chain is easy, and is done in teh Tools->Compiler dialog. It only generates GCC command line options though, so it will need ot be a GCC toolchain. Alternatively you can use a custom make file - it is likly that you will need ot do that in any case since you wil be generating a non-standard build. There is a PDF document on setting and older version of Dev-C++ up for ARM development which is similar in principle.
You will I believe need a retargetted cross compiler, i.e. a compiler that is hosted on Windows, but targets an OS-less x86 PC board. http://wiki.osdev.org/GCC_Cross-Compiler . Unfortunately GCC is not straightforward ot build on Windows, MinGW does it, but information on building a MinGW hosted cross-compiler is sparse. Your best bet is either to use Linux or Cygwin and build the cross-compiler within that. You can use Dev-C++ for Cygwin, but obviously not on Linux.
To be honest, using Dev-C++ is the least of your worries. Get the tool chain first. I suggest that you take a look at the links I posted, there are some great resources there.
Speaking as an embeded systems developer, I suggest that you rather consider building an RTOS for an embedded system. Low cost ARM boards and toolchains are readily available, and while no one will be interested in your x86 OS, there is a ready market for code for resource constrained embedded systems.
Clifford.