On Thu, May 07, 2009 at 12:20:49PM -0700, Alan Irwin wrote: > On 2009-05-07 10:53+0100 Andrew Ross wrote: > >> >> Further to my previous report, this only seems to occur if you explicitly >> set the cmake build type, e.g. with -DCMAKE_BUILD_TYPE=Debug. This is >> probably why no-one has reported it before. Without this option the Qt >> library >> dependencies contain no type tags and so the problem does not occur. Not sure >> whether you would classify this as a cmake problem or a plplot problem. >> Either way it is irritating if you are trying to debug plplot problems. > > I confirm the issue for 2.6.0 so I assume it will appear for all 2.6.x. > What is going on is for -DCMAKE_BUILD_TYPE=Debug, FindQt4.cmake embeds the > debug, optimized, and general CMake keywords into the returned QT_LIBRARIES > list. Those keywords have a special meaning for the CMake > target_link_libraries command, but they screw up any other use of > QT_LIBRARIES such as my use of it to create plplotd-qt.pc. > > FindQt4.cmake isn't the only CMake find module that uses those keywords, but > I guess it's just the first one where PLplot has encountered the issue. So > what is needed is a general parsing routine to take just the debug, > optimized, or general part of LIBRARIES lists returned by Find modules that > is appropriate for the CMAKE_BUILD_TYPE. This should be fairly > straightforward, but still rather time-consuming to implement and test so I > suggest we put off implementing this LIBRARIES parsing routine until > post-release. > > For now, the safe thing to do is to avoid the use of -DCMAKE_BUILD_TYPE > (which as far as I know has never worked properly on Linux) and instead if > you want to debug just simply use the environment variable approach to > control your compile flags, e.g., > > export CC='gcc -g' > export CXX='g++ -g' > export FC='gfortran -g' > > I routinely use this approach (with the added -fvisibility=hidden flag), and > it works well.
You are probably right. What I don't understand is why it works with the general tag (which is there even if you don't specify a build type, but not with the optimized or debug tags. Andrew ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Plplot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/plplot-devel
