On 2017-09-26 10:43+0200 Laurent Berger wrote:
Hi alan,
Ok in this folder http://perso.univ-lemans.fr/~berger/Afsd56/plplot/ you got
everything from git clone to wxopencv build
In http://perso.univ-lemans.fr/~berger/Afsd56/plplot/ you can find result of
plplot install
in http://perso.univ-lemans.fr/~berger/Afsd56/plplot/TXT_INFO/ you 've got
cmakecache and cmakeoutput for plplot and same file for wxopencv project
using plplot. In buildprocessplplot.txt you have results from git clone,
build plplot in debug and release and install process.
In my wwxopencv project I use too ceres-solver glog and gflag and opencv and
openscenegraph lib
my script command to install plplot and wxopencv are installplplot.sh and
installwxopencv.sh
if something is missing tell me what
Hi Laurent:
I looked at
<http://perso.univ-lemans.fr/~berger/Afsd56/plplot/TXT_INFO/installPlplot.sh>.
From my perspective alone, the major issue with that script
is you are attempting to use cmake in a way that is largely outside my
experience. For example, I have no experience with the --build option
for cmake, only limited Windows experience (with the Wine version of
Windows) and no experience with the "Visual Studio 14 2015 Win64"
generator.
In order for me to help you further, here is what I would like you to
do. Please switch to a more low-level PLplot configure and build
process that I have a better chance of understanding. That is, you
should use the "NMake Makefiles" generator and do your build with
nmake like this without using the cmake --build option.
cmake -G"NMake Makefiles" $optCMAKE \
-DBUILD_SHARED_LIBS:BOOL=OFF \
-DwxWidgets_ROOT_DIR:PATH=G:/lib/wxWidgets-3.1.0 \
-DwxWidgets_LIB_DIR:PATH=G:/lib/wxWidgets-3.1.0/lib/vc_x64_lib \
../../"$RepoSource"
nmake VERBOSE=1 install
So the only change from what you are currently doing is the choice of
generator for cmake and running nmake rather than several different
cmake --build commands to do the installation. Note, that nmake
simply builds the named target ("install" in this case which also
builds the "all" target first). The VERBOSE=1 option outputs some
extra details that are sometimes useful. Then all I really need to see
for this PLplot case is the output (combined stderr and stdout) from
this slightly revised script which should include all output
from both the above cmake and nmake commands.
Once I understand what is going on with the PLplot configure (with
cmake) and build and install (with nmake), then we should follow up
with a similar analysis of the configure and build of your own
software.
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
