That would be asking PJRC to support non-PJRC products. The Teensyduino installer is designed to never modify Arduino for non-PJRC boards.
At the moment, I'm working on a new Teensy product, so I don't have time for extra stuff lately.
I'm sorry, i must have misundertood something. From your 'long-email' below i gathered you are already supporting arduino.
I understood, your installer doesn't work for arduino boards because you respect the arduino-team's decision not to include your modifications.
Whatever, you viewpoint is taken.
Isn't simply copying the malloc.c I provided (which is really just a slightly modified copy from a later avr-libc) into your hardware/arduino/cores/arduino directory also a partial solution?
The "partial solution" was meant to say 'it is a solution until the arduino team provides a final fix'.
I don't know what is actually necessary to fix it.
I also don't get it, if it is so simple to fix it then why don't the Arduino people do that?
I am not sarcastic here, i really don't see the issue: why isn't it fixed?
There seem to be an issue with dynamic mem.alloc. and String - which is dependent on malloc.
I can't remember the name - someone in the earlier posts said it is too hard to fix it.
And yes, i remember you did say to copy malloc.
Is this all to it?
One last thing. You said something about a compiler switch?
Is it a swith in the compiler to compile for arduino boards? Or for your boards?
Do i/we need to be concerned abouth this switch - whatever it may be.
Thanks for your time and effort anyway.