On 2017-08-14 09:35-0000 Arjen Markus wrote:
Hi Alan,
I will ignore wxWidgets for the moment. Cmake seems to find something, but is
quiet about the reasons for its final decision:
Hi Arjen:
I don't want to distract you now from the important goal of
immediately finishing off your noninteractive testing for
MinGW-w64/MSYS2 and Cygwin. But once those tasks are completed (early
Tuesday?) I am virtually positive the revised ideas below will help
you to quickly solve your current find issues for wxwidgets on Cygwin.
The reason I revised my ideas, is I did do a bit more research this
morning. What follows should be skimmed lightly for now, but studied
in more detail once your noninteractive tests of MinGW-w64/MSYS2 and
Cygwin are completed.
One possibility I dismissed before (since you should be a veteran at
installing wxwidgets by now on all your platforms) is you might not
have the right set of wxwidgets packages installed on Cygwin.
For Cygwin, I believe the result is you will automatically be using
the Unix part of cmake/modules/FindwxWidgets.cmake, and that uses some
name variant of the wx-config script.
So after your noninteractive tests are done, you need to be sure to
install the package that contains some name variant of wx-config, and
from
<https://cygwin.com/cgi-bin2/package-grep.cgi?grep=wx-config&arch=x86_64>
the 3.x choice seems to be
libwx_gtk3u3.0-devel
Furthermore, if you click on that package name in the GUI provided
above, the name variant provided by that package is wx-config-3.0
(which is one of the variant names of wx-config that are supported by
cmake/modules/FindwxWidgets.cmake).
Thus, if you have libwx_gtk3u3.0-devel (and all its dependencies) installed
already, then execution of wx-config-3.0 within
cmake/modules/FindwxWidgets.cmake should result in a consistent set of
compile flags and libraries. So it should all "just work".
However, in the case that normally reliable executable fails for some
strange reason within cmake/modules/FindwxWidgets.cmake, i.e., you
still get wxwidgets "not found" messages, then as I have previously
mentioned you can use the cmake --debug-out and --trace options to
debug what is going on. But use of those cmake options are a really
blunt tool that generate a tonne of output. So save that possibility
for a last resort and instead first use a much more selective choice
for debugging cmake/modules/FindwxWidgets.cmake which is to uncomment
the message commands in the DBG_MSG and DBG_MSG_V macros that occur
within that module. If it turns out you cannot figure out what is
going wrong with that find module from that selective debug output,
please send that cmake debug output to me to see if I can use that
information to help you out.
But I emphasize again, all the above ideas are for after your completion
of the noninteractive tests.
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
__________________________
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel
