On 2011-06-17 11:59+0100 Richard Jackson wrote:

> The difference is the -s option which removes all symbol table and
> relocation information from the executable. In Netbeans I then built the
> Debug version and it crashes just like the QtCreator version. Looking back
> at my main application, I was building the debug version there too, so I
> changed to build a release version and it all runs! I have a feeling it
> would also run with Qt 4.7.3 linked with Plplot compiled with gcc 4.4.4. One
> question, does the Plplot build include debug symbols and if so, can I
> disable it somehow?

What you said reminded me that the Qt set of libraries comes in two
flavours, "release" and "debug".  I am not sure anybody here has
actually tried this with PLplot, but from skimming through the CMake
documentation related to Qt4, it appears to me there is full support
for choosing one of those flavours.  In particular, I suggest you try
using the -DCMAKE_BUILD_TYPE:STRING=Debug cmake option if you want to
use the debug flavour of Qt libraries for PLplot linking and don't
specify that option (which is what you have doing so far) if you want
to use the release flavour of the Qt libraries for PLplot linking.

N.B. You should use the results of the "make VERBOSE=1" command to see
the differences in linking between those two cases.

Note, if PLplot is linked with the release flavour of Qt (the current
status of your PLplot builds, I believe), then it would be necessary
to link your own application with that flavour of Qt, and similarly if
PLplot is linked with the debug flavour of Qt (using the cmake
-DCMAKE_BUILD_TYPE:STRING=Debug option), then your own application
should be linked the same way.  I believe this consistency in Qt
flavour is necessary because different compiler optimizations are used
for the two cases which are likely incompatible with each other.  So
there is a lot more involved then whether symbols are stripped or not
for the two cases.

By the way, aside from the QSAS team (which apparently use their own
independent build methods rather than our CMake-based build system),
you are our first user to attempt to use the Qt parts of PLplot within
their own independent Qt application. Thus, we are all learning this
Qt-related CMake-based build system stuff together which is why some
experimentation is needed (e.g., trying the
-DCMAKE_BUILD_TYPE:STRING=Debug cmake option) to figure out how to get
this all to work for your type of use case.

I very much appreciate the patience you have shown in trying out these
various experiments, and I am sure we can resolve all the issues you
have found if we keep persisting.

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); PLplot scientific plotting software
package (plplot.org); 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
__________________________

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to