If all you want is faster builds, the solution is make-style dependency
checking. I submitted this feature as part of a patch on issue #393.
The code is still there in the issue tracker, if you're interested to
Ultimately, only the compile order portion was used. Changing the build
to reuse compiled code was considered too risky. I still have this code
in development for use with Teensy. After it's more mature, I'll ask
for help testing with Arduino. When/if David feels this is ready to
merge, I'll prepare another patch.
If you want faster builds now, and you're willing to test this, please
contact me off list.
But if what you really want is to distribute closed source libraries,
that's not really feasible, and nothing I've done will be of much help.
On 03/04/2011 10:00 AM, Mark Sproul wrote:
> I agree with Massimo
> Pre-compiled libraries speed things up a little but have drawbacks.
> Many users only own one Arduino board and therefore it would work to
> have pre-compiled headers. I own almost every one ever made and
> sometimes have 3 different ones attached to my computer at the same
> time to allow testing code on different configurations. Pre-compiled
> libraries would just get in the way.
> On 3/4/11 9:57 AM, Massimo Banzi wrote:
>> My heart... is that enough :)
>> On 4.03.2011, at 15:54, Pierce Nichols wrote:
>>> Does it break anything to include the possibility?
>>> On Fri, Mar 4, 2011 at 6:50 AM, Massimo
>>> Banzi<> wrote:
>>>> That's kind of against the arduino philosophy :)
>>>> On 4.03.2011, at 15:38, Pierce Nichols wrote:
>>>>> Will this allow Compiler.java to use pre-compiled libraries?
> Developers mailing list
Developers mailing list