It looks like the extension got messed up. If that's the case renaming mkconfig.exe to mkconfig should at least build.
On Tue, Oct 13, 2020 at 10:45 PM Eduard Niesner <niesneredu...@gmail.com> wrote: > > Yeah, there is definitely something wrong - I just tried again (ubuntu for > windows 10). > > 1. Cleaned everything (git clean and make distclean) > 2. checked that the *mkconfig.exe* or any other *mkconfig *binary does > not exist in the tools folder > 3. called './tools/configure.sh -u nucleo-h743zi:nsh' > 4. called 'make' > 5. mkconfig*.exe *showed up in the tools folder. > > I even tried to make fresh clones of nuttx and apps and run the above steps > again. > I am not sure what else I could try.. > > Edi > > On Wed, Oct 14, 2020 at 12:29 AM Gregory Nutt <spudan...@gmail.com> wrote: > > > > > > I used 'make V=1' and I saw that mkconfig is being built successfully. > > > > > >> root@edi-laptop:/mnt/d/Work/Development/Git/GitHub/nuttx# make V=1 > > >> make -C tools -f Makefile.host mkconfig.exe > > >> make[1]: Entering directory > > >> '/mnt/d/Work/Development/Git/GitHub/nuttx/tools' > > > > No, the binary tools/mkconfig is NOT being built. Instead, > > tools/mkconfig.exe is being built. That will not work on Ubuntu for > > windows. There is something screwed up in your configuration. > > Specifically EXEEXT must be .exe??? But that should not happen unless > > you are actually trying to build for Windows Cygwin or MSYS. > > > > > I also checked the tools directory and there is a mkconfig.exe that was > > > created about the same time when I called make v=1. > > Again that is wrong. It is expecting tools/mkconfig, and NOT > > tools/mkconfig.exe > > > >
