Re: [Plplot-general] [msys2, qt] no rule to make target moc_compilation.cpp

[Thomas G. <t_g...@gm...>]

Hi Alan,

thanks for your response.

Unfortunately, the default configuration fails with the same error (see
attached files).

Sorry, that I was unclear about this: When I saw failure in the defaults
I started dropping devices to single out the one that seemed to cause
the issue. It could still be that I'm missing something that needs to be
installed before I can use it, but I'm not sure what.

I can give you the output files and tests when just disabling Qt later
(I don't have access to a windows throughout the day).

Best, Thomas

Alan W. Irwin wrote on 05/18/2017 06:04 AM:
> On 2017-05-18 01:00+0200 Thomas Gläßle wrote:
>
>> Dear plplot community/devs,
>>
>>
>> I'm trying to build plplot with the qt driver on msys2. From a freshly
>> unpacked plplot-5.12.0 folder, I run the following commands in the msys2
>> mingw64 shell:
>>
>>    pacman -S mingw-w64-x86_64-qt4
>>
>>    mkdir build && cd build
>>
>>    cmake .. -G 'MSYS Makefiles' -DDEFAULT_NO_BINDINGS=ON
>> -DDEFAULT_NO_DEVICES=ON -DENABLE_qt=ON -DPLD_qtwidget=ON >& cmake.out
>
> Hi Thomas:
>
> There is obviously a very large number of different combinations of
> CMake options that are possible to use with our build system, and
> because of that "combinatorial" issue, lots of those combinations
> (such as what you chose above) are completely untested, and thus may
> have issues.  For example, the above combination disables C++, but our
> qt device driver is written in that language so I am not sure our
> build system can handle that combination.  Therefore, as a first step
> I advise you to drop all specific options and instead just choose the
> default options (the particular combination of options which are best
> tested). You do that (again starting with an empty build tree as you
> did above) by simply running
>
> cmake .. -G 'MSYS Makefiles' >& cmake.out
>
> If the resulting cmake.out shows any showstopping errors, then disable
> the relevant components, but do not disable working components such as
> C++ (at least in your early PLplot testing on this platform).
>
> To expound a broader view for all Windows users here, I believe the
> MinGW-w64/MSYS2 platform is potentially our most important Windows
> platform because it gives access to so many useful free software
> libraries in native Windows form that are all ABI compatible and which
> also add a lot of power (such as the number of different qt devices)
> to PLplot.  And some time ago one of our users (Greg Jung) did have
> fairly complete success with this platform (including our qt device
> driver). So I welcome all user interest in this platform, and I have
> also long been encouraging our developers with access to Windows to
> test PLplot on this platform for themselves (even though I
> don't have access to Windows myself).
>
> The current status is some limited testing (i.e., excluding qt) has
> been done on that platform by at least one of our developers but none
> of our developers has yet attempted the near-complete testing done by
> Greg.  However, from recent discussions, I have hopes that "largely
> untested by developers" status will change soon for this platform
> so that we can unreservedly recommend it to our Windows users.
>
> Alan
> __________________________
> Alan W. Irwin
>
> Astronomical research affiliation with Department of Physics and
> Astronomy,
> University of Victoria (astrowww.phys.uvic.ca).
>
> Programming affiliations with the FreeEOS equation-of-state
> implementation for stellar interiors (freeeos.sf.net); the Time
> Ephemerides project (timeephem.sf.net); PLplot scientific plotting
> software package (plplot.sf.net); the libLASi project
> (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
> and the Linux Brochure Project (lbproject.sf.net).
> __________________________
>
> Linux-powered Science
> __________________________
>