>
>
> > Ok, then we should wait before the release, right?
>
> The change I made for the 12f629/675,16f630/676 (w.r.t. issue 50) seem
> to work with a simple blink test, but I want to do some more tests. I'll
> report when done!


OK


> BTW I'll change the compiler requirement to 2.4i for all device files!


I've heard it would be nice to package the compiler with jallib. Is it
possible ? I mean, if we care about the license (BSD for compiler, BSD/Zlib
for jallib) with dedicated a license file for the compiler, is there any
other issue I can't see ? Would package only the binaries (jalv2 +
jalv2.exe) be enough ? About the packaging, several options:

 1. add the binaries in our repos (or the whole archive), as a 3rd party.
Pros: when packaging, it's already there. Cons: need to update this for each
compiler release. Rem: we should put the version in the binary names if we
want to use more than one version (eg. jalv24i)
 2. when building the package, download the archive, extract and take what
we want. Pros: keep repos kind of clean. Cons: Kyle's website needs to be
up, archive content should be the same, else need to adjust the packaging
script.

I'd prefer 1.


And pushing the whole thing a little bit further, we could also package
JALEdit and/or PICShell...


> >> We appreciate your work Seb, even though we may not say that every day!
>
> > Mmmhh.. What do you mean ?!
>
> OK, in other words: I do not want to repeat every day 'thanks for the
> good work' even though you deserve it.


OK, we all deserve it, so here it is: Thanks for your device files and all
your involvement !


Cheers,
Seb
-- 
Sébastien Lelong
http://www.sirloon.net
http://sirbot.org

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/jallib?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to