[En-Nut-Discussion] Working Windows build?

[Thiago A. Corrêa]

Somewhere you have a wrong toolchain selected. See the logs says it's
creating makefiles for arm-gcc but then the build logs are trying to
use makedefs for avr-gcc

When using qnutconf you have to check in settings if everything is
correct, specially the toolchain. With nutconfigure I have no ideia
but I guess you have to specify each time you run.

On Tue, Mar 31, 2020 at 8:45 AM Nikolas Becker <N.Becker at pemtec.de> wrote:
>
> Hi Uwe,
>
> I tried:
> Nutconfigure -c nut/conf/ethernut50f.conf -s /nut -b /nutbld -m arm-gcc create-buildtree
> And several other folder combinations. It gives:
> nutconfigure 2.0.10
> Loading ./nut/conf/repository.nut...OK
> Loading nut/conf/ethernut50f.conf...OK
> Creating Makefiles for arm-gcc in /nutbld...OK
> Creating header files in /nutbld...OK
>
> Then I tried to run make in the nutbld-folder. It gives:
> make -C arch
> make[1]: Entering directory `D:/dev/trunk/Ethernut/ethernut-head/nutbld/arch'
> makefile:38: /nut/Makedefs.avr-gcc: No such file or directory
> makefile:52: /nut/Makerules.avr-gcc: No such file or directory
> make[1]: *** No rule to make target `/nut/Makerules.avr-gcc'.  Stop.
> make[1]: Leaving directory `D:/dev/trunk/Ethernut/ethernut-head/nutbld/arch'
> make: *** [all] Error 2
>
> Any advice?
>
> Best regards,
>    Nikolas
>
> -----Ursprüngliche Nachricht-----
> Von: en-nut-discussion-bounces at egnite.de [mailto:en-nut-discussion-bounces at egnite.de] Im Auftrag von bon at elektron.ikp.physik.tu-darmstadt.de
> Gesendet: Dienstag, 31. März 2020 11:39
> An: Ethernut User Chat (English) <en-nut-discussion at egnite.de>
> Betreff: Re: [En-Nut-Discussion] Working Windows build?
>
> Nikolas Becker writes:
> > I tried stm3210e-eval.conf and stm3240g-eval.conf. Always the same:
> > the makedes and makerules cannot be found.
> > Besides, I currently want to build the predefined ethernut50f.conf
> > file, since I use that board.
> >
> Did you try pure nutconfigure? For a given configuration, nutconfigure is the easiest way to go. qnutconf is only helpfull if you want to setup/change a configuration in a graphical way with online help on the configuration items.
>
> It boils down to create the tree
> $(NUTCONFIGURE) -c $(CONF) -s $(NUTSOURCE) -u . create-buildtree
> $(NUTCONFIGURE) -c $(CONF) -s $(NUTSOURCE) -u . create-usertree
>
> But anyway, the qnutconf issues should get fixed...
>
> Bye
> --
> Uwe Bonnes                bon at elektron.ikp.physik.tu-darmstadt.de
>
> Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
> --------- Tel. 06151 1623569 ------- Fax. 06151 1623305 --------- _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion