[chirp_devel] Development env?
All installed. OK up to:
python chirpw
Python: can't open file 'chirpw': [Errno 2] No such file or directory
I'm not seeing where chirp source was installed in the procedure.
python chirpw
Python: can’t open file ‘chirpw’: [Errno 2] No such file or directory
I’m not seeing where chirp source was installed in the procedure.
In the "Clone the repository" step, you should get a new chirp.hg directory. Go into that and then chirpw should be inside.
Drew, here is my response from the other day. I'm copying you directly to make sure you get it, but please be sure to reply on the list.
On 12/24/2012 01:41 PM, Dan Smith wrote:
python chirpw
Python: can’t open file ‘chirpw’: [Errno 2] No such file or directory
I’m not seeing where chirp source was installed in the procedure.
In the "Clone the repository" step, you should get a new chirp.hg directory. Go into that and then chirpw should be inside.
chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
Where do I find the chirp.hg directory? I don't see one.
-----Original Message----- From: Dan Smith [mailto:dsmith@danplanet.com] Sent: December 27, 2012 09:34 To: chirp_devel@intrepid.danplanet.com Cc: drew@whisperingwoods.org Subject: Re: [chirp_devel] Development env?
Drew, here is my response from the other day. I'm copying you directly to make sure you get it, but please be sure to reply on the list.
On 12/24/2012 01:41 PM, Dan Smith wrote:
python chirpw
Python: can't open file 'chirpw': [Errno 2] No such file or directory
I'm not seeing where chirp source was installed in the procedure.
In the "Clone the repository" step, you should get a new chirp.hg directory. Go into that and then chirpw should be inside.
chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
-- Dan Smith www.danplanet.com KK7DS
Where do I find the chirp.hg directory? I don't see one.
You're following this, right?
http://chirp.danplanet.com/projects/chirp/wiki/DevelopersWin32Environment
In the "Clone the repository" step, you run "hg clone ...". That grabs a copy of the repository locally into "chirp.hg". After you run that command, you would type "cd chirp.hg" and chirpw is inside.
Yes, I am following it, but running the python command line you note does not find the source.
-----Original Message----- From: Dan Smith [mailto:dsmith@danplanet.com] Sent: December 27, 2012 09:58 To: chirp_devel@intrepid.danplanet.com Cc: Drew Vonada-Smith Subject: Re: [chirp_devel] Development env?
Where do I find the chirp.hg directory? I don't see one.
You're following this, right?
http://chirp.danplanet.com/projects/chirp/wiki/DevelopersWin32Environment
In the "Clone the repository" step, you run "hg clone ...". That grabs a copy of the repository locally into "chirp.hg". After you run that command, you would type "cd chirp.hg" and chirpw is inside.
-- Dan Smith www.danplanet.com KK7DS
Found \chirp.hg in C:\Users\Drew. A rather odd spot, it is in my user profile! Where is supposed to go? My python env is at P:\Python.
-----Original Message----- From: Drew Vonada-Smith [mailto:drew@whisperingwoods.org] Sent: December 27, 2012 09:50 To: 'chirp_devel@intrepid.danplanet.com' Subject: RE: [chirp_devel] Development env?
Where do I find the chirp.hg directory? I don't see one.
-----Original Message----- From: Dan Smith [mailto:dsmith@danplanet.com] Sent: December 27, 2012 09:34 To: chirp_devel@intrepid.danplanet.com Cc: drew@whisperingwoods.org Subject: Re: [chirp_devel] Development env?
Drew, here is my response from the other day. I'm copying you directly to make sure you get it, but please be sure to reply on the list.
On 12/24/2012 01:41 PM, Dan Smith wrote:
python chirpw
Python: can't open file 'chirpw': [Errno 2] No such file or directory
I'm not seeing where chirp source was installed in the procedure.
In the "Clone the repository" step, you should get a new chirp.hg directory. Go into that and then chirpw should be inside.
chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
-- Dan Smith www.danplanet.com KK7DS
Found \chirp.hg in C:\Users\Drew. A rather odd spot, it is in my user profile! Where is supposed to go? My python env is at P:\Python.
It is wherever you where when you ran the "hg clone". It doesn't matter where it is, because it's your working directory for the code. I'm not a Windows user, so I have no idea where devs normally stage their stuff, but I'd guess in My Documents or something? Totally your call :)
I put it in my documents area now, but "python chirpw" does not find it. It must matter where it is placed for that line to work...
-----Original Message----- From: Dan Smith [mailto:dsmith@danplanet.com] Sent: December 27, 2012 10:05 To: chirp_devel@intrepid.danplanet.com Cc: Drew Vonada-Smith Subject: Re: [chirp_devel] Development env?
Found \chirp.hg in C:\Users\Drew. A rather odd spot, it is in my user profile! Where is supposed to go? My python env is at P:\Python.
It is wherever you where when you ran the "hg clone". It doesn't matter where it is, because it's your working directory for the code. I'm not a Windows user, so I have no idea where devs normally stage their stuff, but I'd guess in My Documents or something? Totally your call :)
-- Dan Smith www.danplanet.com KK7DS
I put it in my documents area now, but "python chirpw" does not find it. It must matter where it is placed for that line to work...
You have to be in the chirp.hg directory for that to work, yes. If it's in C:\Foo\chirp.hg, then you would do this:
c: cd \Foo\chirp.hg python chirp.hg
If you aren't comfortable at the command-line, you should probably be able to convince to the GUI to run chirpw with Python via some association mechanism...
No, I am fine at the command line, but assumed path was somehow taken care of by the env, since it wasn't noted.
If I cd to the new \chirp.hg directory and then run: python chirpw I get:
Traceback (most recent call last): File "chirpw", line 42, in <module> platform.get_platform().os_version_string(), File "P:\chirp.hg\chirp\platform.py", line 384, in os_version_string import win32api ImportError: DLL load failed: %1 is not a valid Win32 application.
-----Original Message----- From: Dan Smith [mailto:dsmith@danplanet.com] Sent: December 27, 2012 10:12 To: chirp_devel@intrepid.danplanet.com Cc: Drew Vonada-Smith Subject: Re: [chirp_devel] Development env?
I put it in my documents area now, but "python chirpw" does not find it. It must matter where it is placed for that line to work...
You have to be in the chirp.hg directory for that to work, yes. If it's in C:\Foo\chirp.hg, then you would do this:
c: cd \Foo\chirp.hg python chirp.hg
If you aren't comfortable at the command-line, you should probably be able to convince to the GUI to run chirpw with Python via some association mechanism...
-- Dan Smith www.danplanet.com KK7DS
No, I am fine at the command line, but assumed path was somehow taken care of by the env, since it wasn't noted.
Okay, I'll tweak the documentation.
Traceback (most recent call last): File "chirpw", line 42, in <module> platform.get_platform().os_version_string(), File "P:\chirp.hg\chirp\platform.py", line 384, in os_version_string import win32api ImportError: DLL load failed: %1 is not a valid Win32 application.
Hmm, well, I'm not sure what to do about that. That means the place it tries to import the win32 module (as installed from pywin32) fails. From the error, I'd expect that it's actually failing inside the pywin32 bits.
Are you on 64-bit Windows? Did you match the bitness of all the components you installed? In other words, did you get 32-bit python, 32-bit pywin32, and 32-bit pygtk?
I dunno if 32-bit versions of the dependencies are available for Windows, nor do I know much about how Win64 works, other than that it seems to have the same sort of expectation as other OSes, that everything in a single process be the same bitness.
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
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?
...sent from my cell phone
On Dec 27, 2012, at 10:21, Dan Smith dsmith@danplanet.com wrote:
No, I am fine at the command line, but assumed path was somehow taken care of by the env, since it wasn't noted.
Okay, I'll tweak the documentation.
Traceback (most recent call last): File "chirpw", line 42, in <module> platform.get_platform().os_version_string(), File "P:\chirp.hg\chirp\platform.py", line 384, in os_version_string import win32api ImportError: DLL load failed: %1 is not a valid Win32 application.
Hmm, well, I'm not sure what to do about that. That means the place it tries to import the win32 module (as installed from pywin32) fails. From the error, I'd expect that it's actually failing inside the pywin32 bits.
Are you on 64-bit Windows? Did you match the bitness of all the components you installed? In other words, did you get 32-bit python, 32-bit pywin32, and 32-bit pygtk?
I dunno if 32-bit versions of the dependencies are available for Windows, nor do I know much about how Win64 works, other than that it seems to have the same sort of expectation as other OSes, that everything in a single process be the same bitness.
-- Dan Smith www.danplanet.com KK7DS
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!
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@danplanet.com] Sent: December 27, 2012 10:34 To: chirp_devel@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
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...
CHIRP itself is neither 32 nor 64-bit, so your runtime can be either. However, external (binary executable, non-python) dependencies must *match*. Since I don't think there is a 64-bit version of the pygtk dependency pre-built for Windows, that means everything you have needs to be 32-bit.
Just so we're clear, you downloaded the 32-bit Python and the 32-bit (not amd64) pywin32, right?
If you just start python into the shell, what does your banner look like? It should be this:
Python 2.7.2 (default, Jun 12 2011, 15:08:59) [MSC v.1500 32 bit (Intel)] on win32
which shows that the python itself is 32-bit.
By the way, I am not getting any of these messages except direct. How do I turn off the "daily digest" feature?
It's standard mailman, just go here:
http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
And do the stuff at the bottom to set preferences. Note that since I've been copying you direct, the default preference is not to receive another copy via the list. I assume you didn't see Marco's reply, which was to the list only, in which case maybe the digest is holding you up.
Dan,
Yes, all parts were 32 bit. Python banner looks like you note, except a newer date and v2.7.3. Does that matter? The page didn't specify the subversion.
I went to the mailman page you note, but it has only an option to sign up, not to modify. I signed up a second time with the changed digest but got an error email in return that I couldn't sign up a second time.
73, Drew
-----Original Message----- From: Dan Smith [mailto:dsmith@danplanet.com] Sent: December 27, 2012 11:03 To: chirp_devel@intrepid.danplanet.com Cc: Drew Vonada-Smith 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...
CHIRP itself is neither 32 nor 64-bit, so your runtime can be either. However, external (binary executable, non-python) dependencies must *match*. Since I don't think there is a 64-bit version of the pygtk dependency pre-built for Windows, that means everything you have needs to be 32-bit.
Just so we're clear, you downloaded the 32-bit Python and the 32-bit (not amd64) pywin32, right?
If you just start python into the shell, what does your banner look like? It should be this:
Python 2.7.2 (default, Jun 12 2011, 15:08:59) [MSC v.1500 32 bit (Intel)] on win32
which shows that the python itself is 32-bit.
By the way, I am not getting any of these messages except direct. How do I turn off the "daily digest" feature?
It's standard mailman, just go here:
http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
And do the stuff at the bottom to set preferences. Note that since I've been copying you direct, the default preference is not to receive another copy via the list. I assume you didn't see Marco's reply, which was to the list only, in which case maybe the digest is holding you up.
-- Dan Smith www.danplanet.com KK7DS
OK, figured out the subscription part, sorry...
-----Original Message----- From: Drew Vonada-Smith [mailto:drew@whisperingwoods.org] Sent: December 27, 2012 11:12 To: 'Dan Smith'; 'chirp_devel@intrepid.danplanet.com' Subject: RE: [chirp_devel] Development env?
Dan,
Yes, all parts were 32 bit. Python banner looks like you note, except a newer date and v2.7.3. Does that matter? The page didn't specify the subversion.
I went to the mailman page you note, but it has only an option to sign up, not to modify. I signed up a second time with the changed digest but got an error email in return that I couldn't sign up a second time.
73, Drew
-----Original Message----- From: Dan Smith [mailto:dsmith@danplanet.com] Sent: December 27, 2012 11:03 To: chirp_devel@intrepid.danplanet.com Cc: Drew Vonada-Smith 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...
CHIRP itself is neither 32 nor 64-bit, so your runtime can be either. However, external (binary executable, non-python) dependencies must *match*. Since I don't think there is a 64-bit version of the pygtk dependency pre-built for Windows, that means everything you have needs to be 32-bit.
Just so we're clear, you downloaded the 32-bit Python and the 32-bit (not amd64) pywin32, right?
If you just start python into the shell, what does your banner look like? It should be this:
Python 2.7.2 (default, Jun 12 2011, 15:08:59) [MSC v.1500 32 bit (Intel)] on win32
which shows that the python itself is 32-bit.
By the way, I am not getting any of these messages except direct. How do I turn off the "daily digest" feature?
It's standard mailman, just go here:
http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
And do the stuff at the bottom to set preferences. Note that since I've been copying you direct, the default preference is not to receive another copy via the list. I assume you didn't see Marco's reply, which was to the list only, in which case maybe the digest is holding you up.
-- Dan Smith www.danplanet.com KK7DS
Maybe this is a hint to my problems? Is it normal for PyGTK to take half an hour to install or remove?
-----Original Message----- From: Drew Vonada-Smith [mailto:drew@whisperingwoods.org] Sent: December 27, 2012 11:15 To: 'Dan Smith'; 'chirp_devel@intrepid.danplanet.com' Subject: RE: [chirp_devel] Development env?
OK, figured out the subscription part, sorry...
-----Original Message----- From: Drew Vonada-Smith [mailto:drew@whisperingwoods.org] Sent: December 27, 2012 11:12 To: 'Dan Smith'; 'chirp_devel@intrepid.danplanet.com' Subject: RE: [chirp_devel] Development env?
Dan,
Yes, all parts were 32 bit. Python banner looks like you note, except a newer date and v2.7.3. Does that matter? The page didn't specify the subversion.
I went to the mailman page you note, but it has only an option to sign up, not to modify. I signed up a second time with the changed digest but got an error email in return that I couldn't sign up a second time.
73, Drew
-----Original Message----- From: Dan Smith [mailto:dsmith@danplanet.com] Sent: December 27, 2012 11:03 To: chirp_devel@intrepid.danplanet.com Cc: Drew Vonada-Smith 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...
CHIRP itself is neither 32 nor 64-bit, so your runtime can be either. However, external (binary executable, non-python) dependencies must *match*. Since I don't think there is a 64-bit version of the pygtk dependency pre-built for Windows, that means everything you have needs to be 32-bit.
Just so we're clear, you downloaded the 32-bit Python and the 32-bit (not amd64) pywin32, right?
If you just start python into the shell, what does your banner look like? It should be this:
Python 2.7.2 (default, Jun 12 2011, 15:08:59) [MSC v.1500 32 bit (Intel)] on win32
which shows that the python itself is 32-bit.
By the way, I am not getting any of these messages except direct. How do I turn off the "daily digest" feature?
It's standard mailman, just go here:
http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
And do the stuff at the bottom to set preferences. Note that since I've been copying you direct, the default preference is not to receive another copy via the list. I assume you didn't see Marco's reply, which was to the list only, in which case maybe the digest is holding you up.
-- Dan Smith www.danplanet.com KK7DS
Maybe this is a hint to my problems? Is it normal for PyGTK to take half an hour to install or remove?
Dunno about remove, but no, not install. Mine took a minute or less. PyGTK doesn't depend on PyWin32, and your import problem was coming from importing PyWin32, well ahead of any UI stuff being entered (which is what PyGTK is for). So, maybe an indication of something wrong on your system, but rather far away from what seemed to be the problematic component).
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@whisperingwoods.org] Sent: December 27, 2012 10:56 To: 'Dan Smith'; 'chirp_devel@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@danplanet.com] Sent: December 27, 2012 10:34 To: chirp_devel@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
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.
There are other ways to get the dependencies in 64-bit form, like getting all the bits and pieces individually, and/or compiling them yourself. They have to match, and reports seem to be pretty clear that 64-bit versions of all of those work fine on Windows, yes.
Is that confirmed? 32 doesn't seem to work under Win7/64 and 64 bit parts are apparently not all available.
Does the .exe build of chirp work for you? If so, then those 32-bit parts work just fine on 64-bit Windows. That installer just lays down a special copy of the 32-bit Python environment that is on my build system.
In the google hits, I see mention of folks tweaking DLL names, and locations (for some reason I don't understand). Have you tried any of that?
I should have access to a 64-bit windows environment tonight and will try to replicate all of this there. However, as I say, the build runs, so the environment (if properly installed) should run.
I should have access to a 64-bit windows environment tonight and will try to replicate all of this there. However, as I say, the build runs, so the environment (if properly installed) should run.
Just installed a clean 64-bit Windows 7 Enterprise machine. Installed the following files in order:
* python-2.7.3.msi * pygtk-all-in-one-2.24.2.win32-py2.7.msi * libxml2-python-2.7.7.win32-py2.7.exe * pywin32-218.win32-py2.7.exe * pyserial-2.5.win32.exe
Downloaded the chirp code, and ran the installed Python on chirpw. It started up perfectly the first time. Hopefully checking your downloads against the list above will help identify the problem.
I'll keep this VM image around for a bit in case there are questions, but it creeps me out having two Windows boxes (even if they're VMs) in the house :D
----- Original Message ----
From: Dan Smith dsmith@danplanet.com To: chirp_devel@intrepid.danplanet.com Sent: Thu, December 27, 2012 9:46:59 PM Subject: Re: [chirp_devel] Development env?
I'll keep this VM image around for a bit in case there are questions, but it creeps me out having two Windows boxes (even if they're VMs) in the house :D
I know what you mean. Since getting a Flex-3000 I even have one in the ham shack now!
Mike, N0SO
Thanks Dan. I had those exact same file versions. Reinstalled again and no joy. Either some specifics about the install matter, or I'm in DLL hell due to something else; who knows. I'm going to bail and try it instead on the target machine in the ham shack; that one is native Win32 Win 7. Will let you know.
-----Original Message----- From: Dan Smith [mailto:dsmith@danplanet.com] Sent: December 27, 2012 21:47 To: chirp_devel@intrepid.danplanet.com Cc: Drew Vonada-Smith Subject: Re: [chirp_devel] Development env?
I should have access to a 64-bit windows environment tonight and will try to replicate all of this there. However, as I say, the build runs, so the environment (if properly installed) should run.
Just installed a clean 64-bit Windows 7 Enterprise machine. Installed the following files in order:
* python-2.7.3.msi * pygtk-all-in-one-2.24.2.win32-py2.7.msi * libxml2-python-2.7.7.win32-py2.7.exe * pywin32-218.win32-py2.7.exe * pyserial-2.5.win32.exe
Downloaded the chirp code, and ran the installed Python on chirpw. It started up perfectly the first time. Hopefully checking your downloads against the list above will help identify the problem.
I'll keep this VM image around for a bit in case there are questions, but it creeps me out having two Windows boxes (even if they're VMs) in the house :D
-- Dan Smith www.danplanet.com KK7DS
My Windows 7 64-bit configured as suggested by Dan works fine. Python isn't in the path, so in the command window and in the chirp.hg folder, I have to launch CHIRP using the following command:
C:\Python27\python chirpw
I've since then created a shortcut on the desktop that launches CHIRP by setting Target equal to the following:
C:\Python27\python.exe "C:\Users\Jim\chirp.hg\chirpw"
Jim
On Fri, Dec 28, 2012 at 10:38 AM, Drew Vonada-Smith < drew@whisperingwoods.org> wrote:
Thanks Dan. I had those exact same file versions. Reinstalled again and no joy. Either some specifics about the install matter, or I'm in DLL hell due to something else; who knows. I'm going to bail and try it instead on the target machine in the ham shack; that one is native Win32 Win 7. Will let you know.
-----Original Message----- From: Dan Smith [mailto:dsmith@danplanet.com] Sent: December 27, 2012 21:47 To: chirp_devel@intrepid.danplanet.com Cc: Drew Vonada-Smith Subject: Re: [chirp_devel] Development env?
I should have access to a 64-bit windows environment tonight and will try to replicate all of this there. However, as I say, the build runs, so the environment (if properly installed) should run.
Just installed a clean 64-bit Windows 7 Enterprise machine. Installed the following files in order:
- python-2.7.3.msi
- pygtk-all-in-one-2.24.2.win32-py2.7.msi
- libxml2-python-2.7.7.win32-py2.7.exe
- pywin32-218.win32-py2.7.exe
- pyserial-2.5.win32.exe
Downloaded the chirp code, and ran the installed Python on chirpw. It started up perfectly the first time. Hopefully checking your downloads against the list above will help identify the problem.
I'll keep this VM image around for a bit in case there are questions, but it creeps me out having two Windows boxes (even if they're VMs) in the house :D
-- Dan Smith www.danplanet.com KK7DS
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
My Windows 7 64-bit configured as suggested by Dan works fine.
Cool!
Python isn't in the path, so in the command window and in the chirp.hg folder,
You know how to fix that, right?
Thanks for trying that, and I'm glad you've got a real environment set up now!
...mmm... Dan, I think it can be easier to teach him to develop on a live-cd linux then to remotely fight with windows. I'll also expect some difficulties with editor and CR/LF formats BTW
73 de IZ3GME Marco
On 12/27/2012 05:21 PM, Dan Smith wrote:
No, I am fine at the command line, but assumed path was somehow taken care of by the env, since it wasn't noted.
Okay, I'll tweak the documentation.
Traceback (most recent call last): File "chirpw", line 42, in <module> platform.get_platform().os_version_string(), File "P:\chirp.hg\chirp\platform.py", line 384, in os_version_string import win32api ImportError: DLL load failed: %1 is not a valid Win32 application.
Hmm, well, I'm not sure what to do about that. That means the place it tries to import the win32 module (as installed from pywin32) fails. From the error, I'd expect that it's actually failing inside the pywin32 bits.
Are you on 64-bit Windows? Did you match the bitness of all the components you installed? In other words, did you get 32-bit python, 32-bit pywin32, and 32-bit pygtk?
I dunno if 32-bit versions of the dependencies are available for Windows, nor do I know much about how Win64 works, other than that it seems to have the same sort of expectation as other OSes, that everything in a single process be the same bitness.
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
...mmm... Dan, I think it can be easier to teach him to develop on a live-cd linux then to remotely fight with windows.
Well, that's his call I guess. I'd hate to boot out of my regular environment to develop. Perhaps running inside a VM, but if he's not familiar with Linux, it might be uncomfortable.
On 32-bit Windows, at least, this is really not that hard. While writing up the Win32 setup procedures on the wiki the other day, I created a clean Windows (32-bit XP) VM and did the install quickly and successfully in less than an hour.
I'll also expect some difficulties with editor and CR/LF formats BTW
Nah, any editor worth its weight in electrons will do this correctly :)
I suppose that is one nice thing about the new LiveCD though.. should be perfectly adequate for development as well. Maybe we should ask Bob to include mercurial in the next spin of it so that folks can clone the repository without having to install another package?
participants (5)
-
Dan Smith -
Drew Vonada-Smith -
Jim Unroe -
Marco IZ3GME -
Mike Heitmann