Just realized I only replied to Alan, not the list - see below if you are
interested.
Alan I added my bin directory to the PATH. The examples now run, giving me a
list of drivers, however, when I select a driver, plplot exits saying it cannot
load the driver. Suggestions from any of our Windows users welcome as I'm not
used to using dlls. I wonder if Plplot is trying to load dlls that don't exist.
E.g. I probably don't have wxWidgets dlls built, just static Libs. Although
even if I select svg, which has no external dependencies I get the same error.
Phil
-----Original Message-----
From: "Phil Rosenberg" <philip_rosenb...@yahoo.com>
Sent: 22/09/2014 17:44
To: "Alan W. Irwin" <ir...@beluga.phys.uvic.ca>
Subject: RE: [Plplot-devel] tcl build problem
Hi Alan
I have started this testing. It all works fine with my standard static lib,
static runtime visual studio, cmake 3 setup.
However if I try dynamic runtime with dynamic Libs then I get errors for all
the test_xxx_dyndriver projects. The errors look like:
Generating test_dyndrivers_dir/xxx.driver_info
Could not open driver module xxx
CUSTOMBUILD : libltdl error : No error information
The test_dyndrovers_dir is full of 0 byte files and if I try to run an example
I get a popup saying plplot.dll is missing from your system. Although I do have
the dlls in my bin directory. Maybe it is just a case of adding the bin
directory to my path.
I will keep you updated
Phil
From: Alan W. Irwin
Sent: 05/09/2014 12:40
To: phil rosenberg
Cc: PLplot development list
Subject: Re: [Plplot-devel] tcl build problem
On 2014-09-04 13:51-0700 Alan W. Irwin wrote:
> On 2014-09-01 11:08-0700 Alan W. Irwin wrote:
>
>> I now plan to do a comprehensive run-time test using
>> scripts/comprehensive_test.sh for the same Tcl/Tk/Itcl/Itk install
>> locations, and such a comprehensive test (involving run-time tests of
>> both the build tree and install tree for our 3 major build
>> configurations) will almost guarantee finding more changes that have
>> to be done for our three different build systems (core build +
>> CMake-based and traditional build systems for the installed examples).
>
> That prediction was spot on, and over the last few days I have been
> plugging away at all the issues that were found by that comprehensive
> testing. Today I finally got a breakthrough on what had been an
> intractable problem (dealing with blanks in pathnames for the Makefile
> + pkg-config traditional build system for the installed examples).
>
> Propagating that solution from one of our libraries to the rest
> requires extensive and non-trivial build-system changes that all need
> to be comprehensively tested, but I think the end is finally in sight,
> so I might even get this pushed by late Friday.
Hi Phil:
Actually, I just made that push (commit 6f7f855) a little ahead of my
ETA. This should complete my project to get comprehensive run-time
testing (done with the scripts/comprehensive_testing.sh script) to
work completely on Linux for a test case where
Tcl/Tk/itcl/itk/iwidgets were installed with a pathname prefix that
had a blank. This should clear out many of the blank-in-path issues
that would have hindered you for your own comprehensive run-time
testing.
@everyone: As part of these series of commits I also took the
opportunity to remove all mention of the unused LIB_TAG variable
from our build-system logic. This change makes that logic
much easier to read.
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
__________________________
------------------------------------------------------------------------------
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
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel
