On 2011-06-20 11:34+0100 Richard Jackson wrote: > [...]So, the only way I can get a working application is with Qt 4.5.3 (Qt SDK > 2009.04) and its included compiler gcc 3.4.5 in Release mode. I am going to > have to return to that and adapt my application to suit. I did this, and > still my simple application does not run! What's different from Friday? I > still have the plplot build from Friday, checked the DLLs against my current > build and they are different sizes. Prepended Friday's dll folder to my path > so they will be used rather than my latest ones and I can now run OK. Double > checked, gcc -v reports version 3.4.5, the qt in my path is 2009.04. Rebuilt > without the install stage and that makes no difference. I wondered if I had > inadvertently left gcc 4.4.4 in my path when I built on Friday. Tried adding > it and rebuilding, but the DLLs are different sizes again, and it doesn't > run. > > So, now I am left in the situation that I have a working build of plplot > which runs with Qt 4.5.3 but I don't know how I did it and I can't recreate > it! I must be missing something obvious but I can't think what.
Because I have begun to test PLplot on Windows (and the wine version of Windows at that) only recently, I don't understand the details, and I may even have this wrong, but my understanding is the on Windows systems, CMake not only searches for system components via the PATH, but also via the registry. On wine I avoided all registry complications (I hope) when I installed Qt4 by installing it in a non-system location. Then I put qmake from that location on my PATH, and the result worked when I didn't have incompatible compilers. Anyhow, if you have several Qt versions on your system and one of those is in the registry, it is possible you are accessing the wrong version of qmake which then would pull in a Qt version that was different then the one you wanted. Because of this uncertainty, I suggest on systems with multiple Qt4 versions installed, you should always check your cmake output and your "make VERBOSE=1" output for everything qt related to make sure you are accessing the Qt4 header and library locations consistent with how you specified the qmake location with your PATH. I hope this fundamental check of cmake and make output will help you figure out how to replicate what you had before. You also mentioned having to invoke cmake twice when using -DTEST_DYNDRIVERS=OFF. That doesn't seem right so I will look into that. 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
