"manoflinux" wrote:
still doesn't seem as clean to me. we are going to have to agree to disagree on this one.
What I have done though is setup my rokus in my /etc/avahi/hosts file so I can refer to them as roku01.local and roku02.local
if you dont use avahi you should check it out. I wouldn't put it on a box outside a firewall. but for your home network its great. . I dont use it for autoip because I stilll have a windows box(if it was not for playon I wouldnt have any windows boxes, just virtuals will get a multi core box to host it as a virtual at some point) and some windows virtuals that need dhcp, but you can use autoip and get rid of your dhcp server if you have nothing but Linux boxes. But I do use it for local dns. I never have to remember ips any more as long as I named the box something I can remember.
wish someone would make a windows avahi autoip client. it would make my life very easy.
ROKU_DEV_TARGET in the command referenced is just a bash environment variable. It's something that gets passed to the make command on run.
All the following would work, assuming the addresses/hostnames are reachable/resolvable:
ROKU_DEV_TARGET=192.168.0.10 make install
ROKU_DEV_TARGET=roku01.local make install
ROKU_DEV_TARGET=roku02.local make install
or even:
export ROKU_DEV_TARGET=roku01.local
# Do some stuff
make install # Installs into roku01
export ROKU_DEV_TARGET=roku02.local
# do some other stuff,
make install # installs into roku02
ROKU_DEV_TARGET=roku01.local make install # Installs into roku01 FOR THIS COMMAND
make install # Installs into roku02 because the main environment var is still set to that
The nice benefit of the makefiles included is that you don't have to zip the channel. They do that automatically ("make" will zip the channel for deployment, "make install" implies first a make, then the install portion which uses curl to upload it). You can also set certain files to not be included automatically in the zip, in case they are purely for local development (such as the Makefile itself, or any buffer/swap files from editors left around during zip). In addition to that, when creating the zip, it actually first zips up all PNG files it finds with no compression (they already have their own compression), and then all the other files with max compression.
There's something to be said for having much of the complexity bundled with the development environment itself (the guts of the makefiles are actually in a single app.mk file, shared/loaded by the individual Makefiles for each sample channel).
There's nothing wrong with rolling your own deployment system, but it's worth seeing what Roku's already provided, because they may have a few tricks you haven't considered (I hadn't noticed the separate compression for PNG files before looking closer at the file when writing this post).
-- GandK Labs
Check out Reversi! in the channel store!
