Hi guys,
Quite a few questions brought up here and even more answers :)
As there seems a vast majority to keep jat here, follow this path...
As William says, we need a place for more then just the sources of the
translater itself. So maybe create a directory structure like:
───jat
├───bin
├───grammar
├───source
└───targets
├───arduino
│ ├───cbuild
│ ├───include
│ └───sample
└───arm
├───cbuild
├───include
└───sample
where
- bin contains the (stable) jat executable
- grammar contains the grammar file. This is a bit of a compromise,
since the grammar could be part of source too. The grammar part is
next to independent of jat, but there are also rewrite rules in this
file and jat relies heavy on there.
- source contains the sources of the translator itself
- targets contain a directory for each port (which can be a single
processor, a group of processors etc). Such a directory will contain a
build script and subdirs.
- include contains a device file (which means: a file in jal format)
for this target and libraries. Some of these libraries could provide
target-specific code, others might give a target implementation of a
known jal library (often by wrapping an exisiting c lib).
- cbuild contains the files used in the build process, like linker
files, startup code and wrapped libraries.
- sample wil contain the samples specific to this target. Later, when
we have more insight, we can think on how to integrate these into the
existing jallib sample structure.
Would this be an appropriate structure for now?
Joep
--
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.
