Hi Thomas, > By any chance is a cross compile from linux to win32 or win64 supported? > Just for C that is. I'm all thumbs with cmake. If this has not been done > before, I'll be glad to test it, if someone can give me some clue how to > start. For instance I have a home built cross mingw tool chain at > /opt/crosscompilers/win32/bin/i686-mingw32-X (where is X is gcc, ar, > ranlib, etc) with a pkg-config file directory for the win32 cairo and > such at /opt/crosscompilers/win32/mingw/lib/pkgconfig. I also have a > similar working win64 tool chain. (this is rapidly becoming my exclusive > approach to windows development btw) > There are some discussions about cross compiling in the cmake mailing list (archive: http://www.mail-archive.com/[email protected]/). AFAIR, cmake doesn't support it by default, but it is possible. > Before I go to that though, the more relevant question would be will > "extcairo" work on windows? > I've never test extcairo, but the other cairo devices (pdfcairo, svgcairo, ...) work on Windows when using gtk for Windows. So I assume extcairo will work as well. Keep us informed, since this would be interesting.
Regards, Werner > Alan W. Irwin wrote: > >> On 2009-02-25 18:22-0600 Thomas Stover wrote: >> >> >>> Hi, I just signed up to the list, so my apologies if my post is >>> completely out of whack. >>> >>> -Firstly the documentation (wiki & INSTALL) use a file named >>> plplot_cmake. This file is not present in either 5.9.2 source tree nor >>> the current svn trunk. >>> >> The documentation did attempt to discuss the "plplot_cmake" name used >> in the >> example, but it was a bit confusing so I have just changed those >> remarks to >> the following: >> >> Note in the above example an initially empty build directory >> (arbitrarily) >> named build_dir is used to insure a clean start, and ../plplot_cmake >> is the >> (arbitrary) name of the top-level directory of a freshly checked out >> source >> tree from our svn repository. If instead you use a freshly unpacked >> PLplot >> source distribution tarball "../plplot_cmake" will need to be replaced by >> "../plplot-5.9.2" (for our latest release at time of writing). >> >> I hope that clears it up for you. For a svn checkout the name of the top >> level directory is anything you want to specify. That's not true of >> an unpacked source distribution tarball (although you could mv the >> resulting >> plplot-$version directory to any arbitrary name as well). >> >> >>> -After running cmake in "build_dir" the makefile is created in '../' >>> (the source dir) instead of './'. Moving on.. >>> >> That only happens if you have attempted to build in the top-level >> source-tree directory before. Try pristine source (freshly checked >> out from >> svn or freshly unpacked from a tarball), then try to build from a >> separate >> initially empty build_directory. All the build action is in the build >> tree >> and the source-tree should have no files written into it at all (which >> is a >> very nice property to have). >> >> >>> My real question is that there appears to be no way to tell cmake what >>> my cairo and pangocairo build flags need to be, resulting in predictable >>> errors such as: >>> ...plplot-5.9.2/drivers/cairo.c:33:19: error: cairo.h: No such file or >>> directory >>> ...plplot-5.9.2/drivers/cairo.c:34:30: error: pango/pangocairo.h: No >>> such file or directory >>> >>> Of course what is missing is these calls somewhere: >>> >>> $ pkg-config --cflags --libs cairo >>> $ pkg-config --cflags --libs pangocairo >>> >>> Any help pointing me in the right direction would be much appreciated. >>> >> Our build system (implicitly) uses pkg-config (from within CMake) to find >> what you need to know about building against cairo. If you have >> installed a >> development version of pangocairo and cairo in a standard location, then >> CMake will find it using a standard pkg-config call. From your cmake >> output >> it looks to me like pango was actually found okay. >> >> >>> Here is my cmake line: >>> >>> cmake -DCMAKE_INSTALL_PREFIX=/home/thomas/ -DPLD_extcairo=ON >>> -DENABLE_f77=OFF -DENABLE_wxwidgets=OFF -DENABLE_cxx=OFF >>> -DENABLE_python=OFF -DCMAKE_C_FLAGS=-O2 -DPLD_pscairo=OFF >>> -DPLD_pdfcairo=OFF -DPLD_pngcairo=OFF -DPLD_xcairo=OFF >>> -DPLD_svgcairo=OFF -DPLD_memcairo=OFF -DPLD_png=OFF -DPLD_jpeg=OFF >>> -DPLD_gif=OFF -DPLD_hp7470=OFF -DPLD_hp7580=OFF -DPLD_lj_hpgl=OFF >>> -DPLD_xterm=OFF -DPLD_tek4010=OFF -DPLD_4010f=OFF -DPLD_tek4107=OFF >>> -DPLD_tek4107f=OFF -DPLD_mskermit=OFF -DPLD_versaterm=OFF -DPLD_vlt=OFF >>> -DPLD_conex=OFF -DPLD_aqt=OFF -DPLD_cgm=OFF -DPLD_dg300=OFF >>> -DPLD_gcw=OFF -DPLD_imp=OFF -DPLD_linuxvga=OFF -DPLD_ljii=OFF >>> -DPLD_ljiip=OFF -DPLD_mem=OFF -DPLD_ntk=OFF -DPLD_null=OFF -DPLD_pbm=OFF >>> -DPLD_pdf=OFF -DPLD_plmeta=OFF -DPLD_ps=OFF -DPLD_pstex=OFF >>> -DPLD_psttf=OFF -DPLD_svg=OFF -DPLD_tk=OFF -DPLD_tkwin=OFF >>> -DPLD_wingcc=OFF -DPLD_wxwidgets=OFF -DPLD_xfig=OFF -DPLD_xwin=OFF >>> ../CMakeLists.txt >& cmake.out >>> >> There is a much easier way to turn everything off except the core library >> build and anything else you specify. For example, >> >> cmake -DCMAKE_INSTALL_PREFIX=/home/thomas -DDEFAULT_NO_DEVICES=ON >> -DDEFAULT_NO_BINDINGS=ON -DPLD_pscairo=ON ../path_to_source_tree >> >> Gives you a PLplot build with just a core library and the Cairo >> PostScript >> device, but that is all. >> >> From your cmake output and the above commands you appeared to turn >> everything off except the extcairo device. I am not sure how well that >> works (or whether you have to do something extra to make it work). It is >> disabled by default so I have never tried it myself. Therefore, I suggest >> you build one of the other cairo devices as well to make sure you have a >> device that is known to work (any of pdfcairo, pngcairo, pscairo, >> svgcairo, >> or xcairo should work well). >> >> Thanks for your interest in PLplot. >> >> 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 >> __________________________ >> > > > -- Dr. Werner Smekal Institut fuer Allgemeine Physik Technische Universitaet Wien Wiedner Hauptstr 8-10 A-1040 Wien Austria DVR-Nr: 0005886 email: [email protected] web: http://www.iap.tuwien.ac.at/~smekal phone: +43-(0)1-58801-13463 (office) +43-(0)1-58801-13469 (laboratory) fax: +43-(0)1-58801-13499 ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Plplot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/plplot-devel
