On 2016-12-17 03:30-0500 Pedro Vicente wrote:

> false alarm, sorry
>
> what happened is that my wxWidgets libraries were not built.
>
> In Windows , I don't do install, but rather build software and leave it where 
> it was built, and sometimes delete and rebuild.
>
> In PLplot 5.11.1 the build actually did not include the wxWidgets projects 
> and files, so it built.
> but in the git version it did include the wxWidgets projects and files, so it 
> failed.
>
> there's the small detail that cmake should have had allerted that wxWidgets 
> was not built...but probably not important , or could just have been my 
> mistake somewhere.
>
> so the result is for cmake build with wxWidgets
>
> Rebuild All: 88 succeeded, 0 failed, 0 skipped =

To give some quick background for my answer,
our build system enables three principal configurations:

(1) Shared PLplot libraries + dll device drivers which are dynamically loaded by
our core shared library (identified by its "plplot" basename).

(2) Shared PLplot libraries + device driver code embedded in our core
shareded library (identified by its "plplot" basename).

(3) Static PLplot libraries + device driver code embedded in our core
static library (identified by its "plplot" basename).

In case (1) the wxwidgets device driver dll (with basename of wxwidgets)
exists, but otherwise that dll does not exist for cases (2) and (3).
Of course, that device driver dll must be distinguished from
the wxwidgets binding library (identified with the basename of
plplotwxwidgets) which exists in all 3 cases, and which in
cases (1) and (2) will be shared and in case (3) will be static.

I am not sure whether you are referring to the wxwidgets device driver
(which if you use a static build will make it become part of the
plplot library) or plplotwxwidgets library above.

As far as I know, our build system handles all build dependencies of
wxwidgets (when it exists for case (1)), our plplot library (both
without [case (1)] and with [cases (2) and (3)] wxwidgets device
driver code embedded in it) and the plplotwxwidgets library.  Can you
give me an example of a wxwidgets-related specific target
(e.g., wxwidgets, plplot, plplotwxwidgets, wxPLviewer,
test_wxPLplotDemo, or even wxPLplotDemo) (where I include plplot in
the list for just cases (2) and (3) and exclude wxwidgets for those cases)
that you attempt to (re)build with your Windows IDE that obviously has
incorrect dependencies?

Also, you cannot change horses in mid-stream, i.e., you cannot change
a build tree that is configured for (1), (2), or (3) into one of the
other cases.  Instead, you have to start fresh with an empty build
tree for each of those three cases.  Is that the source of the
dependency difficulty you have encountered?

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

Reply via email to