Hi Bill,
So Joe, are you now able to build wsjtx on Windows with the
checked in CMake script?
Yes, the build seems to work perfectly.
I haven't thought about packaging issues yet, but it seems I may need
only to change the paths in wsjtx.iss. Or do you have another packaging
scheme that would be better?
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.
I just tried opening CMakeLists.txt with QtCreator, rather than
wsjtx.pro. After a little bit of fooling around, it works OK.
It will not be a problem. I will continue to use QtCreator for editing
code and for designing the GUI. Actual project builds can be done
either inside QtCreator or in a command window.
So yes, let's make CMake the default for building WSJT-X.
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.
OK. There's nothing magical about next Monday -- we could put it off
for weeks, if necessary. But if we're ready to make the switch, I guess
we might as well bite the bullet sooner rather than later.
-- Joe
_______________________________________________
Wsjt-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/wsjt-devel
