Congratulations on the application of JAL for ATmega/Aruindo! Two weeks ago, the blink example was 'leading edge' and many features have been added to the translator since. So I guess it is time for a more complex demo.
And my 'build scripts' are clumsy and with the jal-to-hex (and deploy) focus, we should work on that too. How could we automate the build chain in a flexible and platform-independent way? I know the obvious answer is make, but - apart from the tabs vs spaces I never get used to - there seem so many different versions around that are slightly different so everyone seems to supply it's own version (which does not *make* it easier). A search on my system gave 13 copies of make.exe (and 8 which have make.exe as part of their name) and of those 13, there are at least 6 different versions... Is this just because I don't understand? And are there any alternatives (I see bscmake, dmake, vmake and also mingw32-make)? Joep 2010/5/8 William <[email protected]>: > Greetings, > >> /trunk/grammar/avrdemo/blink_avr.jal > > This one took a while to track down. I could blink led from Arduino > IDE example 'blink' sketch, but not from JAL. Wrong pin was > defined. :-) > > William > > -- > 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.
