Raspberry Pi build of Daily Snap Shots

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

Raspberry Pi build of Daily Snap Shots

James Key
Has anyone successfully built one on the daily snapshots on Raspberry Pi. I'm currently running 'Jessie' and attempted to build 4.0.0a4.dev3185. I was unable to compile the DEBUG version due to what appeared to be a memory issue, so I compiled the RELEASE version. It compiles but when it attempts to link it runs out of memory. The Pi has 256MB of memory so I thought I'd try a virtual QEMU install. It's hard coded with the same memory cap in the kernel. 
Are there some switches I'm missing? or is it possible to use another ARM Debian kernel to compile it on QEMU? 

--
You received this message because you are subscribed to the Google Groups "wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Raspberry Pi build of Daily Snap Shots

Tim Roberts
James Key wrote:
> Has anyone successfully built one on the daily snapshots on Raspberry
> Pi. I'm currently running 'Jessie' and attempted to build
> 4.0.0a4.dev3185. I was unable to compile the DEBUG version due to what
> appeared to be a memory issue, so I compiled the RELEASE version. It
> compiles but when it attempts to link it runs out of memory. The Pi
> has 256MB of memory so I thought I'd try a virtual QEMU install. It's
> hard coded with the same memory cap in the kernel.

So, the question is not "has anyone RUN wxPython on a Pi", the question
is "has anyone BUILT wxPython on a Pi", right?

I'm not terribly surprised that 256MB is not enough to run the
development tools.  You may need to cross-compile this from an x86
system, using something like buildroot.

--
Tim Roberts, [hidden email]
Providenza & Boekelheide, Inc.

--
You received this message because you are subscribed to the Google Groups "wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Raspberry Pi build of Daily Snap Shots

James Key
In reply to this post by James Key
Oh yes, it's about the build process, I'm trying to develop an app for the Pi and decided on wxPython. I'm not familiar with build root, but I will do some investigation.

On Sunday, July 9, 2017 at 5:30:41 PM UTC-4, James Key wrote:
Has anyone successfully built one on the daily snapshots on Raspberry Pi. I'm currently running 'Jessie' and attempted to build 4.0.0a4.dev3185. I was unable to compile the DEBUG version due to what appeared to be a memory issue, so I compiled the RELEASE version. It compiles but when it attempts to link it runs out of memory. The Pi has 256MB of memory so I thought I'd try a virtual QEMU install. It's hard coded with the same memory cap in the kernel. 
Are there some switches I'm missing? or is it possible to use another ARM Debian kernel to compile it on QEMU? 

--
You received this message because you are subscribed to the Google Groups "wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Raspberry Pi build of Daily Snap Shots

mikejonson7501
This post has NOT been accepted by the mailing list yet.
In reply to this post by James Key
hi, I have the same problem, and will be very grateful if someone help  me to solve it too
[url=https://huge-it.com/google-map/]Google Map[/url] - [url=https://wordpress.org/plugins/slider-image/]WordPress Slider[/url]
Reply | Threaded
Open this post in threaded view
|

Re: Raspberry Pi build of Daily Snap Shots

nepix32
In reply to this post by Tim Roberts


On Monday, July 10, 2017 at 6:12:46 PM UTC+2, Tim Roberts wrote:
I'm not terribly surprised that 256MB is not enough to run the

Maybe it would be cheaper (spending less hours) for the original poster to spend 40 Bucks on a raspberry Pi 3 with 1 GB RAM, compile there and transfer the binary to the smaller machine?

--
You received this message because you are subscribed to the Google Groups "wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Raspberry Pi build of Daily Snap Shots

James Key
In reply to this post by James Key
Not a bad idea!!! Sometimes the obvious escapes me!

On Sunday, July 9, 2017 at 5:30:41 PM UTC-4, James Key wrote:
Has anyone successfully built one on the daily snapshots on Raspberry Pi. I'm currently running 'Jessie' and attempted to build 4.0.0a4.dev3185. I was unable to compile the DEBUG version due to what appeared to be a memory issue, so I compiled the RELEASE version. It compiles but when it attempts to link it runs out of memory. The Pi has 256MB of memory so I thought I'd try a virtual QEMU install. It's hard coded with the same memory cap in the kernel. 
Are there some switches I'm missing? or is it possible to use another ARM Debian kernel to compile it on QEMU? 

--
You received this message because you are subscribed to the Google Groups "wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Raspberry Pi build of Daily Snap Shots

James Key
In reply to this post by James Key
The new Pi has arrived and wxWidgets will build on it both shared and monolithic, but when I attempt to build wxPython Phoenix 4.0.0b1. I keep getting this error:

Running command: dox
bash ./regen.sh xml
Finished command: dox (1m58.67s)
Running command: etg
"/usr/bin/python3.4" etg/image.py --sip --nodoc
Unable to find xml file for ITEM: wxTIFFHandler
Tried: /home/pi/Phoenix-wxPython-4.0.0b1/ext/wxWidgets/docs/doxygen/out/xml/classwx_t_i_f_f_handler.xml
       /home/pi/Phoenix-wxPython-4.0.0b1/ext/wxWidgets/docs/doxygen/out/xml/structwx_t_i_f_f_handler.xml
       /home/pi/Phoenix-wxPython-4.0.0b1/ext/wxWidgets/docs/doxygen/out/xml/wxTIFFHandler
Traceback (most recent call last):
  File "etg/image.py", line 681, in <module>
    run()
  File "etg/image.py", line 43, in run
    etgtools.parseDoxyXML(module, ITEMS)
  File "/home/pi/Phoenix-wxPython-4.0.0b1/etgtools/__init__.py", line 82, in parseDoxyXML
    raise DoxyXMLError(msg)
etgtools.DoxyXMLError: Unable to find xml file for ITEM: wxTIFFHandler
Command '"/usr/bin/python3.4" etg/image.py --sip --nodoc' failed with exit code 1.
Finished command: etg (0.814s)

I have installed and build sip and doxygen for the arm on the Pi.
Any thoughts?

On Sunday, July 9, 2017 at 5:30:41 PM UTC-4, James Key wrote:
Has anyone successfully built one on the daily snapshots on Raspberry Pi. I'm currently running 'Jessie' and attempted to build 4.0.0a4.dev3185. I was unable to compile the DEBUG version due to what appeared to be a memory issue, so I compiled the RELEASE version. It compiles but when it attempts to link it runs out of memory. The Pi has 256MB of memory so I thought I'd try a virtual QEMU install. It's hard coded with the same memory cap in the kernel. 
Are there some switches I'm missing? or is it possible to use another ARM Debian kernel to compile it on QEMU? 

--
You received this message because you are subscribed to the Google Groups "wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Raspberry Pi build of Daily Snap Shots

Robin Dunn
James Key wrote:

> The new Pi has arrived and wxWidgets will build on it both shared and
> monolithic, but when I attempt to build wxPython Phoenix 4.0.0b1. I
> keep getting this error:
>
> Running command: dox
> bash ./regen.sh xml
> Finished command: dox (1m58.67s)
> Running command: etg
> "/usr/bin/python3.4" etg/image.py --sip --nodoc
> Unable to find xml file for ITEM: wxTIFFHandler
> Tried:
> /home/pi/Phoenix-wxPython-4.0.0b1/ext/wxWidgets/docs/doxygen/out/xml/classwx_t_i_f_f_handler.xml
>      
>  /home/pi/Phoenix-wxPython-4.0.0b1/ext/wxWidgets/docs/doxygen/out/xml/structwx_t_i_f_f_handler.xml
>      
>  /home/pi/Phoenix-wxPython-4.0.0b1/ext/wxWidgets/docs/doxygen/out/xml/wxTIFFHandler
> Traceback (most recent call last):
>   File "etg/image.py", line 681, in <module>
>     run()
>   File "etg/image.py", line 43, in run
>     etgtools.parseDoxyXML(module, ITEMS)
>   File "/home/pi/Phoenix-wxPython-4.0.0b1/etgtools/__init__.py", line
> 82, in parseDoxyXML
>     raise DoxyXMLError(msg)
> etgtools.DoxyXMLError: Unable to find xml file for ITEM: wxTIFFHandler
> Command '"/usr/bin/python3.4" etg/image.py --sip --nodoc' failed with
> exit code 1.
> Finished command: etg (0.814s)
>
> I have installed and build sip and doxygen for the arm on the Pi.
> Any thoughts?

Is it doxygen version 1.8.8?  If not, then they may have changed how the
xml files are named or something. Do a grep in
ext/wxWidgets/docs/doxygen/out/xml for wxTIFFHandler to see if the
class' definition is in a different file.

On the other hand, if you are using the source tarball then you do not
need to do the dox, etg, or sip commands. The generated files should
already be present.  Just start with the build command followed by
whatever packaging or installation commands you want to use.


--
Robin Dunn
Software Craftsman
http://wxPython.org

--
You received this message because you are subscribed to the Google Groups "wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Raspberry Pi build of Daily Snap Shots

James Key
SUCCESS!!!

I have attached a Markdown document for those of you who wish to try this.

On Thursday, August 3, 2017 at 5:11:12 PM UTC-4, Robin Dunn wrote:
James Key wrote:

> The new Pi has arrived and wxWidgets will build on it both shared and
> monolithic, but when I attempt to build wxPython Phoenix 4.0.0b1. I
> keep getting this error:
>
> Running command: dox
> bash ./regen.sh xml
> Finished command: dox (1m58.67s)
> Running command: etg
> "/usr/bin/python3.4" etg/image.py --sip --nodoc
> Unable to find xml file for ITEM: wxTIFFHandler
> Tried:
> /home/pi/Phoenix-wxPython-4.0.0b1/ext/wxWidgets/docs/doxygen/out/xml/classwx_t_i_f_f_handler.xml
>      
>  /home/pi/Phoenix-wxPython-4.0.0b1/ext/wxWidgets/docs/doxygen/out/xml/structwx_t_i_f_f_handler.xml
>      
>  /home/pi/Phoenix-wxPython-4.0.0b1/ext/wxWidgets/docs/doxygen/out/xml/wxTIFFHandler
> Traceback (most recent call last):
>   File "etg/image.py", line 681, in <module>
>     run()
>   File "etg/image.py", line 43, in run
>     etgtools.parseDoxyXML(module, ITEMS)
>   File "/home/pi/Phoenix-wxPython-4.0.0b1/etgtools/__init__.py", line
> 82, in parseDoxyXML
>     raise DoxyXMLError(msg)
> etgtools.DoxyXMLError: Unable to find xml file for ITEM: wxTIFFHandler
> Command '"/usr/bin/python3.4" etg/image.py --sip --nodoc' failed with
> exit code 1.
> Finished command: etg (0.814s)
>
> I have installed and build sip and doxygen for the arm on the Pi.
> Any thoughts?

Is it doxygen version 1.8.8?  If not, then they may have changed how the
xml files are named or something. Do a grep in
ext/wxWidgets/docs/doxygen/out/xml for wxTIFFHandler to see if the
class' definition is in a different file.

On the other hand, if you are using the source tarball then you do not
need to do the dox, etg, or sip commands. The generated files should
already be present.  Just start with the build command followed by
whatever packaging or installation commands you want to use.


--
Robin Dunn
Software Craftsman
<a href="http://wxPython.org" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2FwxPython.org\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHG9kM-NEpJfIvl_lWJvA23SuLjOA&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2FwxPython.org\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHG9kM-NEpJfIvl_lWJvA23SuLjOA&#39;;return true;">http://wxPython.org

--
You received this message because you are subscribed to the Google Groups "wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

Raspberry_Pi_wxPython.md (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Raspberry Pi build of Daily Snap Shots

Claudia Frank
Thank you with this guide we were able to compile wxpython on the new rock64 sbc.
One additional step we needed to do was to replace the config.sub and config.guess 
within ext/widgets with a more recent version.

First test:

rock64@therock:~$ python -c "import wx; import platform; print 'wx:{}\narch:{}'.format(wx.version(),platform.machine())"
wx:4.0.0b1 gtk2 (phoenix)
arch:aarch64

Cheers
Claudia

--
You received this message because you are subscribed to the Google Groups "wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Raspberry Pi build of Daily Snap Shots

James Key
I'm very happy that it help you. It's also available on the wxPython wiki for future reference.

On Wednesday, September 6, 2017 at 12:32:09 PM UTC-4, Claudia Frank wrote:
Thank you with this guide we were able to compile wxpython on the new rock64 sbc.
One additional step we needed to do was to replace the config.sub and config.guess 
within ext/widgets with a more recent version.

First test:

rock64@therock:~$ python -c "import wx; import platform; print 'wx:{}\narch:{}'.format(wx.version(),platform.machine())"
wx:4.0.0b1 gtk2 (phoenix)
arch:aarch64

Cheers
Claudia

--
You received this message because you are subscribed to the Google Groups "wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.