3 ms·
You can submit path to vasm/vlink/vbcc authors and they would applt to his toolchain. They are very friendly to any improviment. On this way, We got a full macr
by Zardoz84 11y ago
You can submit path to vasm/vlink/vbcc authors and they would applt to his toolchain. They are very friendly to any improviment. On this way, We got a full macro assembler and linker for TR3200 cpu. Also, we have a SmallerC back end for TR3200. We only need to add some stuff for relocatable code on vasm tr3200 back end, and and write or adapt a libc to have a full C toolchain working.
Also, I think that is time to put our virtual computer here...
- david-given 11y agoOh sure --- I'm not saying there's anything wrong with it technically. But I can't use any kind of open development process. So, no github or Bitbucket. And the distributions still won't touch it. And there's still a single point of failure revolving around Volker Barthelmann; I can't rely on vbcc continuing to exist. A similar thing happened to lcc, which was a perfectly good if quite simple compiler that simply stopped being relevant because distributing was too hard.
- Zardoz84 11y agoWhy not we ask him about changing their license model? VASM and VLINK are modular. I think that if there is a problem about changing the license model, would be on these modules, not on the core of VASM and VLINK. I would be more happy if vasm/vlink/vbcc resides on GitHub or at least on a public subversion repository.
- david-given 11y agoI have, on several occasions. It's probably worth trying again, but TBH it would probably sound better coming from someone else.