On 2013-03-15 16:35+0100 Arjen Markus wrote: > Hi Alan, > > On 2013-03-14 19:00, Alan W. Irwin wrote: > >> >> One issue that completely surprises me is why in the world do the >> MSVC/ifort set of compilers build the test_plend executable as >> if C++ code (as opposed to plain C code) is involved? >> > > Well, as we are building a static library the device drivers are > also built as static libraries ... Oh, that is an explicit option > in the command line. I will turn that off and see what happens. > > Regards, > > Arjen
Yes, a static runtime (a user decision concerning which Microsoft core libraries should be used) is a completely different issue than whether the PLplot libraries are built as shared or static. If PLplot libraries are built as static, you are going to see a problematic mixture of code compiled from both C and C++ sources in libplplotd (until someone fixes that issue for the PLplot static libraries' case). If PLplot libraries are built as shared then they should contain nothing but code compiled from C sources. 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 __________________________ ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ Plplot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/plplot-devel
