#174575 - Michoko - Sun Jun 27, 2010 1:53 pm
Hi,
I'm considering switching from EFSlib to NitroFS, for handling the extra assets of my games embedded into my homebrews.
First, I thought that NitroFS required the linker to be ARGV compatible, forcing either to use a compatible firmware, or HBmenu. If it was the case, that would still prevent my homebrews from running on older, not-updated linkers.
But then I stumbled upon this page: http://blea.ch/wiki/index.php/Talk:Nitrofs#Finding_filename_for_nitroFSInit.28.29
where the original author of NitroFS had made a generic function to locate automatically the ROM we are currently running. My question is: does DevkitARM use this function, in case no filename was passed through ARGV? In that case, I suppose it works on any linker, it's just slower to init? (because it scans every rom?)
Thank you for your reply!
Michoko
I'm considering switching from EFSlib to NitroFS, for handling the extra assets of my games embedded into my homebrews.
First, I thought that NitroFS required the linker to be ARGV compatible, forcing either to use a compatible firmware, or HBmenu. If it was the case, that would still prevent my homebrews from running on older, not-updated linkers.
But then I stumbled upon this page: http://blea.ch/wiki/index.php/Talk:Nitrofs#Finding_filename_for_nitroFSInit.28.29
where the original author of NitroFS had made a generic function to locate automatically the ROM we are currently running. My question is: does DevkitARM use this function, in case no filename was passed through ARGV? In that case, I suppose it works on any linker, it's just slower to init? (because it scans every rom?)
Thank you for your reply!
Michoko