@yoctopuce FYI

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.37%. Comparing base (6515cd0) to head (c403bf2).

@@           Coverage Diff           @@
##           master   #17751   +/-   ##
=======================================
  Coverage   98.37%   98.37%           
=======================================
  Files         171      171           
  Lines       22228    22228           
=======================================
  Hits        21866    21866           
  Misses        362      362           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Code size report:

   bare-arm:    +0 +0.000% 
minimal x86:    +0 +0.000% 
   unix x64:    +0 +0.000% standard
      stm32:    +0 +0.000% PYBV10
     mimxrt:    +0 +0.000% TEENSY40
        rp2:    +0 +0.000% RPI_PICO_W
       samd:    +0 +0.000% ADAFRUIT_ITSYBITSY_M4_EXPRESS
  qemu rv32:    +0 +0.000% VIRT_RV32

@yoctopuce FYI

Makes sense. I see that <time.h> was included directly in the .c files present in ports/unix, hence the fact that the error did not come out earlier on Linux/windows builds.

I'm not sure if there's any better place to put this. But since typedef time_t mp_timestamp_t; is in py/mpconfig.h it seems prudent to put <time.h> in mpconfigport.h.

I agree, and it shouldn't hurt since this is port specific.