skeezix
Internal Development
Who has dev units? Perhaps we should start a registry of who 'claims' what, to avoid duplicating efforts right now? (ie: Is Squidge going ot 'take' Quake1?
)
Anyway, my question is..
What assumptions do we get to make? I know very few dev units are out, but I hope to get a regular user advance unit soon so could start devving in a bit.
ex: Which shared libs do we have on the devices virtual filesystem?
Do we need to force any shared-lib paths into the LD_CONFIG_PATH with an ELF-stamp? etc etc.. (ie: in gcc-speak, you'd " -Xlinker -R -Xlinker <path>"
ex: Which SDL version are they using? Do we have the source of their compiled environment so we know what SDL options were used, and can recompile witrh our own optimizations and inclusions/exclusions?
ex: What format is the framebuffer, and whats the device name for it? Or does the gcc295 it come with a closed source SDL modded to work appropriately?
Or do we just static-link everything and go?
(I've not looked at any SDKs, since I assume the gcc295 kit that was floating around was broken and out of date. Or is it actually usable to produce working binaries?)
jeff
I suppose it harkens back to the question from a month or two back.. they'll have to release the full source in a week or two, or there'll be fit hitting the shan
Anyway, my question is..
What assumptions do we get to make? I know very few dev units are out, but I hope to get a regular user advance unit soon so could start devving in a bit.
ex: Which shared libs do we have on the devices virtual filesystem?
Do we need to force any shared-lib paths into the LD_CONFIG_PATH with an ELF-stamp? etc etc.. (ie: in gcc-speak, you'd " -Xlinker -R -Xlinker <path>"
ex: Which SDL version are they using? Do we have the source of their compiled environment so we know what SDL options were used, and can recompile witrh our own optimizations and inclusions/exclusions?
ex: What format is the framebuffer, and whats the device name for it? Or does the gcc295 it come with a closed source SDL modded to work appropriately?
Or do we just static-link everything and go?
(I've not looked at any SDKs, since I assume the gcc295 kit that was floating around was broken and out of date. Or is it actually usable to produce working binaries?)
jeff
I suppose it harkens back to the question from a month or two back.. they'll have to release the full source in a week or two, or there'll be fit hitting the shan