Skip to content

Releases: earlephilhower/mklittlefs

4.0.2 - Proper 64b time attributes, newer MacOS/Xcode

21 Dec 18:14
db0513a
Compare
Choose a tag to compare

Overview

LittleFS doesn't have native file creation/access time support, so we utilize LFS attributes to store time_t timestamps on creation (and on use in the ESP8266 and Pico). However, time_t went from 32bits->64bits in recent Newlibs to avoid the year 2038 problem but mklittlefs was still truncating time_t to 32bits. This would cause timestamps of files to read out as time==0 in those cores.

This removes the 32bit kludge and writes the full 64bit time_t to the attribute.

Also, unfortunately, GitHub has deprecated older Mac X86 runners and XCode versions. The release build is still using the oldest version of MacX86 runner and XCode available, but those have been bumped up one major release.

What's Changed

Full Changelog: 4.0.1...4.0.2

4.0.1

03 Sep 23:10
cc32c94
Compare
Choose a tag to compare

What's Changed

  • Include necessary Win-Pthreads DLL for MINGW builds.

Full Changelog: 4.0.0...4.0.1

Release 4.0.0 - LittleFS updates, Mac M1/ARM support

03 Jun 19:34
Compare
Choose a tag to compare

TWO POTENTIALLY BREAKING CHANGES

  1. LittleFS has been upgraded from 2.5.1 to the latest 2.9.3 release. At release 2.6.0 the on-flash format for LittleFS changed. LittleFS >= 2.6.0 can read 2.5.0 formats but not vice-versa.
  • If you have not upgraded the LittleFS on your system to 2.6.0 or later, please stick with earlier releases of this package or you will be unable to use the generated filesystems.
  1. LFS_NAME_MAX set to 255, the default. It was set in prior releases to 32 for ESP8266 memory reasons but since that platform is EOL there's no reason to limit names so severely.
  • If your code is already setting LFS_NAME_MAX to 255, or you don't set it at all (and hence it will default to 255) then this change is a no-op.
  • If your code, like on the ESP8266 and older Arduino-Pico releases, does set this define to 32 then, again, the filesystem will not be usable onboard. The fix is to set the constant to 255 (at the same time as updating your LittleFS release)

New binaries

Binaries are now built using GitHub actions and runners, and include ARM-based Mac (M1/M2/M3...) builds.

What's Changed

  • Use snprintf instead of sprintf for security reasons by @uztbt #39
  • Follow littlefs file name spec, update for compiling for c++ 20, update gitignore for binaries by @Szybet #43
  • BREAKING: Move to latest LittleFS release, v2.9.3 by @earlephilhower #44

New Contributors

Full Changelog: 3.2.0...4.0.0

Release 3.2.0 - Add --from-file option

23 Sep 17:30
975bd0f
Compare
Choose a tag to compare
Merge pull request #37 from earlephilhower/readline

Update to the latest Apple compiler for cross

Release 3.1 - Minor ease of use fixes

29 Jan 17:30
4aca452
Compare
Choose a tag to compare
  • Upgrade to LittleFS 2.5.1
  • Expand --version information
  • Automatically pick FS size for unpack/list

Fix support for paths > 32 bytes in total

16 Aug 19:55
295fe9b
Compare
Choose a tag to compare

Minor update to fix an issue where if the total path depth of a file was >32 it would crash.

Bugfix to match Arduino Core LittleFS config

25 Jun 20:16
7f77f2b
Compare
Choose a tag to compare
Merge pull request #2 from earlephilhower/update

 Match the LittleFS version and settings in 8266 core

Update to LittleFS V2

12 Apr 02:37
Compare
Choose a tag to compare
2.5.1-1

Minor build script fix

Add subdirectory support

18 Dec 05:03
Compare
Choose a tag to compare
2.5.0-3

Clean up add'l OS warnings

Initial release

16 Dec 05:35
Compare
Choose a tag to compare
Support fake directory names

Use same renaming scheme to make subdir markers into 0x01/vice versa.