I have now built Plplot using cygwin. The cairo dirvers show up. I think the problem was resolved by disabling other things on my system, mainly Mingw (Fortran Tools), but also Absoft, Intel, and G95 Fortran compilers. I don't know how to use the cairo driver, but will work on that.
I don't think this helps me build Plplot for inclusion in the Fortran
Tools because the FT do not include cygwin (just Mingw). So I
am trying to attach all the stuff requested. I don't think this is a
bug report, just a problem trying to get everything set up OK.
The command to build is:
C:\"Program Files (x86)"\"CMake 2.8"\bin\cmake -G "MinGW Makefiles"
-DDEFAULT_NO_BINDINGS=ON -DENABLE_f95=ON
-DENABLE_DYNDRIVERS=ON -DCMAKE
INSTALL_PREFIX=install .. 1>cmake.out 2>cmake.err
all one line, of course. The files cmake.??? are in the tar ball attached.
Also the output from make.
The lines that say that pango and cairo can't be found (after finding
them--see cmake.out) surely are suspicious. Here is a bit more about
that checking on what Darius said:
C:\walt>echo %PKG_CONFIG_PATH%
C:\FortranTools\gtk\lib\pkgconfig
C:\walt>dir C:\FortranTools\gtk\lib\pkgconfig\pango*
Volume in drive C has no label.
Volume Serial Number is BADA-0412
Directory of C:\FortranTools\gtk\lib\pkgconfig
04/20/2013 05:24 AM 330 pango.pc
04/20/2013 05:24 AM 283 pangocairo.pc
04/20/2013 05:24 AM 303 pangoft2.pc
04/20/2013 05:24 AM 263 pangowin32.pc
4 File(s) 1,179 bytes
0 Dir(s) 37,579,841,536 bytes free
C:\walt>dir C:\FortranTools\gtk\lib\pkgconfig\cairo*
Volume in drive C has no label.
Volume Serial Number is BADA-0412
Directory of C:\FortranTools\gtk\lib\pkgconfig
04/20/2013 05:14 AM 262 cairo-fc.pc
04/20/2013 05:14 AM 259 cairo-ft.pc
04/20/2013 05:14 AM 288 cairo-gobject.pc
04/20/2013 05:14 AM 242 cairo-pdf.pc
04/20/2013 05:14 AM 239 cairo-png.pc
04/20/2013 05:14 AM 248 cairo-ps.pc
04/20/2013 05:14 AM 239 cairo-svg.pc
04/20/2013 05:14 AM 257 cairo-win32-font.pc
04/20/2013 05:14 AM 255 cairo-win32.pc
04/20/2013 05:14 AM 374 cairo.pc
10 File(s) 2,663 bytes
0 Dir(s) 37,578,792,960 bytes free
so there is all kinds of cairo and pango stuff there. And
the following also seems to work . . .
C:\walt>pkg-config --libs pango
-LC:/FortranTools/gtk/lib -lpango-1.0 -lm -lgobject-2.0 -lglib-2.0 -lintl
C:\walt>pkg-config --libs cairo
-LC:/FortranTools/gtk/lib -lcairo
and gtk-demo works OK.
Files printenv.out, cmake.out, cmake.err,
make.out, and make.err (empty) are attached
in walt.tar.gz. Rename it from walt_tar_gz.
Thanks for looking at this. Let me know if you
need anything else.
On Sun, May 4, 2014 at 11:33 AM, Alan W. Irwin <ir...@beluga.phys.uvic.ca>wrote:
> On 2014-05-04 09:12-0700 Walt Brainerd wrote:
>
> Alan: do you really want to look at the results
>> of my build attempts? It seems quite obvious that
>> there is something "wrong" with my system
>> configuration or the way I am trying to do things.
>>
>
> Yes, please. Often the PLplot build problem is something really simple,
> but we
> cannot help you figure that out without comprehensive information from
> you containing all the details. Only some of those details will be
> relevant, but we don't know which until we see all of them. Without
> such comprehensive details, we speculate as to what the issue is, you
> respond, we speculate again, etc., and those iterations consume
> a lot of time for both parties.
>
> So here is the comprehensive information that I would really like to
> see in a typical bug report from you and others here so that we have a
> good chance to help you while minimizing iterations.
>
> 1. List all environment variables. (This is important since some of
> those environment variables affect cmake's operation.) On Unix or if
> you have MSYS installed this can be done with
>
> printenv >printenv.out
>
> but otherwise, output any PATH, CMAKE_LIBRARY_PATH,
> CMAKE_INCLUDE_PATH, PKG_CONFIG_PATH, CC, CXX, FC, CFLAGS, CXXFLAGS, and
> FFLAGS
> environment variables you have set to a file, and include that file in
> your bug report.
>
> 2. Give the exact command you used to invoke cmake.
>
> 3. Give the output from that command captured, e.g., in the cmake.out file
> using
>
> cmake <whatever options> <source tree> >& cmake.out
>
> where <whatever options> and <source tree> are given in detail in 2.
>
> The above is a good way to capture stderr and stdout in a file
> simultaneously on Unix, Cygwin, or for MSYS, but I am sure there is also
> a way to capture stderr and stdout for a cl-based native Windows
> environment,
> but I don't know what that is.
>
> 4. Include the resulting CMakeCache.txt file (from the top directory in the
> build tree).
>
> 5. Give the exact build command you used (with VERBOSE=1 set)
>
> For example, on Unix, Cygwin, or MSYS that could be
>
> make VERBOSE=1 all >& all.out
>
> and on native Windows it would be
>
> nmake VERBOSE=1 all >& all.out
>
> (where ">&" stands symbolically for whatever means are necessary to
> capture stderr and stdout on Windows in the all.out file).
>
> 6. Give the output from the build command (e.g., all.out in the example
> just above).
>
> Then collect all these requested files in a compressed tarball and
> send it to this list along with the cmake and build command invocation
> information requested in 2 and 5.
>
> I hope these detailed instructions for reporting any PLplot build
> problems will be a help to you and everyone else on this list.
>
>
> 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); the Time
> Ephemerides project (timeephem.sf.net); PLplot scientific plotting
> software package (plplot.sf.net); 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
> __________________________
>
--
Walt Brainerd
walt_tar_gz
Description: Binary data
------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce
_______________________________________________ Plplot-general mailing list Plplot-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-general
