[chirp_devel] Development env?

[Dan Smith]

> 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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: OpenPGP digital signature
Url : http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20121227/639c7250/attachment-0001.bin