In message <[EMAIL PROTECTED]>
Matthew Howkins <[EMAIL PROTECTED]> wrote:
> I am not sure how best to add the Module source to the CVS repository, because
> BASIC files are binary, and don't lend themselves to CVS diff showing changes
> easily - CVS works better with text files. I am open to suggestions on how
> best to handle this.
You could save them as plain text (BasText). This isn't too hard to
change back and forth.
>
> Incidentally, the method I am using for generating modules is to assemble
> them
> under Linux/x86 using the GNU binutils setup for ARM code. This way the
> module source is plain text, and can be assembled anywhere the GNU tools are
> available. Does anyone think this is the best way to add source code for
> support modules to ArcEm?
You mean, anywhere that ARM targetted binutils are available; but anyone
can install binutils-multiarch (Debian) or download an x86-ARM cross
compiler. This is probably the best solution, and in the fullness of
time, we'll be able to use the same code to directly generate modules
using GCC+binutils in RISC OS. The alternative is to have them in AOF
assembler, and use GCCSDK to assemble them.
--
Peter Naulls - [EMAIL PROTECTED] | http://www.chocky.org/
----------------------------------------------------------------------------
Drobe - http://www.drobe.co.uk/ | The Premier RISC OS News Site
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
arcem-devel mailing list
arcem-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/arcem-devel
