Breaking into components: gcode-parser more separate

[Henner Zeller]

Hi,
In the recent changes, the gcode-parser grew a lot in files (and
Leonardo plans to add more to it), so I now put the gcode-parser and
the common utilities (mostly string utils) in a separate library
subdirectory in src/.

Things are not optimal yet, there is a lot of common boilerplate in
all Makefiles, which should probably be more compacted. Also, the
libraries are done with simple static libraries; it would probably be
better to use libtool for these things.

Suggestions welcome :)

Cheers,
Henner.

[Leonardo Romor]

Hi,

Il giorno giovedì 23 marzo 2017 12:22:25 UTC+1, Henner Zeller ha scritto:

Hi,
In the recent changes, the gcode-parser grew a lot in files (and
Leonardo plans to add more to it), so I now put the gcode-parser and
the common utilities (mostly string utils) in a separate library
subdirectory in src/.

maybe we could move the *.p, *.hp, pru-motion-queue, uio-pruss inside a pru/ folder?
Or move in another folder the hardware dependent files?

 

Things are not optimal yet, there is a lot of common boilerplate in
all Makefiles, which should probably be more compacted. Also, the
libraries are done with simple static libraries; it would probably be
better to use libtool for these things.

I never played around with libtool, it would be interesting for me to understand how it works :D