From: Aaron H. <he...@co...> - 2015-03-31 12:45:10
|
Alan, The version I'm using is from git, but after doing a remote fetch, I can see that I'm a few commits behind. I'm working off of 0bfe721. Happy to provide as many details as you need. Should I advance first and see if its fixed? Is there a bug submission std I can check out to see how much detail you'd like? Thanks, Aaron. -----Original Message----- From: Alan W. Irwin [mailto:ir...@be...] Sent: Tuesday, March 31, 2015 1:22 AM To: Aaron Hexamer Cc: plp...@li... Subject: RE: [Plplot-general] Am I going about this the best way? Hi Aaron: On 2015-03-30 22:29-0500 Aaron Hexamer wrote: > Alan, > > Thanks for the hint on Qt4 vs Qt5 - probably spared me a few hours of pain! > I set out to trial the memqt driver and ran into some issues with the > build on MSVC 2012. > > 1) For some reason, which I had never encountered before, the CMake > system generates incorrect build files when the source path includes > spaces. Not a big deal really, I can just move to a path without > spaces. I don't recall the exact issue, but I think it broke up > include paths into separate entries. I am using a fairly old version > of CMake (2.8.12.2) That's an issue with our own build system and not CMake. From time to time we try and clean up some aspect of this issue, but it is a low priority because it is so easy to use PATH's without spaces in them. > > I started with Qt configured for dynamic linking > > 2) I tried to build PLplot as a shared lib, then realized that was not > really going to work for me since my application accessed some other > normally private functions, not exported in the DLL (pldtik, pldprec, etc). > > 3) I tried to build PLplot as a static lib (which I normally do for my > app anyway). But then I started getting incompatible linkage warnings > and some errors about trying to initialize dllimport'ed data > (\plplot-plplot\bindings\qt_gui\plqt.cpp(28): error C2491: 'vectorize' : > definition of dllimport data not allowed). After finding/following > the thread here (http://ehc.ac/p/plplot/mailman/message/33603310/), I > began to suspect that the USINGDLL macro might be an issue. Despite > the fact that I configured PLplot for static build it seems that the > cmake scripts still applied USINGDLL to the plqt.c file. Is that > expected (I don't totally understand the use of USINGDLL in all the > contexts)? Is it perhaps related to the issue described in that thread on the devel list? Are you using PLplot-5.10.0 or the git master tip version (which is about to turn into PLplot-5.11.0)? I would prefer you to try the master tip version if you haven't been doing that already because it has been a very long time since 5.10.0 was released, I am much more familiar with the master tip version, and I would like to get the master tip version tested as well as possible before the 5.11.0 release. For example, if you spot a USINGDLL issue for that version (such as USINGDLL being defined for the static library case), please let me know with lots of details. 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 __________________________ |