[chirp_users] MacOS Version of Chirp
ALCON:
I have been a Unix System Administrator for many years, and in fact would be quite capable of testing, compiling, or generating object code on my Intel Mac for the benefit of the community.
My understanding of the current Apple Development Kit is that you can generate Intel based code on the PPC, whether it is "Universal" code for any target processor (PPC or Intel), or Intel specific (and optimized) code that is intended for only the Intel chip. Now I understand this is mostly written in Python, anyway, but, just some food for thought here.
I saw where someone was speaking of a ".19" version (beta?) but given the open source nature of the software, was surprised to not see it on the download site.
One thing I had been working on was a decoder for reading the code plug from an "ICF" file. Now that I see this software is here, I would be willing to try to integrate that into Chirp such that we could at least read and for sure try to shoot for writing "ICF" files compatible with the ICOM software for Windows.
I have been a Unix System Administrator for many years, and in factwould be quite capable of testing, compiling, or generating object code on my Intel Mac for the benefit of the community.
That would be great. I spent some time working up instructions for how to get a build environment built on MacOS for D-RATS. If you follow those instructions (aside from the bit about building D-RATS) you should be able to at least run it on your system. From there, I'll need to make some tweaks to the build system to get it to create a .app package. The instructions are here:
http://www.d-rats.com/wiki/MacOSXBuildNotes
My understanding of the current Apple Development Kit is that you cangenerate Intel based code on the PPC, whether it is "Universal" code for any target processor (PPC or Intel), or Intel specific (and optimized) code that is intended for only the Intel chip. Now I understand this is mostly written in Python, anyway, but, just some food for thought here.
That's true, Xcode can produce universal binaries, but that's only half the story. All of the code you compile must be endian safe in order to run on both platforms. Not all of the packages needed are safe and thus it's necessary to build one for each.
CHIRP and D-RATS are written in Python, but require a substantial set of additional libraries to run (GTK being one you have already identified). Further, the Python included with MacOS is quite old, so a new one is built along the way.
I saw where someone was speaking of a ".19" version (beta?) but giventhe open source nature of the software, was surprised to not see it on the download site.
You can get the latest beta that I'm working on here:
http://chirp.danplanet.com/download/beta
I have been extremely busy lately and thus haven't done much work on CHIRP, but I need to get back into it.
One thing I had been working on was a decoder for reading the code plug from an "ICF" file. Now that I see this software is here, I would be willing to try to integrate that into Chirp such that we could at least read and for sure try to shoot for writing "ICF" files compatible with the ICOM software for Windows.
CHIRP can read ICF files generated from the mobile radios already by actually turning them directly into .img files. Exporting them is a little harder because there is some extra gorp at the end of the memory image that I don't know about yet. Further, the ICF files for the handhelds are a different beast altogether.
If you get the environment built and CHIRP running, let me know and we'll move forward with the .app build changes.
Thanks!
On Feb 25, 2009, at 20:16, Dan Smith wrote:
If you get the environment built and CHIRP running, let me know and we'll move forward with the .app build changes.
well, I built it, and it launches, but I mostly just get various errors trying to get it to pull data down from my ic-92ad.
should I be launching it by running "python chirpw" that was the closest I found by looking in the chirp.desktop to figure out what that was launching.
I've attached the output from launch, setting ic9x to "B", and trying to download from radio. then I selected "new" and again tried to download from radio.
I was in band B and on a DV memory. I checked the GPS settings and they were off.
I didn't find any place to tell it what serial port or other such info I might be using, that might be why it's not working, as it's likely got no idea where my radio's plugged in. I'm assuming that's user error on my part.
FWIW, I also just checked, and at MacOS 10.5.6, the built-in python is 2.5.1
-debbie, n9dn
should I be launching it by running "python chirpw" that was the closest I found by looking in the chirp.desktop to figure out what that was launching.
Yep, that's a fine way to do it.
I've attached the output from launch, setting ic9x to "B", and trying to download from radio. then I selected "new" and again tried to download from radio.
Okay, you might be missing something there.
I didn't find any place to tell it what serial port or other such info I might be using, that might be why it's not working, as it's likely got no idea where my radio's plugged in. I'm assuming that's user error on my part.
When you go to Radio->Open ic9x->Band B (for example), it will bring up the settings box, where the model and file are greyed out. The serial port box is likely empty, so you need to put the path to your device in there. Whatever you use for D-RATS should do the trick there as well. Then you can hit okay and it should load the radio.
I've never actually run CHIRP on the Mac, but several other people have, so it sounds like it should be okay.
participants (3)
-
Dan Smith -
Debbie Fligor -
IT2 Stuart Blake Tener, USNR