installing bB on Mac OS X Snow Leopard?

[esplonky]

How would one achieve this?

[cybercylon]

http://bataribasic.com/install.html

 

There is a section for OS X. Don't know if these binaries are PPC, universal, or intel. If they are PPC, remember that they won't work under Lion, Mountain Lion, or whatever comes after that.

 

Just saw that page might be out of date. Try http://www.randomterrain.com/atari-2600-memories-batari-basic-commands.html. Maybe Random Terrain might be able to help you.

Edited July 15, 2012 by cybercylon

[+Gemintronic]

Use VMWare Fusion. Or WINEBottler. Or dual boot XP with boot camp. VisualbB really is needed for bB development. I doubt if VisualbB will ever get recompiled for Mono so..

Edited July 15, 2012 by theloon

[Byte Knight]

http://bataribasic.com/install.html

 

There is a section for OS X. Don't know if these binaries are PPC, universal, or intel. If they are PPC, remember that they won't work under Lion, Mountain Lion, or whatever comes after that.

 

The above install worked fine for me using the Terminal application. If you want to use the DPC+ kernel, I recall having to use the "make" command after installing everything, and the "make" command is not included in the Terminal app. You'll have to download Xcode 4.2 for Snow Leopard in order to install this. Then, you type in "2600basic.sh filename.bas" to compile your programs.

[esplonky]

Use VMWare Fusion. Or WINEBottler. Or dual boot XP with boot camp. VisualbB really is needed for bB development. I doubt if VisualbB will ever get recompiled for Mono so..

 

I've actually only used visual bB like 2-3 times. I like it, but only because of the compile button. that's it. i do all my editing in a Text editor.

[+Gemintronic]

I get you. Still, it's not just for the nice VisualbB interface. Different versions of the bB compiler will give different results. For instance, in my version of bB the SDATA support is broke.

 

If you use WINE or VMWare Fusion you can be sure to use the same bB compiler as everyone else. It gives people a better chance of reproducing your issues when you have trouble compiling

Edited July 16, 2012 by theloon

[esplonky]

I got the compiler in the right spots, and I got the makefile from an older thread, and when I type make, i get this in terminal:

 

Forrest-Hodgess-MacBook-Pro-15:mag forresthodges$ make
2600basic.sh default.bas -O
make: 2600basic.sh: No such file or directory
make: *** [default.bas.bin] Error 1

 

the compiler is located in /bB and the project I'm trying to compile is in /bB/mag, and on my linux box when I would compile, I would just put the makefile in the project folder and navigate there in terminal, and type make and it would compile.

 

here is my makefile code:

 

export PROJECT=default
export bB=/bB
export PATH=/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin:.:${bB}
export COMPILER=2600basic.sh
export HOME=${PWD}
main:  ${PROJECT}.bas.bin
${PROJECT}.bas.bin: ${PROJECT}.bas
${COMPILER} ${PROJECT}.bas -O
@ [ `du -sb ${PROJECT}.bas.bin | cut -f1 | awk '{print $$1 % 2048}'` = 0 ] || rm ${PROJECT}.bas.bin
@ ( [ -r ${PROJECT}.bas.bin ] && echo "\n	 /|\\" ${PROJECT}.bas compiled successfully" /|\\ \n" ) || echo "\n	 > > > Compile of ${PROJECT}.bas FAILED! > > >\n"
clean:
/bin/rm -f ${PROJECT}.bas.bin ${PROJECT}.bas.asm ${PROJECT}.bas.dump includes.bB bB.asm 2600basic_variable_redefs.h
run:
stella ${PROJECT}.bas.bin
debug:
mkdir .stella 2>/dev/null || true
echo "breakif {_scan>#262}" > .stella/autoexec.stella
stella -break "*($fffc)" ${PROJECT}.bas.bin
backup: clean
tar -cvzf ${PROJECT}-`date +%Y%m%d`-backup.tgz --exclude=\*tgz *

 

my project is default.bas

[+stephena]

here is my makefile code:

 

export PROJECT=default
export bB=/bB
export PATH=/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin:.:${bB}
export COMPILER=2600basic.sh
export HOME=${PWD}
main: ${PROJECT}.bas.bin
${PROJECT}.bas.bin: ${PROJECT}.bas
${COMPILER} ${PROJECT}.bas -O
@ [ `du -sb ${PROJECT}.bas.bin | cut -f1 | awk '{print $$1 % 2048}'` = 0 ] || rm ${PROJECT}.bas.bin
@ ( [ -r ${PROJECT}.bas.bin ] && echo "\n	 /|\\" ${PROJECT}.bas compiled successfully" /|\\ \n" ) || echo "\n	 > > > Compile of ${PROJECT}.bas FAILED! > > >\n"
clean:
/bin/rm -f ${PROJECT}.bas.bin ${PROJECT}.bas.asm ${PROJECT}.bas.dump includes.bB bB.asm 2600basic_variable_redefs.h
run:
stella ${PROJECT}.bas.bin
debug:
mkdir .stella 2>/dev/null || true
echo "breakif {_scan>#262}" > .stella/autoexec.stella
stella -break "*($fffc)" ${PROJECT}.bas.bin
backup: clean
tar -cvzf ${PROJECT}-`date +%Y%m%d`-backup.tgz --exclude=\*tgz *

 

my project is default.bas

 

Keeping in mind that the commands to launch Stella and the location of the autoexec file are different for OSX (and Windows, for that matter).

 

Although having to edit the autoexec.stella file manually reminds me that it should be available in the UI. Not to mention, a better filename could be used).

[esplonky]

I got the bB part to compile into ASM, now I get this in terminal:

 

Forrest-Hodgess-MacBook-Pro-15:mag forresthodges$ make
/bB/2600basic.sh default.bas -O
Starting build of default.bas
2600 Basic compilation complete.
DASM V2.20.07, Macro Assembler (C)1988-2003
  bytes of ROM space left
  2854 bytes of ROM space left
Complete.
Build complete.
du: illegal option -- b
usage: du [-H | -L | -P] [-a | -s | -d depth] [-c] [-h | -k | -m | -g] [-x] [-I mask] [file ...]
/bin/sh: line 0: [: =: unary operator expected
 > > > Compile of default.bas FAILED! > > >

[+RevEng]

Hmmm... your makefile looks familiar!

 

Just remove the entire line that has the "du" command in it... your "du" doesn't support reporting in bytes or has a different syntax. That line in the makefile is supposed to check if the compiled bB program is a multiple of 2k, and removes it if its not so you're not fooled by incomplete builds. Its a nice-to-have feature, but not strictly required.

 

It also looks like AA stripped the tabs out of the makefile. Hopefully your copy still has them in, otherwise it won't work correctly.

[esplonky]

Yay Compilation worked