Hello all, I used a little app called innoextract (you may already know of it) to extract the Windows.exe that Joe sent out recently. For those unfamiliar with it, using innoextract, you don't have to install with Wine to get the extracted files; pull the files out with:
innoextract -d ./wsjtx-r3644 ./WSJTX_122r3644.exe InnoExtract Link: http://constexpr.org/innoextract/ Wsjtx-r3644: http://physics.princeton.edu/pulsar/K1JT/WSJTX_122r3644.exe When using the Makefile.linux build method, there are a number of files / folders we have to either link: ln -s or cp straight over into ../wsjtx_install (kvasd, ./save ./samples ./doc ./Palettes mouse_commands.txt, shortcuts.txt .. etc). While comparing the WSJTX svn source tree against the extracted Windows files, I found 4 files that aren't present in svn, at least, not that I can find, but are present in the extracted Windows folder: - azel.dat - CALL3.TXT - cty.dat - qt.conf I found a web-link to cty.dat :http://www.country-files.com/cty/ .. I'm sure there are other sites as well. >From a Linux packaging perspective (tar.gz, .rpm, .deb etc), should we simply copy these from an Windows install or should they be added to the source tree and pulled at packaging time? 73's Greg, KI7MT [email protected] _______________________________________________ Wsjt-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/wsjt-devel
