Manifest would need to be extended and Makefile generation should know how to generate recipies for additional file types.
Candidates:
[ ] forms (.ftx -> .tx and .vr)
[ ] dictionaries (.utx -> .tx)
[ ] tp progs (.ls -> .tp)
tp programs will need a properly configured robot.ini. Support for that is already in place (robot.ini should be placed in the source space root or in the root of the main application package, then configured for use with the --robot-ini option).
Compiling TP programs is slightly more involved than Karel programs: the translator (maketp) requires an actual Roboguide cell to figure out which option (and thus mnemonics) are supported.
Manifest would need to be extended and Makefile generation should know how to generate recipies for additional file types.
Candidates:
.ftx
->.tx
and.vr
).utx
->.tx
).ls
->.tp
)tp programs will need a properly configured
robot.ini
. Support for that is already in place (robot.ini
should be placed in the source space root or in the root of the main application package, then configured for use with the--robot-ini
option).