"jbrave" wrote:
I use a mac, and in addition to my ~/.bash_profile which has the ROKU_DEV_TARGET, I have two copies named after the ip address (I assign a fixed address from my router based on the mac addr), one each with a different target. When I want to upload I just type:
>source ~/.67
>make install
for roku A
>source ~/.69
make install
for roku B
Nice and simple. The reason one doesn't want to use the web interface becomes clear when you do hundreds of builds and tests per day, you would get carpel tunnel in a week.
- Joel
I think this is one of those culture things I dont get because although I have years of coding I avoided coding C.
now I can do ./configure; make; make install with the best of them. but making my own make files was something I always left to the c guys. I would write a script to do whatever the make file didn't. always have. Maybe its from having to administer thousands of boxes, I think how do I script around what someone else has forgotten to do or to customize to my situation instead of modifying the make file. Still don't think its as clean but it makes more sense now thanks to kbenson. I am going to finish the command line interface for the web interface. I am sure someone will use it. maybe some linux lurker. I may make a command line that looks for rokus on the network and creates a script to automatically "make" them to all rokus on the network or give you a choice of which ones. that script will use the environment variable.
