[Coco] Drivewire on an original Raspberry Pi

Ron Klein ron at kdomain.org
Wed Feb 2 12:59:09 EST 2022


That's a cool story.  :)


On Wed, Feb 2, 2022 at 7:03 AM Rocky Hill via Coco <coco at maltedmedia.com>
wrote:

>  That is funny and it reminds of this story.
> "One day in 1939, George Bernard Dantzig, a doctoral candidate at the
> University of California, Berkeley, arrived late for a graduate-level
> statistics class and found two problems written on the board. Not knowing
> they were examples of “unsolved” statistics problems, he mistook them for
> part of a homework assignment, jotted them down, and solved them. (The
> equations Dantzig tackled are more accurately described not as unsolvable
> problems, but rather as unproven statistical theorems for which he worked
> out proofs.)"
>
>
>     On Wednesday, February 2, 2022, 02:17:37 AM EST, Walter ZAMBOTTI <
> zambotti at iinet.net.au> wrote:
>
>  This will make you all laugh.
>
> The only reason I persisted in getting it going on ARM Linux (Odroid)
> was because when I read the post DW4 was working on the CoCo-PI I
> assumed the GUI was also working and I thought to myself if someone can
> do it on the PI then I can do it on the Odroid.
>
> This is not the first time I have tried.
>
> Funny how a misconception can be the impetus for success!
>
> Walter
>
> On 2/2/22 08:45, Ron Klein wrote:
> > Perhaps the configuration I have set up on the CoCo-Pi distribution isn't
> > what folks here are looking for, but I have pyDriveWire and DriveWire 4
> > installed - though only one of them is active at a time.
> >
> > For DriveWire, I make sure to use Oracle 1.8.0:
> >
> > pi at raspberrypi:~ $ java -version
> > java version "1.8.0_202"
> > Java(TM) SE Runtime Environment (build 1.8.0_202-b08)
> > Java HotSpot(TM) Client VM (build 25.202-b08, mixed mode)
> >
> > This will allow DriveWire 4 to run, but without the GUI (X-Windows / Java
> > client on the Raspberry Pi itself).  Not an issue for my needs as I
> mainly
> > control the DriveWire server through scripting.  If I need to access the
> > GUI, I simply do it from my main Linux (or Windows) workstation since I
> > also have the DriveWire software installed on both of those computers.
> You
> > simply use the option to connect to another (remote) server and it just
> > works.  This option also allows me to run a Raspberry Pi "headless" yet
> > easily manage it.
> >
> > pyDriveWire includes an easy to use web interface which is also easy to
> > access remotely.
> >
> > I give Walter kudos for going through all the trouble to get the actual
> GUI
> > working on the Raspberry Pi, but perhaps the set up I use may work for
> > others as an alternate method.
> >
> > -Ron
> >
> >
> > On Tue, Feb 1, 2022 at 2:54 PM Rocky Hill via Coco <coco at maltedmedia.com
> >
> > wrote:
> >
> >>  Very nice, can you share a link to the source? Were you able to compile
> >> it?
> >>      On Tuesday, February 1, 2022, 08:22:03 AM EST, Walter Zambotti <
> >> zambotti at iinet.net.au> wrote:
> >>
> >>  I managed to locate the correct 4.2.3.4 eclipse-swt java source which
> >> came with the C source for the system libraries (libswt-*.so).
> >>
> >> I modified the build script to recognize ARM64 (aarch64) and built the
> >> required .so libraries.
> >>
> >> And ........
> >>
> >> they work.
> >>
> >> I now have DriveWire4 working on both Ubuntu 20.04 (or later) on both
> >> AMD64 (X86) and ARM64.
> >>
> >> Regards
> >>
> >> Walter
> >>
> >> On 31/1/22 17:02, Walter Zambotti wrote:
> >>> Bill
> >>>
> >>> I thought I wrote a long explanation and sent it earlier today
> >>> regarding how DW4UI.jar works internally with the libs.  Maybe I sent
> >>> the message to you rather than the list.
> >>>
> >>> So I will make this a short reply.
> >>>
> >>> Basically DW4UI.jar comes bundled with the SWT GTKjava jar library
> >>> inside of it.  When it is run for the first time it installs the
> >>> relevant swtgtk.so to the ~/.swt/lib/linux/XarchitectureX directory.
> >>>
> >>> DW4 comes with SWTGTK libs for OSX, Win32, Win64, Linux32, Linux64 and
> >>> LinuxArm.
> >>>
> >>> However the LinuxArm library appears incomplete and doesn't specify if
> >>> it is 32 or 64 bit.
> >>>
> >>> It specifically requires version 4234 of libswt-gtk-4234.so,
> >>> libswt-pi-gtk-4234.so, libswt-awt-gtk-4234.so,
> libswt-cairo-gtk-4234.so.
> >>>
> >>> If it doesn't find these it automatically installs them to the above
> >>> mentioned directory.  On my ARM64 Ubuntu system it was installing the
> >>> IntelLinux64 version. Probably because several years ago there was
> >>> only one ARM architecture on Linux. Now there are two and it probably
> >>> doesn't recognize the newer and different architecture names.
> >>>
> >>> I haven't tried installing it on a PI which is usually 32 bit!
> >>>
> >>> Regards
> >>>
> >>> Walter
> >>>
> >>> On 31/1/22 03:35, Bill Gunshannon wrote:
> >>>> Anybody have any success doing this?  I have tried DriveWrie4 which
> >>>> dies because of a lack of swt-gtk Libs. (may try doing it UI-less
> >>>> but that is less than desirable)  And I can't even begin to understand
> >>>> how one gets pyDrivewire to run. (Never used Python before.  Not
> >>>> impressed so far!!)
> >>>>
> >>>> Any kind of useful tutorials for this.  Nothing I have found on the
> >>>> web so far has been any help at all.
> >>>>
> >>>> bill
> >>>>
> >> --
> >> Coco mailing list
> >> Coco at maltedmedia.com
> >> https://pairlist5.pair.net/mailman/listinfo/coco
> >>
> >>
> >> --
> >> Coco mailing list
> >> Coco at maltedmedia.com
> >> https://pairlist5.pair.net/mailman/listinfo/coco
> >>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>


More information about the Coco mailing list