Thanks Gothic,

I will definately consider it. That is the exact reason why I have "Compiling Command" tab in the project options. The user will be able to choose to either let SkyIDE compile the project files or let the SkyIDE read user's command and when "Compile" or "Run" is pressed, the command the user typed will run instead of mine. But I know what you mean with all these make files. I haven't used any of them. I will be better of invoking them to do the job, I can just create a nice GUI for it to make things easier.

Once I complete this, what I am doing now, for the next beta after Beta 14 , I may add a third option where I let the user deal with makefiles. I will HAVE to write a help file as this is getting a bit complicated. Here is a screenshot of what happens when the second option is selected: (Considering there are no errors in code)

http://www.skyide.net/images/testing/multiprocess.png

I deliberately created some errors to demonstrate the error writing procedure in the output pane and I just launched the prev EXEs manually but if there were no errors, the EXEs will start by themselves.

Notice how the errors for each file are listed at once. You have main2.cpp, main3.cpp etc.

By the way, I am also adding an option now for the C++ compilers:

(*) Compile ALL of the above files in a single process
( )  Compile ALL of the above files in separate processes

Choosing the single process option, when compiling the files, only one file may have a main() function

Choosing the separate processes option, each file may have multiple main() functions and each file will generate its own exe


Regarding the separate cores, hmmm, I haven't dealt win anything like that before. Manipulating cores? Now that would be cool :)