Hi Jim: Glad you got the PLplot build to work on your particular windows platform. Arjen and Werner have managed to get shared libraries to work on their own windows platforms, but it sounds like a bit more effort will be required to get the same shared library success on your windows platform.
> I then proceeded to try cpack, and got an empty tar.gz file. I tried > cpack with a "-G ZIP" option with no luck either. I tried to use cpack > on a linux build (gcc) and at first it didn't work because it could not > set permissions in the install directory. A quick "sudo cpack" and I > got an empty tar.gz file. cpack needs to be set up properly to work, and that setup is normally done via cmake. See the last part of the top-level CMakeLists.txt file for the _cmake_ source. On Linux, at least, after the cmake command to configure cmake, and the make command to build it, I have confirmed that both "make package" and "make package_source" work. "make package" collects everything that would normally be installed in the install tree (i.e., a binary release) and puts it in a tarball instead. (cmake is set up to make several additional forms of binary release beyond just a tarball when you execute "make package". Those additional forms exist, but I haven't checked their contents.) "make package_source" collects everything in the source tree (except what you exclude with the CPACK_SOURCE_IGNORE_FILES variable) (i.e. a source release) and puts it into a tarball. Jim and Arjen and Werner, do the windows equivalent of "make package" and "make package_source" work for cmake itself on your various windows platforms? If you look in cmake/modules/plplot_version.cmake and the latter part of our top-level CMakeLists.txt file you will see the CPACK related variables we set our very similar to those that already work well for the _cmake_ source. In fact, "make package_source" already works well for us, but "make package" does not work for some reason and the resulting binary release tarball is empty (at least on Linux). I suspect it is some CPACK variable that still needs to be set, but I haven't spotted it yet when comparing with how cmake sets up "make package" for its own binary release(s). This is the "minor debugging" of the subject line, and I hope somebody else will take a look because I am just plain missing what the problem might be. 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 Yorick front-end to PLplot (yplot.sf.net); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
