FYI, I added the notes Michael provided and Jens confirmed was working to the wiki page.

http://chirp.danplanet.com/projects/chirp/wiki/DevelopersWin32Environment

On windows are people generally using Python.org's packages or ActivePython?

Should there be a note to recommend one or the other?

On 11/11/2013 9:44 PM, Michael Pittaro wrote:

I followed the notes at http://chirp.danplanet.com/projects/chirp/wiki/DevelopersWin32Environment

In addition to that, I have the following notes for what I found as I went through the process:

• Follow site directions for setup
• install py2exe
• install cygwin
• add Cygwin zip/unzip
• install NSIS
• run build/make_Win32_build.sh from top hg directory
• output in c:\cygwin (which is a little weird....)

Builds were done from the cygwin prompt.

mike _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers

On 12/1/2013 2:46 PM, Sander Pool wrote:

I prefer ActivePython because of the included package manager. Either version is fine though.

I had used ActivePython in the distant past. However, it looks to me like pyserial was the only one of the chirp dependencies that was available through pypm, the active state package manager.

On 12/1/2013 4:58 PM, Sander Pool wrote:

What I meant was that I don't have a hard preference. Clearly if only one version works with CHIRP then that's the one that should be recommended :-)

I probably should have stated explicitly in my message that ActivePython seems to work fine. I downloaded it, tried to use their package manager to install all of the necessary dependencies, but only succeeded in installing pyserial.

Fortunately, the links that someone already been provided such as the PyGTK Win32 all-in-one installer, take care of installing both the python specific wrappers as well as the necessary binaries for the underlying libraries.

In the not so distant past I struggled to get various packages installed on Windows with the non-AS version. That quickly turned into a rabbit hole of package managers and dependencies that never converged. The AS version takes care of some of that.

Agreed, and that's why I tried ActivePython first. I was a bit disappointed that ActivePython's PyPm which is claimed to handle all that didn't at least have PyWin32 and PyGtk.

At some point, possibly on another system, I'll try it with just Python.org's python build, and see what is available with easy-install.

On 12/1/2013 2:50 PM, Jim Unroe wrote:

"If you are on 64-bit Windows, be sure to either download the 32 or 64-bit variants of each of the above."

I believe that this statement is incorrect. I am using Windows 7 64-bit, and if I remember correctly, I had to uninstall the 64-bit variants and switch to the 32-bit variants to get everything to work.

That was old and has now been updated.

The part I had added was on setting up the environment to build .exe's. I had added the suggestion that 32-bit was probably what you want if your building .exe's.

while I was there, I also did some more editing to flesh that page out.

Hope this helps.