On Wed, Oct 4, 2023 at 2:37 PM Tristan Williams wrote: > Hello Mark, > > I took a local clone of your repo and the new template built for an uno > without issue. Thank you. > > Are you open to a pull request? >
Of course. I do believe that last night I fixed the last of the little bits that were giving me trouble after trying to take care of the zero byte padding issues. For some odd reason one of them played havoc with Evalue in so that it just didn't work. It was in the word list, but was just hanging. That is fine now as far as I can tell. I tested quite a bit with my word list that is pretty extensive. > > Seeing that we are dealing with makefiles, it seemed a good time to > address prebuilt binaries. I have blended/amended your template with > the existing makefile in appl/arduino to output hex files for the m328 > based UNO and the 2561 based mega. I agree. Any of the projects in appl should be able to be built and/or have a prebuilt hex in them. Since today was the first day I was able to stop looking at the repo and look at my own project to clean up the next thing I did want to do is to cull and clean those. I have an uno or three and a mega from an old disassembled 3D printer around here so I can try those next. I also have a few other atmegas to work with from various interests over the years. I need to look and see if any of them (atmega8, 16 etc) are even able to take AmForth. So yes, any info put up at the repo will most certainly be seen and considered by me for now unless something else happens to move that focus. > Separately, I have written a script to produce a simple html build > specific reference-card that lists the words built into the respective > pre-built hex files. It searches the .lst file produced by the > assembler (in this case avra) for the assembler source files used and > then searches them for the documentation. This has been discussed [1] > on the mailing list before. However, if there are going to be prebuilt > hex files in the repo, then a reference-card for those builds will be > helpful for the person trying them out. It is not intended to be a > substitute for the reference-card for AmForth as a whole. > > I have put up the html here as an idea. > > https://www.mostlymostly.uk/amforthdocs/prebuilt.html > > The page uses material from the existing site. It is not plumbed > into the rst source (but it could be). This looks great. A few times after you put up the link I accidentally ended up there and wondered why the SF site was so snappy. I see you have kept up with the refcard thing over the years from when we played around with it. It's done with python I'm guessing. I really like your idea of making them from the .lst files. It's something I've always thought would be a great addition inside of the project directories if someone so desired. > Best wishes, > Tristan > > [1] https://sourceforge.net/p/amforth/mailman/message/37112236/ All the best to you as well. It feels good to be polishing up the tools to polish up the Forth that was starting to bit rot in my brain. Mark > > > On 30Sep23 22:30, Mark Roth wrote: > > On Sat, Sep 30, 2023 at 9:46 PM Keith Amidon wrote: > > > > > On 9/30/23 03:17, Mark Roth wrote: > > > > Hello weekend AmForth'ers > > > > > > > > So, while waiting to see what will happen with the repo I have > continued > > > to > > > > play with a git version for my own use. I have reworked the makefile > and > > > > made some changes to the repo structure to accommodate for the new > avra > > > > code (which is still only a placeholder until I get that repository > in > > > > properly). I think that the new makefile should make it very easy to > get > > > > started and there is a bit of a long winded readme to explain > anything > > > that > > > > has changed. If anyone wants to take a look and give feedback that > would > > > be > > > > great. > > > > > > > > https://github.com/CableGuy67/AmForth > > > > > > I took a quick look at the makefile and related fines in the > > > appl/template directory, which I believe is what you're referring to > > > here. I have two minor suggestions: > > > > > > 1. How about renaming "template.asm" as "app.asm" and making the > > > corresponding changes to the makefile? I think this would make a > > > workflow of copying the template directory to one named for a new > > > application without updating names within the template directory > > > very natural. I would feel weird leaving around a file called > > > "template.asm" because that doesn't communicate well the purpose of > > > the file in the ultimate project. But "app.asm" seems like it could > > > usually fit. Having a consistent name like this could also simplify > > > documentation. > > > > > > > Yeah, that does sound like a good idea. I like the way it implies intent. > > > > > > > 2. This is really just a template for an avr8 project, right? Perhaps > > > the directory containing this sub-tree should be named > > > "avr8-template" instead of "template"? It seems to me that really > > > all the directories under "/appl" are currently templates for > > > different targets? Is that right? > > > > > > Note that I haven't tried anything here, these all come from code > > > inspection and may be due to misunderstandings on my part. > > > > > > Cheers! Keith > > > > > > > You're not wrong in that. Since I only use the avr-8 chips I only > recently > > even looked into those other appl directories. It seems that it just sort > > of grew like mushrooms (appl that is) and never had any cohesiveness. > > Indicating that it is the appl template for avr8 is a no brainer. I have > to > > wonder if the makefile at one point in time was supposed to be more > > inclusive with the other platforms but just never got there. > > > > Thanks for the suggestions. Different eyes and all. > > > > All the best, > > Mark > > > > > > > > > > _______________________________________________ > > > Amforth-devel mailing list for http://amforth.sf.net/ > > > Amforth-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/amforth-devel > > > > > > > _______________________________________________ > > Amforth-devel mailing list for http://amforth.sf.net/ > > Amforth-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/amforth-devel > > > _______________________________________________ > Amforth-devel mailing list for http://amforth.sf.net/ > Amforth-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/amforth-devel > _______________________________________________ Amforth-devel mailing list for http://amforth.sf.net/ Amforth-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amforth-devel
