[Ovmsdev] How to reproduce exatly the same ovms3.bin (3.2.002-151-g56116fe) build

[Bernd Geistert]

Hi all,

I would like to have a defined toolchain for building ovms3.bin, so that
I can reproduce the same binary (for the same GIT #tag of course) from
where I can start and later share own development.

I have downloaded the "reference" ovms3.bin (3.2.002-151-g56116fe Thu
Aug 1 16:04:20 UTC 2019 Automated build (markhk8), size = 2594192
bytes), but this is different to my own build in the mingw32 console using

$ make clean
$ make all
Toolchain path: /opt/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc
Toolchain version: crosstool-ng-1.22.0-80-g6c4433a5
Compiler version: 5.2.0
Python requirements from C:/msys32/home/.../esp/esp-idf/requirements.txt
are satisfied [Python 3.7.3]

App "ovms3" version: 3.2.002-151-g56116fe1
CC build/app_update/esp_app_desc.o
AR build/app_update/libapp_update.a
Build version is 3.2.002-151-g56116fe1
CXX build/main/ovms_version.o
AR build/main/libmain.a
Generating libapp_update.a.sections_info
Generating libmain.a.sections_info
Generating esp32.project.ld
LD build/ovms3.elf

$ ls -l build/ovms3.bin
-rw-r--r-- 1 Matthias None 2592512  5. Aug 21:12 build/ovms3.bin

At first, my ovms3.bin build was size 3036096, but I modified the make
menuconfig default 'Compiler Optimization' from 'Default' to 'Release',
the size inow similar to edge/ovms3.bin, but not the same.

Maybe someone could tell about other important settings in "IoT
Development Framework Configuration", maybe this could be the path to
match exactly markhk8's setting for 'Automated build'?

I described this also in https://www.openvehicles.com/node/2263

Regards

Matthias