New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
version of Slic3r Prusa edition or PrusaControl running on arm H3 (armhf or appimage) ? #564
Comments
There is also already Slic3r projects in OBS : enter slic3r in https://build.opensuse.org/search |
Will the old Slic3r 1.2.9 run for you? I may get in touch with Chow Loong Jin, who maintains the Debian package, to get a hint why / how the Slic3r PE is failing to build on ARMs at the Debian's build servers. Frankly porting Slic3r to ARM does not have much of a priority as the slicing is too slow on those little critters. |
Thanks a lot for your reply.
I can't have the user interface, slic3r doesn't appear. |
Sorry, we don't have resources as of now to prepare an ARM build. You may try to compile the Slic3r PE on your ARM and I will try to help you to solve your issues along the way. But it may take many iterations and I cannot promise a success. We don't have an up to date build process description for LInux as of now, but the following should mostly work: you will also need to install the intel thread building block package. |
Thanks a lot for your reply, sorry for the delay I was searching partners and help for the project and trying to make a SBC x86 demo in order to start making demonstration. Thanks a lot for your help ! I have tried to to make this : https://build.opensuse.org/package/show/home:Ucino/Slic3rPrusaEdition but it doesn't work actually. I have looked the spec files of other user that have build slic3r standard (https://build.opensuse.org/search and enter slic3r) (ie: https://build.opensuse.org/package/show/home:cgiboudeaux/slic3r ). Do you think it will be easier than building on the arm ? (if yes I will try to solve the obs problem, if no I will try to learn to compile it on the ARM). |
@openelearning Sorry, I cannot answer any of your questions without investing a lot of time. |
@bubnikv Ok, thanks for your reply, I will try to learn OBS, if I failed, I will try to to learn to compile the Slic3r PE on my ARM. |
thanks to @eyal0 that give these informations : "These are the instructions that I used for compiling Slic3r on a RaspberryPi with OctoPi: https://github.com/OctoPrint/OctoPrint-Slic3r/wiki/How-to-install-Slic3r-on-RPi" |
On https://packages.debian.org/sid/slic3r-prusa we can find that there is an armf version of slic3r PE It's maybe a very good news :) I will try to learn how I can make a nice spec file https://build.opensuse.org/package/show/home:Ucino/Slic3rPrusaEdition. It seems that one of the step for this is to complete the dependencies for the build on the spec file, i think that https://packages.debian.org/sid/slic3r-prusa and https://github.com/OctoPrint/OctoPrint-Slic3r/wiki/How-to-install-Slic3r-on-RPi can help me for that. Let's see... |
@openelearning I tried to install the armhf package on my OctoPi Raspberry Pi but it didn't work. I think that it's due to missing dependencies.
All the libboost 1.62 stuff is unavailable. I also had this problem when trying to compile >=1.38.0. I can't find that version from Thanks. |
@eyal0 I wanted to accept your legacy boost compatibility patch, but I cannot find it. Would you please remind me where did you post it? Thanks. |
@bubnikv I intentionally didn't make a PR because I think that supporting old boost is a bad idea. I was able to install new boost on RPi and compile the code without these changes. And the changes make the code look worse, not better. For most people, having a modern libboost won't be a problem. So I think that you should not do these changes. And you're not running old boost so you might at any point re-break old boost compatibility and we'd have to make another patch. That said, here they are: eyal0@af6eae7 I also need to use this link to get it working: http://www.boost.org/doc/libs/1_65_1/boost/spirit/home/qi/copy.hpp I didn't copy the first line of that function, not sure if it'll work. Actually, since I've already installed the new libboost on my system, I no longer have an easy way to test if it's broken with Boost1.55 unless I reformat my RPi! |
Thanks, I will have to sleep on it.
…On Tue, Dec 5, 2017 at 8:56 PM, Eyal ***@***.***> wrote:
@bubnikv <https://github.com/bubnikv> I intentionally didn't make a PR
because I think that supporting old boost is a bad idea. I was able to
install new boost on RPi and compile the code without these changes. And
the changes make the code look worse, not better. For most people, having a
modern libboost won't be a problem. So I think that you should not do these
changes. And you're not running old boost so you might at any point
re-break old boost compatibility and we'd have to make another patch.
That said, here they are: ***@***.***
<eyal0@af6eae7>
I also need to use this link to get it working:
http://www.boost.org/doc/libs/1_65_1/boost/spirit/home/qi/copy.hpp
I didn't copy the first line of that function, not sure if it'll work.
Actually, since I've already installed the new libboost on my system, I no
longer have an easy way to test if it's broken with Boost1.55 unless I
reformat my RPi!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#564 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFj5I6JXwX4c1UrT5pnenJEIK5ztgUwPks5s9aAFgaJpZM4QO9lR>
.
|
@hyperair maybe you have some ideas where I can try to investigate in order to have https://build.opensuse.org/package/show/home:Ucino/Slic3rPrusaEdition# working for appimage armv6l or armv7l (they are both excluded), for example if I had to find some package to add in BuildRequires: in https://build.opensuse.org/package/view_file/home:Ucino/Slic3rPrusaEdition/slic3rPrusaEdition.spec?expand=1 ? [edit : the solution was to use appimage.yml file instead of .spec file] |
This page will be very usefull : https://github.com/AppImage/AppImageKit/wiki/Using-Open-Build-Service & https://build.opensuse.org/package/show/OBS:AppImage/AppImageKit |
Here some new test using OBS to make armv7 appimage (without success actually, I have 2 errors : nothing provides perl(OpenGL), nothing provides perl(Wx::GLCanvas) ) : https://build.opensuse.org/package/show/home:Ucino:branches:OBS:AppImage:Templates/Slic3rPrusaEdition# |
You may need to build and install the two packages using cpan. Those
packages would likely be installed by running
perl Build.PL
from inside the Slic3r directory.
But take these advices with a grain of salt, I have no experience with the
OBS, so I don't know what kind of functionality it offers.
…On Thu, Dec 7, 2017 at 2:03 AM, openelearning ***@***.***> wrote:
Here some new test using OBS to make armv7 appimage (without success
actually, I have 2 errors : nothing provides perl(OpenGL), nothing provides
perl(Wx::GLCanvas) ) : https://build.opensuse.org/package/show/home:Ucino:
branches:OBS:AppImage:Templates/Slic3rPrusaEdition#
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#564 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFj5Iw-hsAxSxzsdNLN5j_hT2rWqwBVDks5s9zllgaJpZM4QO9lR>
.
|
Thanks a lot for your help @bubnikv :) luc14n0 is helping to make an appimage on https://build.opensuse.org/package/show/home:luc14n0/slic3r and he solve the problem of perl(OpenGL), and perl(Wx::GLCanvas). He's trying to solve other problems now. |
You may guys try to compile the current Slic3r master on ARM. A command-line slic3r is compiled with an additional cmake switch
|
No response. I was able to compile PrusaSlicer on an Android e-ink reader, so you should be able to compile on whatever reasonable ARM distribution you pick. |
I'm really sorry for not having replied before. Thanks a lot for the link, this will help me, and this really usefull that we can now use PrusaSlicer on arm distribution. For the moment I have give up the use nanocomputer to make gcode, but I will try later, and give you feedback. The project is going well, French schools want to benefit it, and the project has been nominated for an innovation competition. A pedagogical project have been also made to show the interest of open source and open hardware solutions : https://www.open-elearning.com/magano/magano-education/monumentuss/ |
(for the moment nanocomputer has been replaced by old computer as you can see on this project : https://www.open-elearning.com/magano/magano-education/equiper-ethiquement-les-ecoles-primaires/ the goal of this second project is to find solutions to make easy to any school to have open source and open hardware digital tools (computer, 3D printer, IA module...). |
@bubnikv shall we make an AppImage for Raspberry Pi? |
@probonopd appimage for Raspberry PI would be nice. We need to find some
time to set up a build server for another target.
so 25. 5. 2019 v 1:26 odesílatel probonopd <notifications@github.com>
napsal:
… @bubnikv <https://github.com/bubnikv> shall we make an AppImage for
Raspberry Pi?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#564?email_source=notifications&email_token=ABMPSI4COMH5WZHZ4LGULQTPXB2SLA5CNFSM4EB33FI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWGYDUQ#issuecomment-495813074>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABMPSIZ2P5W6WQPOXNXG543PXB2SLANCNFSM4EB33FIQ>
.
|
We produce some ARM binaries for https://github.com/AppImage/AppImageKit/releases using Travis CI and Docker images for crosscompiling. Maybe @TheAssassin can give you some hints. |
Thanks for the hint.
po 3. 6. 2019 v 16:35 odesílatel probonopd <notifications@github.com>
napsal:
… We produce some ARM binaries for
https://github.com/AppImage/AppImageKit/releases using Travis CI and
Docker images for crosscompiling. Maybe @TheAssassin
<https://github.com/TheAssassin> can give you some hints.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#564?email_source=notifications&email_token=ABMPSI6E44UTYHMGGEO2EB3PYUT4VA5CNFSM4EB33FI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWZTHHA#issuecomment-498283420>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABMPSI2AFRWDU477QT5I2I3PYUT4VANCNFSM4EB33FIQ>
.
|
Any details on how to compile and run on android for the command line version. I have managed to use busy box on android and would love to use this thing. |
Got it working, but it is quite convoluted and the software 3D rendering is very slow. |
Hello,
I'm trying to make possible to deploy open source and open hardware nano computer and 3D printing for schools in France. Actually it seems that Original Prusa i3 MK3 and H3 SBC are a good choice for this. In order that the children could slice their 3D object, a slicer is needed, but it seems that actually there isn't Slic3r Prusa edition or PrusaControl running on arm H3 (armhf or appimage).
Operating system type + version
I'm using armbian for Orange PiPC+, the ubuntu xenial 16.04 legacy kernel that run armhf https://www.armbian.com/orange-pi-pc-plus/
Behavior
I don't know how a children using stl files could make gcode for Original Prusa i3mk2 /mk3 with an H3 arm Single Board Computer.
The children could have a nice gcode that runs on Prusa i3 MK2/3 :)
Other information that could help
OBS can now make AppImage that are running on H3 SOC - armhf, as t-paul has greatly made an OpenScad version that is running on H3 boards : Create portable image for Linux openscad/openscad#1849 (comment)
It seems that someone has used a part of slic3r on RBPI : Int128 is broken on RaspberryPi by a6ea01a #506
https://github.com/OctoPrint/OctoPrint-Slic3r/wiki/How-to-install-Slic3r-on-RPi
https://github.com/OctoPrint/OctoPrint-Slic3r
http://bukobot.com/raspberry-pi-slice
Is it possible to have a version of Slic3r Prusa edition or PrusaControl running on arm H3 (armhf or appimage) ?
If yes, what I can do to help for this ? (I'm newbie in building package / compilation / using OBS, but I can spend time on learning, searching information, try to make crowdfunding for this...)
Thanks for your attention and help
The text was updated successfully, but these errors were encountered: