[chirp_devel] MacOSX - KK7DS Python Runtime Package
First off, my bad for not keeping up with a project I find valuable enough to actually contribute cash and effort to. I should have been following along over the last 10 months, but I fell away and haven't checked back in. I got a new rig for the car (Yaesu FT-7900) and needed to program it, so downloaded everything to my new Mac Book Air 11", and nothing. Actually from the console I was getting the following message, but would get nothing while clicking on it from the Mac Finder.
LSOpenURLsWithRole() failed with error -10810 for the file /Users/jay/Downloads/chirp-daily-20120714.app.
Not very descriptive, which led me to wondering what was going on. I keep Mac Ports up-to-date on my machine, all of the needed Python libraries were installed, but no go. I find my way to the startup script at:
/Users/jay/Downloads/chirp-daily-20120714.app/Contents/MacOS
And I see that all of the work that was put into allowing folks who already have Python2.7 and the needed libraries installed has been removed. That was there so we didn't have to download and pollute our systems with the KK7DS Python runtime. This was the pertinent parts of the Feb 15, 2012 script:
41 if [ ! -x /opt/kk7ds/bin/python2.5 ]; then 42 ERRMSG=$ERRMSG"The KK7DS Python runtime for OSX is not installed\n" 43 # check macports Python 44 if [ ! -x /opt/local/bin/python2.7 ]; then 45 ERRMSG=$ERRMSG"The Macport Python2.7 runtime for OSX is not installed\n"; 46 else 47 ERRMSG=" "; 48 NORUNTIME=0; 49 RUNPYTHON="/opt/local/bin/python2.7"; 50 51 if [ -z "`port -q installed py27-gtk`" ]; then 52 ERRMSG=$ERRMSG"The Macport py27-gtk module for OSX is not installed\n"; 53 let "NORUNTIME += 1"; 54 fi 55 if [ -z "`port -q installed py27-libxml2`" ]; then 56 ERRMSG=$ERRMSG"The Macport py27-libxml2 module for OSX is not installed\n"; 57 let "NORUNTIME += 1"; 58 fi 59 if [ -z "`port -q installed py27-serial`" ]; then 60 ERRMSG=$ERRMSG"The Macport py27-serial module for OSX is not installed\n"; 61 let "NORUNTIME += 1"; 62 fi 63 fi
Is there any particular reason these (or something similar) parts of the startup script aren't in there any longer? Are there more libraries in KK7DS's runtime package these days that is going to prevent the current Daily Build from working correctly? I've temporarily hacked the script since I know I have everything needed (at least from prior versions) installed and things SEEM to be working, but I'm at work and no cable/radio to test with at the moment to test with, and frankly I'd prefer to know I'm not missing something vital before using it anyway.
Again, apologies for not keeping up, and I didn't have a good way to search the mailing list archive for more information. I did find the posts back in August of last year with Gerrit, but not much else along the lines of changing the script.
Thanks in advance for taking the time to answer, and I'll try to keep up with things a bit better in the future. Apologies!
Jay, N2JCM
On Mon, Jul 16, 2012 at 12:41 PM, Jay Moran, N2JCM jay+CHIRP@tp.org wrote:
And I see that all of the work that was put into allowing folks who already have Python2.7 and the needed libraries installed has been removed. That was there so we didn't have to download and pollute our systems with the KK7DS Python runtime. This was the pertinent parts of the Feb 15, 2012 script:
Here is the commit that removed the runtime check: http://chirp.danplanet.com/projects/chirp/repository/diff/build/chirp.app/Co...
It looks like the functionality you seek was abandoned when the script was rewritten, probably because it is a rare use case. I suspect a patch to add it back in would be accepted as long as it doesn't break anything. It would need to have a clear message for the normal users: "KK7DS Runtime not found. Do you want to install it, or use your own?".
Also, the OS X app is pending a rewrite that will get rid of the runtime altogether, but I believe Dan is waiting on a Mac-savvy developer to write it. Any patch you submit for the existing script might not be around very long (probably still worthwhile--I don't hold my breath for promised rewrites!).
Tom KD7LXL
On Mon, Jul 16, 2012 at 2:58 PM, Tom Hayward esarfl@gmail.com wrote:
It looks like the functionality you seek was abandoned when the script was rewritten, probably because it is a rare use case. I suspect a patch to add it back in would be accepted as long as it doesn't break anything. It would need to have a clear message for the normal users: "KK7DS Runtime not found. Do you want to install it, or use your own?".
Also, the OS X app is pending a rewrite that will get rid of the runtime altogether, but I believe Dan is waiting on a Mac-savvy developer to write it. Any patch you submit for the existing script might not be around very long (probably still worthwhile--I don't hold my breath for promised rewrites!).
Thanks Tom. Looks like it was in preparation for the removal of X11... though the app is still running in X11 right now. I can just continue hacking it I guess. Interestingly, with my hack, it opens fine with "open chirp.app" but doesn't work double-clicking in the Mac Finder. Interesting.
I'll leave it alone for now and see how the future comes along. :)
Jay -- Jay Moran, N2JCM http://www.qrz.com/db/N2JCM
Thanks Tom. Looks like it was in preparation for the removal of X11... though the app is still running in X11 right now. I can just continue hacking it I guess. Interestingly, with my hack, it opens fine with "open chirp.app" but doesn't work double-clicking in the Mac Finder. Interesting.
You're running an old runtime then. The current version of the app and runtime run GTK on native quartz.
On Mon, Jul 16, 2012 at 5:26 PM, Dan Smith dsmith@danplanet.com wrote:
You're running an old runtime then. The current version of the app and runtime run GTK on native quartz.
Having someone else's Python installed, scares me (perhaps irrationally) and worries me that they're going to screw up the environment I rely upon for everything else I do, including my job. With that in mind, I use MacPorts Python (as a lot of folks do) and the three MacPorts py27-* libraries that are needed for Chirp.
So, your statement led me on an interesting night of converting GTK to run natively on quartz. I'm heading down that path now... thought it would be easier than it is seeming. But, sounds like that is probably the problem. :)
Jay
Having someone else's Python installed, scares me (perhaps irrationally) and worries me that they're going to screw up the environment I rely upon for everything else I do, including my job. With that in mind, I use MacPorts Python (as a lot of folks do) and the three MacPorts py27-* libraries that are needed for Chirp.
My runtime is just a snapshot of a MacPorts install. You'd only use it for running CHIRP, nothing else.
So, your statement led me on an interesting night of converting GTK to run natively on quartz. I'm heading down that path now... thought it would be easier than it is seeming. But, sounds like that is probably the problem. :)
Yep, well, that's the price (pain) of wanting to do it yourself, but you should be able to make it work. It took me days to get it right, but I'm not a MacOS/MacPorts guy.
Note that if you use the GTK in your MacPorts for other things, there's a good chance converting it to Quartz will break those. You can either install a parallel version for Quartz support, or, you know, just install mine :)
On Mon, Jul 16, 2012 at 10:42 PM, Dan Smith dsmith@danplanet.com wrote:
Note that if you use the GTK in your MacPorts for other things, there's a good chance converting it to Quartz will break those. You can either install a parallel version for Quartz support, or, you know, just install mine :)
Fine! I give. :) Reverted my MacPorts install... installing R10 of yours. :)
Jay, N2JCM
On Mon, Jul 16, 2012 at 11:04 PM, Jay Moran, N2JCM jay+CHIRP@tp.org wrote:
Fine! I give. :) Reverted my MacPorts install... installing R10 of yours. :)
To note, all works as designed. :)
Thanks Dan again, for making such a great program. Deserves another donation. There ya go. :)
Jay, N2JCM
To note, all works as designed. :)
Cool. The Quartz support allows for menubar integration and stuff, which I think makes the Mac types happier.
Thanks Dan again, for making such a great program. Deserves another donation. There ya go. :)
Heh, thanks for that :)
participants (3)
-
Dan Smith -
Jay Moran, N2JCM -
Tom Hayward