Don't copy to CTRNAND if building for exploit mode
While the copy to NAND process is generally a good idea for end users, this can quickly get annoying for actual developers looking to test low level stuff or contribute to Luma3DS if a testing FIRM gets sent to the NAND.
This commit is contained in:
parent
f40a1cc47b
commit
3ecce3fc3e
@ -523,8 +523,10 @@ bool doLumaUpgradeProcess(void)
|
|||||||
#endif
|
#endif
|
||||||
|
|
||||||
// Try to boot.firm to CTRNAND, when applicable
|
// Try to boot.firm to CTRNAND, when applicable
|
||||||
|
#ifndef BUILD_FOR_EXPLOIT_DEV
|
||||||
if (isSdMode && memcmp(launchedPathForFatfs, "sdmc:", 5) == 0)
|
if (isSdMode && memcmp(launchedPathForFatfs, "sdmc:", 5) == 0)
|
||||||
ok = fileCopy(launchedPathForFatfs, "nand:/boot.firm", true, fileCopyBuffer, sizeof(fileCopyBuffer));
|
ok = fileCopy(launchedPathForFatfs, "nand:/boot.firm", true, fileCopyBuffer, sizeof(fileCopyBuffer));
|
||||||
|
#endif
|
||||||
|
|
||||||
// Try to backup essential files
|
// Try to backup essential files
|
||||||
ok2 = backupEssentialFiles();
|
ok2 = backupEssentialFiles();
|
||||||
|
Loading…
x
Reference in New Issue
Block a user