From: Arjen M. <arj...@de...> - 2010-11-08 08:12:20
|
Hi Alan, Linda, I will have a look at this. I never heard of "Philrosenberg" either, but indeed, the best if not the only way to do multiple builds is by resevering separate directories for them. This may not be the common way of working with Visual Studio, as that creates subdirectories for each configuration in the directory containing the project files, but in my experience with PLplot and CMake it is much easier to keep track of things - if only that is easier to delete a complete directory and its contents than to remove all the subdirectories one by one. The first messages about the manifest file are suspicious - they may have resulted in the access violation, as at run-time the manifest information is queried. What happens if you simply do: cmake "plplot dir" -G "Visual Studio 9 2008" -DBUILD_TEST=ON (replacing "plplot dir" with the directory where you have put the PLplot sources)? Regards, Arjen On 2010-11-06 22:38, Alan W. Irwin wrote: > On 2010-11-06 01:04-0000 Linda Rawson wrote: > >> I tried the instructions here -> >> >> http://www.miscdebris.net/plplot_wiki/index.php?title=Configure_PLplot_for_Visual_CXX > > Those instructions have apparently been heavily edited by somebody > called Philrosenberg who I have never heard of. I don't have access > to Windows, but I know enough from the Linux side of things that I can > well believe those directions don't work. > > Why all these complications with all combinations of > -DCMAKE_BUILD_TYPE=Release, -DCMAKE_BUILD_TYPE=Debug, > -DBUILD_SHARED_LIBS=ON, and -DBUILD_SHARED_LIBS=OFF? On Linux, I > leave CMAKE_BUILD_TYPE unspecified, and also take the default > BUILD_SHARED_LIBS=ON. I suspect that one combination will work well > for you. However, if you absolutely need to build four versions > of PLplot with the four configuration combinations > > -DCMAKE_BUILD_TYPE=Release -DBUILD_SHARED_LIBS=ON > > -DCMAKE_BUILD_TYPE=Release -DBUILD_SHARED_LIBS=OFF > > -DCMAKE_BUILD_TYPE=Debug -DBUILD_SHARED_LIBS=ON > > -DCMAKE_BUILD_TYPE=Debug -DBUILD_SHARED_LIBS=OFF > > then the four builds should be absolutely independent of each other. > That is use a separate initially empty build directory for each one, > and use a separate install tree for each one. Mixing various > configurations together in the same build tree like he recommends is a > recipe for disaster! > > Could one of our Windows developers edit that page into a form that is > much more likely to work? > > 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 > __________________________ > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev > _______________________________________________ > Plplot-general mailing list > Plp...@li... > https://lists.sourceforge.net/lists/listinfo/plplot-general > DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail. |