Re: [Plplot-devel] Cannot compile plplot using VS 2017

[Phil Rosenberg]

Excellent, thanks Alan
On Sun, 23 Sep 2018 at 01:25, Alan W. Irwin  wrote:
>
> On 2018-09-22 23:16+0100 Phil Rosenberg wrote:
>
> > Hi Laurent
> >
> > I have implemented your first solution. If you could let me know that
> > things now work for you that would be great.
>
> Hi Phil:
>
> Although your question was addressed to Laurent, it should interest
> you to know your fix causes no issues for Linux (i.e., building the
> test_c_wxwidgets and test_wxPLplotDemo targets caused no obvious build
> or run-time issues).
>
> Alan
> __
> Alan W. Irwin
>
> 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
> __


___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Re: [Plplot-devel] Cannot compile plplot using VS 2017

[Laurent Berger]

Hi,

https://sourceforge.net/p/plplot/plplot/ci/4a5f94a70ac259d696dfaa8117cead7ad89b13f3/ 
: It works thanks!



New file is now

// Headers needed for Rand
#ifdef _WIN32
// This include must occur before any other include of stdlib.h due to
// the #define _CRT_RAND_S
#define _CRT_RAND_S
#include 
#else
#include 
#endif

// wxwidgets headers
#include 
#include 
#include 
// PLplot headers
#include "plDevs.h"
#include "wxwidgets.h" // includes wx/wx.h


// std and driver headers
#include 
#include 


Le 23/09/2018 à 02:23, Alan W. Irwin a écrit :

On 2018-09-22 23:16+0100 Phil Rosenberg wrote:


Hi Laurent

I have implemented your first solution. If you could let me know that
things now work for you that would be great.


Hi Phil:

Although your question was addressed to Laurent, it should interest
you to know your fix causes no issues for Linux (i.e., building the
test_c_wxwidgets and test_wxPLplotDemo targets caused no obvious build
or run-time issues).

Alan
__
Alan W. Irwin

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
__




___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Re: [Plplot-devel] Cannot compile plplot using VS 2017

[Phil Rosenberg]

Good news! Thanks for reporting the problem.

Phil

Get Outlook for Android


From: Laurent Berger 
Sent: Sunday, September 23, 2018 11:12:50 AM
To: Alan W. Irwin; Phil Rosenberg
Cc: PLplot development list
Subject: Re: [Plplot-devel] Cannot compile plplot using VS 2017

Hi,

https://sourceforge.net/p/plplot/plplot/ci/4a5f94a70ac259d696dfaa8117cead7ad89b13f3/
: It works thanks!


New file is now

// Headers needed for Rand
#ifdef _WIN32
// This include must occur before any other include of stdlib.h due to
// the #define _CRT_RAND_S
#define _CRT_RAND_S
#include 
#else
#include 
#endif

// wxwidgets headers
#include 
#include 
#include 
// PLplot headers
#include "plDevs.h"
#include "wxwidgets.h" // includes wx/wx.h


// std and driver headers
#include 
#include 


Le 23/09/2018 à 02:23, Alan W. Irwin a écrit :
> On 2018-09-22 23:16+0100 Phil Rosenberg wrote:
>
>> Hi Laurent
>>
>> I have implemented your first solution. If you could let me know that
>> things now work for you that would be great.
>
> Hi Phil:
>
> Although your question was addressed to Laurent, it should interest
> you to know your fix causes no issues for Linux (i.e., building the
> test_c_wxwidgets and test_wxPLplotDemo targets caused no obvious build
> or run-time issues).
>
> Alan
> __
> Alan W. Irwin
>
> 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
> __

___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

[Plplot-devel] Tentative plans for 5.14.0 freeze date, testing period, and release

[Alan W. Irwin]

I continue have a large list of different topics I would like to work
on for PLplot, but, on the other hand, comprehensive tests are looking
good (at least on Debian Buster) right now, and it has been much too
long since our last release (mostly because of the "new computer" and
"new distro version" issues I have been encountering).  So I plan to
spend the next several weeks working on the most urgent development
topics I have a good chance of finishing before the soft freeze, with
a proposed date of the freeze near the end of October followed by a
testing and debugging period with the actual release of 5.14.0
occurring roughly in mid November.  Please let me know if the general
timing of that soft freeze, testing period, and subsequent release
will cause you any issues with development topics you would like to
push before the release of 5.14.0.  But if I don't hear any strong
objections along those lines, then later this week I plan to finalize
that soft freeze date as October 27th (to be definite and to place it
on the last Saturday in October).

To give you more details about the actual events leading up to the
release, the overall timing of the release depends critically on the
soft freeze date, i.e., the date where we ask our developers to quit
pushing new development topics and instead concentrate on fixing bugs
and updating the documentation until the release is completed.  What
that means practically is just after the freeze date I will call for intensive
testing and use those results to solve as many bugs as possible
without introducing any new development topics.  That process will
likely take one or two weeks after the freeze date before I can start
the official release process currently described for Debian Oldstable
= Jessie in README.Release_Manager_Cookbook.  But that release process
(which normally just takes a day or two) will likely get stretched out
a bit because that cookbook likely needs quite a bit of updating as I
encounter issues that are caused by my current platform of Debian
Buster.  In sum, the official release should occur something like two
to three weeks after the soft freeze date depending on the
participation from you guys in the testing, how difficult it is to
sort out the bugs found by that testing, and how much I have to
upgrade the release process for Debian Buster.  So that's how the
currently proposed freeze date of October 27th gets transformed into a
release date that is roughly in mid November.

Alan
__
Alan W. Irwin

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
__


___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Re: [Plplot-devel] Is there some important reason for using the -single-module linker option on modern Mac OS X?

[Alan W. Irwin]

On 2018-03-22 19:12-0700 Alan W. Irwin wrote:


To those here with knowledge of Mac OS X linking:

According to  there exists
the following ld options:

"
-single_module When building a dynamic library build the library so that it 
contains only one module.


-multi_module
When building a dynamic library build the library so that it contains
one module for each object file linked in. This is the default.
"

We currently use -single_module for linking on this platform
(see CMAKE_USER_MAKE_RULES_OVERRIDE in the top-level CMakeLists.txt
file).

However that override was imposed 12 (!) years ago to address a
linking issue that I suspect no longer exists.  For example, a google
search for the terms  found nothing relevant
beyond the CMake mailing-list discussion I generated about this issue
back then.

So unless I hear from Mac OS X experts here that there is some
important reason for using the -single_module option for linking
dynamic libraries on modern Mac OS X, I plan (on Sunday to give you a
couple of days to respond) to drop this override completely to conform
to how other CMake-based build systems configure linking of dynamic
libraries on Mac OS X.



From the "better late than never" department, I have indeed now

(commit d6a762704) removed this override that is specific to Mac OS X
"on Sunday", but frankly I forgot all about this until reminded of it
today by my ToDo list so it is a large number of Sundays later than I
anticipated in the above post!

N.B. This fundamental linking change for Mac OS X platforms needs to
be comprehensively tested on Mac OS X.  So I need a volunteer (with
lots of free disk space that is temporarily consumed by the test until
deletion of many plot files at the end of the test) to do that.  Just
run

scripts/comprhensive_test.sh --help

to see what is possible with that script.  However, be warned that if
you specify no options the default is *all* components of the
comprehensive test are run.  This means, for example, that you will be
doing a lot of babysitting as you work through the interactive
components of the test so at minimum for a first try you will likely
want to constrain the test with the

--do_test_interactive no

script option to make the test into something that can quietly be run
in the background with little interaction needed from you.

Also, note the test generates a report tarball with all the details of
the test whether it succeeds or not.  So please send me that report
tarball regardless of results since in case of failures that tarball
helps me to analyze the reason for the failures, and in case of
success that tarball helps me to assemble a report of your
comprehensive test success for our wiki.

Alan
__
Alan W. Irwin

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
__


___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel