--- In firstname.lastname@example.org, Dan Andersson [EMAIL PROTECTED] wrote:
Do Not! fork out and use another compiler than the GCC.
As the development of the GCC have been seen breaking some
libraries, it would probably be a serious waste of time to start
makefiles for further compilers.
Regarding quality - GCC is probably the most developed and checked
out there. Besides, the GCC is a free software and by that -
I seriously doubt you will be able to find any serious shortcomings
when compared to Borland.
There are reasons behind the major C-compiler producers to compare
products with GCC.
If you want to develop KiCad further, use GCC! If you have to
functions, see to that they are compatible with MONO so we can
in fully open source environments.
On Saturday 13 October 2007 19:55:37 drwrench wrote:
Hi Dick, Thanks for the reply.
I have not seen support for this compiler in the makefiles.
Do you realize what the quality level is for the GCC compiler
that Kicad uses as standard?
I don't know much about the recommended compiler but I did
it and will use it if I need to.
I mainly develop using Borland tools for Java, C# and Pascal
languages. I was hoping that if I could import Kicad into
CPP builder then everything would be under one IDE and I could
the possibilites of integrating parts of Kicad into other
applications written in other languages.
It's more out of interest at the moment as I have no real need to
any CAD package and don't want to learn a new compiler suite if I
avoid it for now.
But in the future I may need CAD so would like to try things out
early on if I can and I thought the Borland route would be the
easiest way for me.