Setting Up Eclipse For the new Firmware

jml

It seems to have compiled with no errors! The fix was using the "dev" and "v2-dev" of DuetWiFiSocketServer and CoreNG respectively. I will tomorrow actually test it on the Duet2 and the previous Duet board to make sure it runs properly.

Thanks for all the help everyone!

JoergS5

@dc42 I know, I wanted to have it complete. Still searching where Arduino.h reference is in the code (in respect to "You don't need to compile that project" for DuetWifiSocketServer)

jml

RRF compiles in 7 seconds. I remember it used to be 19 seconds when I was on version 1.20. Is this normal?

JoergS5

@jml If parts are already built, it does not recompile. This may be the reason.

JoergS5

@dc42 ( not relevant for @jml)

DuetWifiSocketServer compiling, I found your discussion
https://forum.duet3d.com/topic/4984/cant-build-duetwifiserver
I will try this approach the next days.

jml

@joergs5 are we supposed to be building DuetWiFiSocketserver? I was looking at the forum in your link and I'm wondering why eBerlin is building DuetWifiSocketServer, and why there is discussion about LwipESP8266 ... was that just the older way of doing things?

If I try to build DuetWiFiSocketserver, I get these errors

/bin/sh: xtensa-lx106-elf-g++: command not found
make: *** [src/Misc.o] Error 127
make: *** [src/HSPI.o] Error 127
make: *** [src/SocketServer.o] Error 127
make: *** [src/Listener.o] Error 127
make: *** [src/Connection.o] Error 127

JoergS5

@jml This project is firmware which is uploaded to the WiFi module on the Duet ESP8266 based (like an ESP-12 module). You don't need to compile or change it to be able to change RepRapFirmware or a fork of it that you can make. The only part you need is this one .h file, but from the dev branch.

The Lwip and ESP8266 projects are projects which are needed by this WiFi project (you mentioned them in one of the first comments). In The forum blog I mentioned was an older project which was replaced by the DuetWifi project.

Your errors are path errors, you need to change the paths the same way as in the other projects, changing to the new GNU classes, adding your make path. But it's more complicated because of the other projects needed.

The xtensa files are (in windows) in the users\username... directory, you must change the information in the project, if your username is not David The files are created, when you install Arduino 1.8.5

But as I said, you don't need it now. BUT - if you're interested to compile because you're interested like me, we can discuss here how to compile.

jml

@joergs5 Thanks for the explanation. I'll stick to just compiling the others for now Hopefully what I have done will work when I put it on the Duet2 tomorrow.

dc42

I have just synced the master, dev and v2-dev branches of RepRapFirmware and CoreNG with each other, so all 3 branches are now up to date with release 2.01/1.22 of RRF.

wilriker

@dc42 Thanks. Finally I can also compile everything out of the box (except for binary path). But I had to create a Pull Request that fixes three includes that are not found in case-sensitive file-systems otherwise.

dc42

I've just accepted your PR. Unfortunately, Eclipse under Windows doesn't warn against mismatched letter case in include file names, so this type of error slips in occasionally.

wilriker

@dc42 I know, I had my fun with case-(in)sensitivity on Windows<->Linux already a couple of times. I will then occasionally send PRs to fix this.

jml

Just an update. I had tested the RRF and it worked on the Duet. Yay!

But now that dc42 has "synced the master, dev and v2-dev branches" of RRF and CoreNG, it seems like next time it should be easier.