I am working on a project using eCos, and the GCC compiler we use is called powerpc-eabi-gcc, powerpc-eabi-g++, etc. Because of this I found myself having to create some new classes. I wanted to extend the GCC classes, but because of the static final getInstance() methods I found it easier to simply duplicate the classes and just change what was different.
I can't imagine that this will facilitate code management. It would be nice if we can come up with a better solution, since there are bound to be other GCC variations. If I have any workable suggestions I will let you know.
BTW I would like to contribute back the code that I did for this. Who should I send it to?
Andre
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I am working on a project using eCos, and the GCC compiler we use is called powerpc-eabi-gcc, powerpc-eabi-g++, etc. Because of this I found myself having to create some new classes. I wanted to extend the GCC classes, but because of the static final getInstance() methods I found it easier to simply duplicate the classes and just change what was different.
I can't imagine that this will facilitate code management. It would be nice if we can come up with a better solution, since there are bound to be other GCC variations. If I have any workable suggestions I will let you know.
BTW I would like to contribute back the code that I did for this. Who should I send it to?
Andre