Gone is the ‘os’ script–just use the ‘ins’ script from now on.Â The ‘os’ script will remain if you want to wipe the mem stick and keep our code off of it.
Couple of recent updates: the ‘ins’ script now fails to unmount the memstick when compilation fails (very good, thanks Jeremy).Â Also, we’re now exclusively using the UPENN head engine.Â Rock on.Â AiboConnect you can still choose between the two by calling ‘heads’ (no engine) and ‘headeng’ (head engine).
We’ve conquered windows. With george’s excellent post, I was able to get:
-cygwin (and subversion) installed
-open-r SDK installed
-get our code from the repository
-install the memory card reader driver
-and with editing only one file (makefile.config), get our code onto a working memory stick.
This means: check out the new makefile.config on the repository. If you want to use Win, uncomment the win part. If you want to use Mac, uncomment the make part.
The greatest thing about windows: we don’t have to script the unmounting process. It doesn’t yell at you when you take the stick out.
Windows, consider yourself 0wned.
Makefiles pretty much all sorted. Code properly compiles but there are a billion more warnings now that i’ll have to sort through. Dogs boot up and run fine, but quitting aiboConnect crashes the machine. something with the ceaseHeadSlowly method (!).
Mounting/Unmounting our Sony Memory Sticks in OSX is becoming increasingly tricky.
In linux (or even in cygwin for Windows), this is a very easy process.
Mac OSX has a seemingly easy mount command-line program called ‘disktool’. It identifies the mount internally (e.g. disk1s1 or disk3), and externally (memory sticks typically come up as ‘Untitled’) and users can access this mount at /Volumes/Untitled/. disktool has commands to unmount drives via shell-scripting, which is very nice.
Annoyingly, OSX identifies sticks differently per machine and even sometimes within the machine (sometimes it’s ‘disk1s1’ or ‘disk3s1’). If you’re not careful about setting it properly in the scripts, you can unmount something you don’t want to. I found this out the hard way when I accidently unmounted Chown-dog’s hard drive.
So all of a sudden today, the external and internal identification of my stick somehow changed as I was fiddling with Makefiles. First the external id became ‘Untitled 1’ then ‘Untitled 2’ and ultimately after some ejections and a reboot, ‘UNTITLED’ (shell-scripting in OSX is case-sensitive). This changes the place where we copy all of our sweet code.
I need to use my brain and figure out a way to solve these two annoying mounting issues–both to safely unmount the correct drive, and to not have to constantly change configuration files whenever osx decides to rename a mount.