On 25/09/2014 19:39, Josh Rovero wrote:
Hi Josh,
Bill Somerville <[email protected] <mailto:[email protected]>>
asked:
> That is indeed a defect, but why are you not using the CMake build?
I'm pretty comfortable with qmake and build/run several other Qt
projects that way. WSJTX is the only cmake project, Cmake builds
it, but doesn't install it the way I expect it to. Yeah, old dog, new
tricks, but.......
I understand, but CMake has so many more facilities and the project is
slowly diverging if you build with qmake. The reason is that every time
a feature of CMake is taken advantage of that cannot be easily
replicated with qmake a hack is put in place to prop up the qmake build.
Those hacks invariably get the qmake build to work but they do not
produce exactly the same product.
Using qmake is OK'ish for testing purposes and developing if you must
but you are bound to fall foul of the differences pretty soon. I will
carry on fixing the qmake build (eventually) as long as it is practical
but I am of a mind not to fix this particular defect in v1.4 just in
case someone tries to build a deployable package using the qmake project
file.
I am currently preparing the main line for WSJT-X for v1.5 development
and will sort out that issue there at least.
--
P.J. "Josh" Rovero Ham Radio: KK1D
http://www.roveroresearch.org http://www.roveroresearch.info
73
Bill
G4WJS.
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
