discuss@lists.openscad.org

OpenSCAD general discussion Mailing-list

View all threads

Openscad on Raspberry pi.

RW
Rogier Wolff
Thu, Jan 3, 2019 2:06 PM

Hi,

My niece is getting a raspberry pi. I wanted to install openscad for
her on that, but it is not in the raspbian repository. The excuse seems
to be that a required library is missing.

I've installed dependencies with apt, and then tried to compile
openscad. Some tricky stuff with header files that clash amongst
eachother. (conflicting second declarations of a function.). I have
edited those headers to only include those declarations WITHOUT a
special define. This allowed me to compile openscad.

However now I'm at: "it crashes when opening the main window."

I've recompiled with debugging symbols and I'm going to try and figure
out where the crash happens. But I haven't gotten around to that part
yet.

Has anybody succeeded of running openscad on the pi?

Roger. 

--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2049110 **
**    Delftechpark 11 2628 XJ  Delft, The Netherlands. KVK: 27239233    **
-- BitWizard writes Linux device drivers for any device you may have! --
The plan was simple, like my brother-in-law Phil. But unlike
Phil, this plan just might work.

Hi, My niece is getting a raspberry pi. I wanted to install openscad for her on that, but it is not in the raspbian repository. The excuse seems to be that a required library is missing. I've installed dependencies with apt, and then tried to compile openscad. Some tricky stuff with header files that clash amongst eachother. (conflicting second declarations of a function.). I have edited those headers to only include those declarations WITHOUT a special define. This allowed me to compile openscad. However now I'm at: "it crashes when opening the main window." I've recompiled with debugging symbols and I'm going to try and figure out where the crash happens. But I haven't gotten around to that part yet. Has anybody succeeded of running openscad on the pi? Roger. -- ** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2049110 ** ** Delftechpark 11 2628 XJ Delft, The Netherlands. KVK: 27239233 ** *-- BitWizard writes Linux device drivers for any device you may have! --* The plan was simple, like my brother-in-law Phil. But unlike Phil, this plan just might work.
TP
Torsten Paul
Thu, Jan 3, 2019 2:23 PM

On 03.01.19 15:06, Rogier Wolff wrote:

I've installed dependencies with apt, and then tried to compile
openscad. Some tricky stuff with header files that clash amongst
eachother. (conflicting second declarations of a function.). I have
edited those headers to only include those declarations WITHOUT a
special define. This allowed me to compile openscad.

I suspect to get OpenSCAD compiled correctly on any 32bit ARM
system, a custom compiled Qt is needed. On most systems I've
seen so far, Qt is compiled against the "mobile" version of
OpenGL (GLES). OpenSCAD needs full desktop OpenGL. If both are
mixed, that results in the header file collision you've seen.

I don't know the details but it should be possible as earlier
Raspbian did include openscad in the distribution.

ciao,
Torsten.

On 03.01.19 15:06, Rogier Wolff wrote: > I've installed dependencies with apt, and then tried to compile > openscad. Some tricky stuff with header files that clash amongst > eachother. (conflicting second declarations of a function.). I have > edited those headers to only include those declarations WITHOUT a > special define. This allowed me to compile openscad. > I suspect to get OpenSCAD compiled correctly on any 32bit ARM system, a custom compiled Qt is needed. On most systems I've seen so far, Qt is compiled against the "mobile" version of OpenGL (GLES). OpenSCAD needs full desktop OpenGL. If both are mixed, that results in the header file collision you've seen. I don't know the details but it should be possible as earlier Raspbian did include openscad in the distribution. ciao, Torsten.
RW
Rogier Wolff
Thu, Jan 3, 2019 4:02 PM

On Thu, Jan 03, 2019 at 03:23:32PM +0100, Torsten Paul wrote:

On 03.01.19 15:06, Rogier Wolff wrote:

I've installed dependencies with apt, and then tried to compile
openscad. Some tricky stuff with header files that clash amongst
eachother. (conflicting second declarations of a function.). I have
edited those headers to only include those declarations WITHOUT a
special define. This allowed me to compile openscad.

I suspect to get OpenSCAD compiled correctly on any 32bit ARM
system, a custom compiled Qt is needed. On most systems I've
seen so far, Qt is compiled against the "mobile" version of
OpenGL (GLES). OpenSCAD needs full desktop OpenGL. If both are
mixed, that results in the header file collision you've seen.

Wait! I see plenty of explicit references to GLES while
compiling. Hmm. On second inspection: That's in compilation
command-lines and in the Makefile. So qmake is configured to use GLES
and puts -lGLESv2 into the Makefile?

So the plan would be to setup a chroot compilation-environment,
and compile Qt myself?

I don't know the details but it should be possible as earlier
Raspbian did include openscad in the distribution.

Right!

Roger. 

--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2049110 **
**    Delftechpark 11 2628 XJ  Delft, The Netherlands. KVK: 27239233    **
-- BitWizard writes Linux device drivers for any device you may have! --
The plan was simple, like my brother-in-law Phil. But unlike
Phil, this plan just might work.

On Thu, Jan 03, 2019 at 03:23:32PM +0100, Torsten Paul wrote: > On 03.01.19 15:06, Rogier Wolff wrote: > >I've installed dependencies with apt, and then tried to compile > >openscad. Some tricky stuff with header files that clash amongst > >eachother. (conflicting second declarations of a function.). I have > >edited those headers to only include those declarations WITHOUT a > >special define. This allowed me to compile openscad. > > > I suspect to get OpenSCAD compiled correctly on any 32bit ARM > system, a custom compiled Qt is needed. On most systems I've > seen so far, Qt is compiled against the "mobile" version of > OpenGL (GLES). OpenSCAD needs full desktop OpenGL. If both are > mixed, that results in the header file collision you've seen. Wait! I see plenty of explicit references to GLES while compiling. Hmm. On second inspection: That's in compilation command-lines and in the Makefile. So qmake is configured to use GLES and puts -lGLESv2 into the Makefile? So the plan would be to setup a chroot compilation-environment, and compile Qt myself? > I don't know the details but it should be possible as earlier > Raspbian did include openscad in the distribution. Right! Roger. -- ** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2049110 ** ** Delftechpark 11 2628 XJ Delft, The Netherlands. KVK: 27239233 ** *-- BitWizard writes Linux device drivers for any device you may have! --* The plan was simple, like my brother-in-law Phil. But unlike Phil, this plan just might work.
M
MichaelAtOz
Thu, Jan 3, 2019 11:20 PM

My vague recollection when I looked at it some years ago, was it could only
Render, so there must have been some way to exclude OpenGL in the build.
I keep my eye out for it, but have not come across any such boards with full
OpenGL (non-ES) yet. Can' say I've see every release tho.
It always seems to be SoC lacks support.


Admin - email* me if you need anything, or if I've done something stupid...

  • click on my MichaelAtOz label, there is a link to email me.

Unless specifically shown otherwise above, my contribution is in the Public Domain; to the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. Obviously inclusion of works of previous authors is not included in the above.

The TPP is no simple “trade agreement.”  Fight it! http://www.ourfairdeal.org/  time is running out!

Sent from: http://forum.openscad.org/

My vague recollection when I looked at it some years ago, was it could only Render, so there must have been some way to exclude OpenGL in the build. I keep my eye out for it, but have not come across any such boards with full OpenGL (non-ES) yet. Can' say I've see every release tho. It always seems to be SoC lacks support. ----- Admin - email* me if you need anything, or if I've done something stupid... * click on my MichaelAtOz label, there is a link to email me. Unless specifically shown otherwise above, my contribution is in the Public Domain; to the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. Obviously inclusion of works of previous authors is not included in the above. The TPP is no simple “trade agreement.” Fight it! http://www.ourfairdeal.org/ time is running out! -- Sent from: http://forum.openscad.org/
TP
Torsten Paul
Thu, Jan 3, 2019 11:43 PM

On 04.01.19 00:20, MichaelAtOz wrote:

My vague recollection when I looked at it some years ago,
was it could only Render, so there must have been some
way to exclude OpenGL in the build.

I don't think anyone tested that lately but this would
only produce a command line version. I'm not sure that
is what's asked here.
It would be nice to have this fully supported, but I
suspect it's not high up on the priority list. But as
we talk Open Source, that could change any time :-).

I keep my eye out for it, but have not come across any such
boards with full OpenGL (non-ES) yet. Can' say I've see every
release tho. It always seems to be SoC lacks support.

True, but that's not a huge problem for OpenSCAD which
does not benefit much by hardware accelerated rendering
at this point. So software rendering via Mesa (or maybe
using that new open source VC4 driver?) should be fine.

ciao,
Torsten.

On 04.01.19 00:20, MichaelAtOz wrote: > My vague recollection when I looked at it some years ago, > was it could only Render, so there must have been some > way to exclude OpenGL in the build. I don't think anyone tested that lately but this would only produce a command line version. I'm not sure that is what's asked here. It would be nice to have this fully supported, but I suspect it's not high up on the priority list. But as we talk Open Source, that could change any time :-). > I keep my eye out for it, but have not come across any such > boards with full OpenGL (non-ES) yet. Can' say I've see every > release tho. It always seems to be SoC lacks support. True, but that's not a huge problem for OpenSCAD which does not benefit much by hardware accelerated rendering at this point. So software rendering via Mesa (or maybe using that new open source VC4 driver?) should be fine. ciao, Torsten.
R
Richard
Fri, Jan 4, 2019 12:17 AM

Get an older version of raspian, openscad was working fine on it, including GUI

Verstuurd vanaf mijn iPhone

Op 4 jan. 2019 om 00:43 heeft Torsten Paul Torsten.Paul@gmx.de het volgende geschreven:

On 04.01.19 00:20, MichaelAtOz wrote:
My vague recollection when I looked at it some years ago,
was it could only Render, so there must have been some
way to exclude OpenGL in the build.

I don't think anyone tested that lately but this would
only produce a command line version. I'm not sure that
is what's asked here.
It would be nice to have this fully supported, but I
suspect it's not high up on the priority list. But as
we talk Open Source, that could change any time :-).

I keep my eye out for it, but have not come across any such
boards with full OpenGL (non-ES) yet. Can' say I've see every
release tho. It always seems to be SoC lacks support.

True, but that's not a huge problem for OpenSCAD which
does not benefit much by hardware accelerated rendering
at this point. So software rendering via Mesa (or maybe
using that new open source VC4 driver?) should be fine.

ciao,
Torsten.


OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org

Get an older version of raspian, openscad was working fine on it, including GUI Verstuurd vanaf mijn iPhone > Op 4 jan. 2019 om 00:43 heeft Torsten Paul <Torsten.Paul@gmx.de> het volgende geschreven: > >> On 04.01.19 00:20, MichaelAtOz wrote: >> My vague recollection when I looked at it some years ago, >> was it could only Render, so there must have been some >> way to exclude OpenGL in the build. > > I don't think anyone tested that lately but this would > only produce a command line version. I'm not sure that > is what's asked here. > It would be nice to have this fully supported, but I > suspect it's not high up on the priority list. But as > we talk Open Source, that could change any time :-). > >> I keep my eye out for it, but have not come across any such >> boards with full OpenGL (non-ES) yet. Can' say I've see every >> release tho. It always seems to be SoC lacks support. > > True, but that's not a huge problem for OpenSCAD which > does not benefit much by hardware accelerated rendering > at this point. So software rendering via Mesa (or maybe > using that new open source VC4 driver?) should be fine. > > ciao, > Torsten. > > > _______________________________________________ > OpenSCAD mailing list > Discuss@lists.openscad.org > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org