Disable LFS3_BMAP when LFS3_BIGGEST for now

Currently LFS3_BMAP implies LFS3_YES_BMAP, which is an ugly hack because
I don't want to figure out the BMAP flag logic right now.

As a side-effect, this makes it impossible to test LFS3_BIGGEST without
LFS3_BMAP, which breaks a number of tests that have not been updated to
support >2 format blocks.
This commit is contained in:
Christopher Haster
2025-08-05 01:03:41 -05:00
parent 83196ed67a
commit 8c04482ea3
+4 -3
View File
@@ -47,9 +47,10 @@
#ifndef LFS3_GC #ifndef LFS3_GC
#define LFS3_GC #define LFS3_GC
#endif #endif
#ifndef LFS3_BMAP // TODO how interact with bmap?
#define LFS3_BMAP // #ifndef LFS3_BMAP
#endif // #define LFS3_BMAP
// #endif
#endif #endif
// LFS3_YES_* variants imply the relevant LFS3_* macro // LFS3_YES_* variants imply the relevant LFS3_* macro