-
|
Hi ELKS I've recently sit down to port a small set of CGA graphics utilities to ELKS for my own use, and am faced with a choice of three compilers to select for the task:
For efficiency I'd prefer to cross-compile, so watcom or gcc seem like the right choice. I'm also unconcerned with far pointers but am potentially interested in non-C language support so gcc pops to the top of the list. All that said, I'd really just want to go with the flow. The choice of three compilers is nice but invites analysis-paralysis. Given time constrains for hobby projects, and project leaders future plans, which tool-set would you recommend a new ELKS developer invest their time in... today? Also, with all the recent emphasis on new compilers, what do you plan to see as the mainstream ELKS compiler in, say, 2029? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
I recommend using the ia16-elf-gcc compiler, as it's configured out-of-the-box to work with ELKS, produces great code, and is used to compile the kernel and all the non-optional applications for ELKS. I'm not sure what the future holds for C compilers for ELKS, but ia16-elf-gcc will undoubtably always be supported. |
Beta Was this translation helpful? Give feedback.
-
|
Sounds good to me. Thanks for the clear direction, and for taking time with new users. |
Beta Was this translation helpful? Give feedback.
I recommend using the ia16-elf-gcc compiler, as it's configured out-of-the-box to work with ELKS, produces great code, and is used to compile the kernel and all the non-optional applications for ELKS.
I'm not sure what the future holds for C compilers for ELKS, but ia16-elf-gcc will undoubtably always be supported.