hi rob
yes i'm aware of this, i didn't forget, it was more about the logic
test within buildbot. i wanted to avoid detecting 18f samples, but a
grep will do the trick (lazy i am). i also have preserve cpu on my
server.
cheers,
seb
--
Sébastien Lelong
Le 5 avr. 2010 à 12:27, Rob Hamerling <[email protected]> a
écrit :
Hi Seb,
On 04/05/10 10:28 am, Sebastien Lelong wrote:
Great idea, I'll try this.
Sounds as if you hear about '-no-variable-reuse' for the first time,
while this option has been discussed several times. For example in a
msg here of 3 Jan 2010 I said:
Similar experience here. But for bulk sample compilation I use
-no-variable-reuse *only* for samples of the 18F series. For smaller
PICs it may give 'Out of data space' (e.g. 16f676_hd4480__4_1 and
_4_4).
BTW I check on '18' as first 2 characters of the filename. A grep
for 'include 18f' in the source seems safer, but there may be more
than one space between 'include' and '18f', and there may be (or
come) samples which include an '18lf' PIC.
Regards, Rob.
2010/4/5 mattschinkel <[email protected]
<mailto:[email protected]>>
Here's an idea seb...
compile all samples with -no-variable-reuse, if any fail to compile
(due to lack of ram/program space), do a second compile attempt on
the failed samples without -no-variable-reuse
Matt.
--
Rob Hamerling, Vianen, NL (http://www.robh.nl/)
--
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
.
--
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.
