avr-libc-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [avr-libc-dev] pngtopnm


From: E. Weddington
Subject: Re: [avr-libc-dev] pngtopnm
Date: Fri, 08 Nov 2002 14:53:31 -0700

On 8 Nov 2002 at 22:12, Joerg Wunsch wrote:

> As E. Weddington wrote:
> 
> > I'm attempting to build avrlibc on a Cygwin platform.(ack!) The
> > build dies because it cand find pngtopnm. According to the search
> > that I've done, there is no win32 executable of pngtopnm (and its
> > inverse).
> 
> They belong to the popular netpbm graphics conversion program set.
> Since netpbm basically just converts files, it should be portable to
> any environment that conforms to ANSI/ISO C.
> 
> According to the FreeBSD port, netpbm sources should be found on
> the Sourceforge master sites.  You need the JPEG and PNG libraries
> installed in order to be able to convert from/to these formats.

Yeah, "should be portable", but I'm dealing with Windoze. I'm not 
about to go off and create a port of graphics software that's really 
just auxillary to get a compiler up and running. I barely have enough 
time to try to get a Win32 distro built (and especially before 
December ;-)).


> > Can an alternate solution be 
> > found for all platforms, without trying to create a win32 version of
> > pngtopnm?
> 
> Well, you can always pick the latest generated graphics files from
> some other source, like the official documentation on the Web page.
> They are just generated from the .fig (vector graphics) input files,
> so unless these input files are changed, the generated files will
> never be modified.
> 
> Do you have a ppmtogif tool for Win32?  

No. fig2dev came with ppm2pcx and gif2pnm. And cygwin came with 
ppm2tiff.

> If so, you can revert to
> GIF since your Win32 build has no restrictions unlike the nongnu.org
> servers that forbid to use it. ;-)  See the diffs between 1.23 and
> 1.24 of doc/api/Makefile.am, and 1.3 and 1.4 of doc/api/malloc.dox.
> Basically, by reverting them, you'll get it all in GIF.  You need to
> apply a similar patch for the doc/examples/demo part.

Why does the project have all these auxillary graphics conversions as 
part of its make in the first place?

Why does the .fig have to be a part of the source? Why not convert it 
to .png before adding it to CVS and leave out all this conversion in 
the make? You said "so unless these input files are changed, the 
generated files will never be modified." Will they ever be frequently 
modified enough to warrant this?

Thanks,
Eric






reply via email to

[Prev in Thread] Current Thread [Next in Thread]