I have a problem with building the firmware with make -C mpy-cross.
I get an error with: Use make V=1 or set BUILD_VERBOSE in your environment to increase build verbosity
I follow this tutorial: https://github.com/micropython/micropyt ... sp32/esp32
What I am doing wrong.
Esp32 make is not working
Re: Esp32 make is not working
is not an error message. Better go into the mpy-cross directory and run:Use make V=1 or set BUILD_VERBOSE in your environment to increase build verbosity
make
Re: Esp32 make is not working
I also tried that but then I get the same warning.
Use make V=1 or set BUILD_VERBOSE in your environment to increase build verbosity
Thanks
Use make V=1 or set BUILD_VERBOSE in your environment to increase build verbosity
Thanks
Re: Esp32 make is not working
Thanks. But into the mpy-cross dir with make I get the same error
Re: Esp32 make is not working
That's not an error. If that's the only thing you see then it means everything is up-to-date.
If you really want to see it build then do: The message about using V=1 is printed everytime you run make.
If you really want to see it build then do:
Code: Select all
make clean
make
Re: Esp32 make is not working
Thanks for the reply
Now it is compiling.
Thanks
Now it is compiling.
Thanks
- pythoncoder
- Posts: 5956
- Joined: Fri Jul 18, 2014 8:01 am
- Location: UK
- Contact:
Re: Esp32 make is not working
@input I suspect you're unfamiliar with make. It only compiles a file if the source file is newer than the object file (the file output by the compiler). This saves a lot of time in development: you edit one file in a big project and make ensures that file alone gets compiled.
So, if everything is up to date, make just verifies that fact and terminates. It issues the message you see every time it runs, whether or not it has to compile any files. As others have said, it's not an error message: it's what you expect to see when everything is up to date.
make clean forces it to recompile everything by deleting all the object files. It's not usually necessary but it's a useful trick if you suspect something has gone wrong with the build phase.
So, if everything is up to date, make just verifies that fact and terminates. It issues the message you see every time it runs, whether or not it has to compile any files. As others have said, it's not an error message: it's what you expect to see when everything is up to date.
make clean forces it to recompile everything by deleting all the object files. It's not usually necessary but it's a useful trick if you suspect something has gone wrong with the build phase.
Peter Hinch
Index to my micropython libraries.
Index to my micropython libraries.
-
- Posts: 288
- Joined: Sun May 04, 2014 8:54 am
Re: Esp32 make is not working
Code: Select all
make -B