Jump to content

MontyHall

Members
  • Content Count

    8
  • Joined

  • Last visited

Community Reputation

1 Neutral
  1. I thought this would be legal code 100 for b% = 0 to 10 110 print b% 120 next b But I get a syntax error at line 100. Is this not possible? Or how to do it correctly.
  2. Thanks, looks like -C ${HOME}/workspace/cc65/cfg/cx16.cfg work. too bad that it has to be so verbose, but at least I can get moving. Thanks
  3. Yes, I have a ~/workspace/cc65/cfg/" dir
  4. This is what I get when I "which cl65": /home/rick/workspace/cc65/bin/cl65. Yeah, I don't know what's going on. I'll just hack the make file. but I think I'll try the env vars first. EDIT: I tried the exports, no luck. I guess I'll hack the make file.
  5. That's impressive. Reasonable hit in speed using cc65 C.
  6. What's the performance penalty of using cc65 C over pure assembly? Have to admit would like to rapid prototype in C w/o the assembly albatross. Would you say cc65 C is 2x slower? It certainly can't be worse than basic 2.0.
  7. I can't get hello world to work. I'm running ubuntu 20 and compiled cc65. When I make I get the following: (base) rick@rick:~/workspace/x16-hello-cc65$ make make -C asm make[1]: Entering directory '/home/rick/workspace/x16-hello-cc65/asm' cl65 -t cx16 -o HELLOASM.PRG -l hello.list hello.asm ld65: Error: Cannot find config file 'cx16.cfg' make[1]: *** [Makefile:4: all] Error 1 make[1]: Leaving directory '/home/rick/workspace/x16-hello-cc65/asm' make: *** [Makefile:2: all] Error 2 I have cc65/bin in my path. I suspect I need to hack the make file to point to configs.
×
×
  • Create New...

Important Information

Please review our Terms of Use