Custom inisetp.py

[ste7anste7an]

I would like to start an internal test script upon starting micopython

from test_dut import *
start_test()

The way I did that before was by copying a patched inisetup.py to the ports/esp32/modules directory and effectively overwriting the existing inisetp.py.

Now, when I want to automate this in the lvgl_micropython environment, the lib/micropython directory does not exist when I start building.

What would be a good way for replacing inisetup.py or just adding a few lines to the existing one?

[asherevan]

You can simply place your inisetup.py file into the mpyupdates folder in the repository, making sure you keep the directory structure.

[ste7anste7an]

Thanks! I will try that.

[kdschlosser]

I thought of it all, well just about everything that a person could want to do with customizing. You can create a github repo add this binding as a submodule and add your own build.py script that can initialize the submodule and then place whatever files into the mpy_updates folder and then launch the build. It's pretty easy to do. Just use os.system to start a subprocess that collects the submodules and runs the build script.

[ste7anste7an]

Is mpy_updates or mpyupdates an existing folder? Should I create it in the root of the lvgl_micropython? Do i need to make a subdir esp32 or does it take all files from it. Or is it the 'micropy_updates' folder?

I strangely do not find mpyupdates nor mpy-updates in the scripts in the repo (doing a grep -r in the repo).

[ste7anste7an]

I created a subdirecotry micropy_updates/esp32/modules and put my inisetup.py in that direcotry before building. That seems to work!

[kdschlosser]

Sorry. it's micropy_updates not mpy_updates My bad on that one.