Few questions about building the DSF 3.4.x

Arplyu

Hi! I'd like to add some minor changes to the DSF. As a first step, I tried to build standard version myself, and the process looked successful but in reality not everything is clear.

Could anybody please answer these questions:

Which way is actually preferred - makefile in the root directory, or build.sh in /pkg?
I haven't found in either of those files a target for building reprapfirmware package - what am I missing?
I compiled .deb for 64-bit raspiOS. If I understand correctly, aarch64 (as it is named in pkg/build.sh) is just another name for the same architecture, but attempt to install from this package fails with package architecture (aarch64) does not match system (arm64) (though uname gives aarch64!). Is it known problem?

(please take into consideration these points:

I need to build version 3.4.4, maximum 3.4.6 - for compatibility with the modified RRF.
I haven't had experience with .NET stuff and with building .deb packages by myself before, sorry if some questions seem too primitive for experienced users
my goal is to do compilation of .deb packages for standard raspiOS (both 32 and 64 bits) on my x86-64 ubuntu machine)

Thank you

chrishamm

@Arplyu HTH:

The Makefiles were contributed, I don't maintain them. The build.sh is the proper way to generate .deb packages
Our reprapfirmware package is built on our package server because a headless Eclipse build was barely possible in the past and because that gives us the option to push multiple RRF builds for the same DSF version. If you need the code for that package, I can set up a new repo for it
We actually provide arm64 packages, AFAIR the build.sh script has a switch for that, too

chrishamm

@Arplyu Here's a copy of the RepRapFirmware package files including basic instructions on how to build it: https://github.com/Duet3D/RepRapFirmware-pkg

Arplyu

@chrishamm

Roger
Thanks a lot, I will check it out asap
Just tested passing --target=arm64 , seems to build it. I was a little bit confused that this option was not listed in the help. Will try those packages on my raspi a little later.

Thank you very much! I'll get back here if have further questions

Arplyu

@chrishamm
I built all deb packages for arm64 (for 3.4.4), installed them successfully. I increased SPI buffer size as explained to 8192. Then I enabled both DuetControlServer and DuetWebServer services; successfully connected to DWC from the browser. A macro file created from DWC appeared on the Raspi... BUT! Running tools like CodeConsole and ModelObserver fail with Failed to connect to DCS. There is one suspicious record in logs, despite I mentioned above:

Sep 13 13:42:50 core DuetControlServer[1745]: [warn] Kernel SPI buffer size is smaller than RepRapFirmware buffer size (4096 configured vs 8192 required)

Could that be a problem? If yes, what is wrong? shouldn't file /etc/modprobe.d/spidev.conf have set the right size? Or may be I've missed some step in the setup?

Thanks!

UPD: I increased buffer size as explained here, the warning from service's log disappeared, but still cannot connect to DCS

chrishamm

@Arplyu Your user must br part of the dsf group or invoke it as root.

Arplyu

@chrishamm thanks! Now everything works fine!