[chirp_devel] Development env?

[Drew Vonada-Smith]

PyGTK all-in-one appears to be 32 bit only, so I am stumped other than
setting up a separate 32 bit machine just for CHIRP dev.  Your instructions
say 64 bit users can just download all 64 bit or all 32 bit parts.  Is that
confirmed?  32 doesn't seem to work under Win7/64 and 64 bit parts are
apparently not all available.

-----Original Message-----
From: Drew Vonada-Smith [mailto:drew at whisperingwoods.org] 
Sent: December 27, 2012 10:56
To: 'Dan Smith'; 'chirp_devel at intrepid.danplanet.com'
Subject: RE: [chirp_devel] Development env?

Tons of hits on that message, but not knowing anything about python, none
are at all clear to me.  Certainly though  it is related to 32 vs 64 bits.
Should I be running all 64 bit apps on my Win 64?  I thought the app env had
to be Win32.  Please clarify what I really need...

By the way, I am not getting any of these messages except direct.  How do I
turn off the "daily digest" feature?

-----Original Message-----
From: Dan Smith [mailto:dsmith at danplanet.com]
Sent: December 27, 2012 10:34
To: chirp_devel at intrepid.danplanet.com
Cc: Drew Vonada-Smith
Subject: Re: [chirp_devel] Development env?

> Yes, win is 64 bit.  I assumed this had to be Win32 tools, so all 
> downloaded  items were 32 bit except mercurial, which i didnt think 
> should matter

Right, mercurial can be either.

It looks like pygtk is 32-bit only on windows, so yes, everything will need
to be 32-bit.

> Thanks for the patience.  I think there is more to the win setup than 
> you are aware of running nix; any win users that can clarify?

Well, I'm the only one I know of with a working windows installation
(although I'm sure there are others), and I generate all the builds.
However, it's done on a 32-bit install, so I'm sure there are some
additional gotchas (although there should not be any more packages
required).

The import error you're seeing is a failure to load a DLL that does exist on
your system, so I feel it's pretty obviously a 32-vs-64 problem somewhere.
However, the error you're getting is not coming from chirp, so the plentiful
google results from adding "python win32" to the error message should help
you along.

Good luck!

--
Dan Smith
www.danplanet.com
KK7DS