[fpc-devel] Does mipsel-embedded build?
mail at michael-ring.org
Sun Sep 30 20:08:42 CEST 2018
Most likely Jeppe sent the patch only to me, I have forwarded the patch
to florian at freepascal.org so that you can get an idea on what he did.
Forgive me, I am a license dummy, can the licensing be handled properly
with something like Jeppe's approach? If yes then I would love to
maintain a repro of controller units, I can automagically generate
Headers for most relevant microcontrollers currently available.
Am 30.09.18 um 19:53 schrieb Florian Klämpfl:
> Am 30.09.2018 um 19:48 schrieb Michael Ring:
>> Hi Florian!
>> I have already reduced size to the same size to the size as on other
>> platforms, so a lot less space will be used. Please
>> give me a little time to cleanup my patches...
>> On providing headers seperate, a loooonnnnnngggggg time ago Jeppe
>> created a (close to genious) patch that allowed to use
>> a configuration file to inject embedded controllers at runtime, but
>> this never was implemented in trunk.
> True, I don't remember though were the patch was available.
>> I have tons of .pas files for embedded controllers (complete STM
>> Line, now also complete SAMC/SAMD line of controllers
>> and PIC32) that I can all provide as a patch but this increases the
>> emedded directory a lot and 95% of all headers will
>> most likely never get used. Having the mechanism that Jeppe once
>> developed would allow people to install just the files
>> they need, keeping the embedded directory clean & lean.
>> Perhaps this is something to implement in the future, what do you think?
> Yes, this could be done for sure.
>> FYI, here are the current patches for SAMCD+STM32 family:
> Ah, now I remember the other problem with the controller units: they
> are BSD style licensed because of the license of
> the original headers, so we cannot include them into FPC.
> fpc-devel maillist - fpc-devel at lists.freepascal.org
More information about the fpc-devel