skeezix
Internal Development
hey guys,
I've been super busy as hell, but I do have my BattleJewels and OutcaST nearly ready for Wiz, and possibly HAtari as well. Just I'm overtiming like hell right now :/
Anyway, BattleJewels currently uses libiconv (an older version too), shared lib. Its not in firmware, and copying it into firmware is a little much to ask of people (despite being easy to do). My thought is to just include it with the game, so the user will put the BattleJewels launch script (.gpe), the bin, and the libiconv.so into the same dir and be good to go. (I'll have to look up the .ini file silyness the new launcher supports, one of these days..)
We don't have any standard established yet to stick shared libs in a common location, right? (ie: We could all use LD_LIBRARY_PATH=/mnt/sd/WizLibs or somesuch, or embed the LD-path into the build script or ELF header, etc.)
For now I'll just assume to include it with my apps..
jeff
I've been super busy as hell, but I do have my BattleJewels and OutcaST nearly ready for Wiz, and possibly HAtari as well. Just I'm overtiming like hell right now :/
Anyway, BattleJewels currently uses libiconv (an older version too), shared lib. Its not in firmware, and copying it into firmware is a little much to ask of people (despite being easy to do). My thought is to just include it with the game, so the user will put the BattleJewels launch script (.gpe), the bin, and the libiconv.so into the same dir and be good to go. (I'll have to look up the .ini file silyness the new launcher supports, one of these days..)
We don't have any standard established yet to stick shared libs in a common location, right? (ie: We could all use LD_LIBRARY_PATH=/mnt/sd/WizLibs or somesuch, or embed the LD-path into the build script or ELF header, etc.)
For now I'll just assume to include it with my apps..
jeff