Joe,
As always thanks for the help.
Your point was well taken even before you made it. While windows sticks
its own time stamps on
when SVN does an import I was pretty much assuming, based on comments on the
development
reflector, I was on my own compiling under windows and the make files were
likely dated.
While I do not have much Linux background I do have a lot of programming
background, mostly
embedded systems, and am used to tool chain and make file headaches.
As far as Angelia support... Opps... I was working from memory which is an
increasingly bad thing
to do. I meant Diana support. Somehow I brain farted Angelia for Diana,
probably based on a picture
I saw, and it stuck. In any event Diana files are referenced several
places in the make file, the files
are not in the release, and a grep of the directory showed the make file was
the only place Diana was
referenced. I removed them from the make and that obstacle was passed.
In the latest news I have gotten an "almost" clean compile that appears to
run just fine. The make
is producing an incredible number of warning which makes finding the actual
issue interesting. I finally
tracked down a comment about an undefined reference to usleep being
undefined in usleep.c. This
lead to a further discovery of a seeming circular reference to usleep_ and
usleep between usleep.c and cutil.c.
For a test I commented out the call to usleep in usleep.c and immediately
got a working compile although likely
a cpu hungry version. It looks like usleep.c was meant to fix an issue
that pops up during a compile under windows
that was never fully implemented. I let you know what I find when I get it
fully fixed.
In the meantime I am compiling and a happy camper.
73 de Bill ND0B
-----Original Message-----
From: Joe Taylor
Sent: Monday, February 10, 2014 1:08 PM
To: Bill Ockert - ND0B ; WSJT Devel
Subject: Re: [Wsjt-devel] Tool chain and make file to compile WSJT
underwindows.
Bill --
In the past we have gone to some considerable effort to ensure that
users can compile WSJT on *nix-based platforms. Not so much for
Windows; since we provide a click-to-install Windows package, there has
never been any demand.
The Makefile.MinGW in the SVN repository is configured for my personal
development system. We have never intended for it to provide an
out-of-the-box WSJT build on another user's system. As stated before,
you will almost surely need to tweak the makefile in various ways.
You mention "angelia support". I have no idea what this refers to.
In due course we may put together some more detailed instructions for
what you're trying to do. Right now, our development efforts are
concentrated more on WSJT-X than WSJT.
-- Joe, K1JT
PS: did you receive my off-list email of Feb 7, about filtering of Tx
audio in your Flex 5000? I got no response.
ND0B wrote:
Thank you for the reply,
Things are slowly coming together. While Makefile.MinGW appears to be
the most correct makefile it
contains support for angelia and none of the referenced files are in the
distribution A grep of all the files
showed that the makefile was the only place angelia showed up so I
cleaned all references and got to the next stage.
I did install the makefile listed version of the installer
(pyinstaller-1.5.1) and then based on an error I was getting about the
configure file being non existant or corrupt ran the configure.py for
it. That cleaned up that issues.
The make is now bombing out in the section creating Audio.pyd with the
following error:
error: unknown file type '' (from '-fbounds-check')
(that is two single quotes)
I have played around a bit with the --opt line including the bad idea of
removing it... in that case the make continues on and after tons of
warning produces an file that does not execute correctly. Nothing seems
to get it past that stage.
I have tried both gfortran and g95 with the same results.
I would appreciate hearing from anyone who has seen something similar.
This appears to be something with the python setup so will likely be
next weekends project.
Thanks in advance for any help!!
73 de Bill ND0B
-----Original Message----- From: Joe Taylor
Sent: Saturday, February 08, 2014 4:19 PM
To: WSJT Devel
Subject: Re: [Wsjt-devel] Tool chain and make file to compile WSJT
underwindows.
Hi Bill,
On 2/8/2014 11:20 AM, Bill Ockert - ND0B wrote:
Good morning,
I am attempting to get the tool chain set up to compile WSJT under
windows.
The blip on the WSJT page says “To compile the programs for Windows you
can use the MinGW system and g95. You will also need the python packages
listed above.”
That packages listed above are
subversion
a.. python2.x-dev
a.. python-numpy
a.. python-imaging-tk
a.. python-pmw
a.. libportaudio2
a.. libportaudio-dev
a.. libsamplerate0-dev
a.. libfftw3-dev
a.. gfortran or g95
So far I have loaded MingW and seem to be compiling fortran OK.
I have loaded Python 2.7 and Numpy, I am working on loading imaging-tk
and pmw.
Question: Are the lib* libraries required under windows? I not sure
how to interpret the “python packages” comment above.
It simply means you need to install the packages in the list.
Question: Is Makefile.MinGW the correct make file to use for development
under windows with MinGw?
Yes.
You might need to tweak the Makefile according to your own paths, etc.
To get through all the steps in the Makefile you'll also need to install
pyInstaller, which makes an executable wsjt9.exe that contains python
and all the needed modules. To run the program on your own machine,
however, you don't need the "pyInstaller" step.
Any pointers to get the windows based tool chain set up would be
greatly appreciated.
Thanks!!
73 de Bill ND0B
-- 73 and GL de Joe, K1JT
_______________________________________________
Wsjt-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/wsjt-devel
_______________________________________________
Wsjt-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/wsjt-devel
_______________________________________________
Wsjt-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/wsjt-devel
