Maybe a simple edit to the Makefile could correct that issue.
Since I use ant (and the build.xml files) I welcome feedback for the
makefiles. I seldom (in fact never) use make.
Foolishly sloppy language from me again: I meant Makefile as a form of
synecdoche for the Build Process. (And I suppose in lieu of detritus I
might have said artifact, too.)
But my intent was clear (I hope): fully functional HEX files reside within
the distribution, and can get a new user, especially on an Arduino, up and
running right away. After some experimentation with these non-specific
builds, a user who cares to can figure out how to customize the HEX file to
suit their application.
That's exactly how I got started, and the path I followed to build my Uno
R3. And now I do all my Amforth dev work over SSH to a headless Raspberry
Pi with InoTool for a USB attached Uno (either commercial or homebrew). For
USD 35 I have a completely dedicated Amforth development station.
But without the early ability to experiment with those existing builds in
the distro, I might never have been motivated to figure it all out. You
should publicize those files more:
For evaluating Amforth, or even if you're merely curious about Forth on
Arduino, you may use one of the existing HEX files for the list of Arduino
boards supported found the folder of the distro.
Heck, you could even copy that family of HEX files to a higher level in the
source tree, and call it Demos or Test Images or the like.
Just a thought.
--
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
Amforth-devel mailing list for http://amforth.sf.net/
Amforth-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amforth-devel
