Dear colleagues,

It's a great pleasure working with you folks! What a skillful and enthusiastic team we have working together, at present! Lots of progress being made!

Three things on my mind, right now:

1. Thanks to Bill and Greg, I'm rapidly becoming a CMake convert. It's an extremely convenient way to build programs like ours.

I fixed several typos in wsjtx-build-setup.bat: *.bat rather than *.txt in two places, wsjt-dev.bat instead of wsjtx-dev.bat, and also did several minor edits to wsjtx-dev.adoc. Then I followed the instructions there and built the Release version WSJT-X for Windows, with no further problems. (I also built the Debug version, but I think it came out identical to Release. Presumably this is not intended.)

Greg, please check the changes I've just committed to
wsjtx-build-setup.bat and wsjtx-dev.adoc, to be sure you're OK with them.

2. I think I have put wsjt/trunk into reasonably good shape. It now builds wsjt10 properly in both Windows and Linux, at least on my development systems. This includes packaging the executable and co-requisite files using PyInstaller. (note to G4KLA: PyInstaller should work for OS X, also.)

Still to do: bring code for wsjt up to our present standards, in other ways.

3. Unless I hear arguments against it, I propose to submit a ticket to SourceForge on Monday next week, asking them to migrate the whole WSJT project from BerliOS to SourceForge. No doubt this will be somewhat disruptive. I imagine we'll all need to register at SourceForge, possibly subscribe anew to mailing lists, etc., etc. Probably we should refrain from doing any more commits to BerliOS after Monday. Any other advice?

        -- Joe, K1JT
_______________________________________________
Wsjt-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/wsjt-devel

Reply via email to