On 20/02/2014 18:04, Joe Taylor wrote:
Dear colleagues,
Hi Joe,
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.
Good news. So Joe, are you now able to build wsjtx on Windows with the
checked in CMake script?
If so I would really like to switch to building with CMake as the
"normal" practise. Some of the reasons are:
1) I have code to automatically extract the Subversion revision number
(no more having to touch mainwindow when checking in).
2) I have code to generate a wsjtx_config.h including configuration
options from CMake.
3) I have code to control the product version number from a central
checked in file.
4) I am making good progress with automatic packaging on all platforms.
5) No need to maintain multiple build scripts.
6) ...
(1) (2) and (3) require some source file changes to take full advantage
of them.
One outstanding issue is integration with QtCreator, I am not a
QtCreator user at all so I don't know how well building with CMake fits
in. Given that qt-project.org is clearly committed to CMake users since
they include and maintain the CMakeConfig scripts in the Qt releases, it
can't be that difficult. I'll admit to not having looked into this even
though it is on my list, does anyone have any experience? I would hope
there is some easy way to tell QtCreator to use a pre-defined external
command to build rather than use qmake.
None of the above is critical or urgent but I feel that there is lots of
benefit to be gained if we can make the shift. I have deliberately not
suggested this up until now given that you have had problems with CMake.
<snip>
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?
All sounds good to me.
I am making a big push on completing my current outstanding work.
Unfortunately integration testing has made it clear a few of my original
implementation ideas had to be rethought. I hope to make a checkin
before Monday which might be a bit broken but it will be at a point
where I think fixes will be reasonably isolated rather than wholesale
re-factorings.
I'm not too concerned if I miss the deadline since a Subversion repo
switch for a workspace is a single command and shouldn't be a problem
(svn relocate).
It would be nice if the BerliOS migration included user logins, ssh keys
and, ML subscriptions. But none are very onerous to complete manually.
We just need to be careful that any users that are inactive don't get
lost thinking the ML traffic has dwindled to nothing when it has just
switched to a different server. Since the project website is not moving
that shouldn't really be an issue anyway.
-- Joe, K1JT
73
Bill
G4WJS.
_______________________________________________
Wsjt-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/wsjt-devel
