From: Thomas S. <th...@ws...> - 2009-03-04 20:06:07
|
Thomas Stover wrote: > Andrew Ross wrote: >> Agh! I think the problem might be that the .rc files are blank. >> Just as a test could you try addding the following to cairo.rc >> (include only the lines referring to the drivers you have) >> >> xcairo:Cairo X Windows Driver:1:cairo:59:xcairo >> pdfcairo:Cairo PDF Driver:0:cairo:60:pdfcairo >> pscairo:Cairo PS Driver:0:cairo:61:pscairo >> svgcairo:Cairo SVG Driver:0:cairo:62:svgcairo >> pngcairo:Cairo PNG Driver:0:cairo:63:pngcairo >> >> Also might be useful to add the following to ps.rc (this driver >> will work without any external libraries so is a good test). >> >> ps:PostScript File (monochrome):0:ps:29:psm >> psc:PostScript File (color):0:ps:30:psc >> >> Then repeat your above tests. >> >> Any difference? >> >> Andrew >> > > After adding the .fnt file over to that directory as well. The ps and > color ps work fine. (I did actually look at the output to make sure.) > The cairo stuff fails gracefully like this: > Plotting Options: > < 1> ps PostScript File (monochrome) > < 2> psc PostScript File (color) > < 3> pngcairo Cairo PNG Driver > < 4> extcairo Cairo External Context Driver > > Enter device number or keyword: 3 > Unable to load driver: cairo. > > *** PLPLOT ERROR, IMMEDIATE EXIT *** > Unable to load driver > Program aborted > > I'll try rebuild to make sure. Is there any debug flags or anything > you want me to try and get some more verbose info with? > Correction: the cairo stuff works fine! I busted out the trusty dependency walker program and realized I had a few missing dlls. I would have noticed this before, but I have this thing about wanting to know what files are need to do what. Next up win64 tests... |