This is the mail archive of the
mailing list for the Cygwin project.
Re: Avail for test: tiff-3.5.7-1
- From: Charles Wilson <cwilson at ece dot gatech dot edu>
- To: Charles Wilson <cwilson at ece dot gatech dot edu>
- Cc: cygwin at cygwin dot com
- Date: Fri, 15 Feb 2002 20:14:50 -0500
- Subject: Re: Avail for test: tiff-3.5.7-1
- References: <3C66F5A0.email@example.com>
Any objections if I remove the 'test' status on this release? Has
anybody experienced a regression failure? (Has anybody even tested it?)
Charles Wilson wrote:
> TEST RELEASE. PLEASE test to see that this DLL doesn't break your
> existing tiff-dependent applications (without recompiling your
> apps). It *should be* backwards compatible, but we've had problems
> with libtiff before. I want to be sure...
> Also, there are a few exported variables that are "bad" -- in the
> sense that they cannot be auto-imported (arrays of structs, etc).
> However, these are library private and should NOT be accessed by
> external programs. If you find a rogue program out there that
> messes with these internal data objects, let me know...
> The tiff package has been updated to version 3.5.7-1. It is based
> on the official tiff-v3.5.7.tar.gz distribution, and provides a
> library and utility routines for manipulating tiff files and images.
> CHANGES: (vs. 3.5.6beta-2)
> 1. Internal changes to facilitate easier building/maintainance
> 2. tiff is now built using the 'auto-import' features of
> recent binutils.
> 3. update to the official 3.5.7 release
> 4. install "private" headers so that libgeotiff can be compiled
> 5. the -src package is much larger now because it contains the
> test images needed so that 'make check' works.
> Charles Wilson
> tiff volunteer maintainer for cygwin
> To update your installation, click on the "Install Cygwin now" link on
> the http://sources.redhat.com/cygwin web page. This downloads setup.exe
> to your system.
> Run setup and answer all of the questions. You must choose a
> mirror, since direct downloads from 'cygwin.com' are no longer
> ftp://mirrors.rcn.net/pub/sourceware/cygwin/ (US)
> ftp://linux.sarang.net/mirror/development/compiler/cygwin/ (Korea)
> ftp://ftp.mirror.ac.uk/sites/sourceware.cygnus.com/pub/cygwin (UK)
> The setup.exe program will figure out what needs to be updated on your
> system and should install the tiff package automatically. To install
> this TEST version of tiff you'll have to select the experimental radio
> button in setup.
> If you have questions or comments, please send them to the Cygwin
> mailing list at: firstname.lastname@example.org . I would appreciate if you
> would use this mailing list rather than emailing me directly. This
> includes ideas and comments about the setup utility or Cygwin general.
> If you want to make a point or ask a question the Cygwin mailing list is
> the appropriate place.
> *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
> If you want to unsubscribe to the cygwin-announce mailing list, look at
> the "List-Unsubscribe: " tag in the email header of this message. Send
> email to the address specified there. It will be in the format:
> o Now uses the auto-import functionality of newer binutils, and
> doesn't use __declspec(dllimport). This means you no longer need
> "-DTIFF_STATIC -DJPEG_STATIC -DZLIB_STATIC" or even -DALL_STATIC
> when compiling objects intended for static linking. Just compile
> as normal. HOWEVER, you need to use a special flags when linking
> statically: 'gcc -static'. For dynamic linking, you need no special
> link-time flags (assuming you're using binutils newer than 20011002,
> when --enable-auto-import was made the default).
> -- PRO: no compile time flags needed when building
> client programs; ONLY need a link-time flag
> linking to static libraries. NO special flags
> at compile-time nor link-time when linking to
> dynamic links.
> -- CON: (partial): if using binutils older than 20010930,
> you now need a special linktime flag for dynamic
> linking (-Wl,--enable-auto-import). However,
> with an up-to-date binutils, you don't need this.
> o Depends on zlib-1.1.3-7 and jpeg-6b-7 packages; please install those
> packages as well.
> o As of v3.5.3, libtiff no longer includes support for LZW-compressed
> images, due to Unisys' recent activities enforcing their patent. While
> the source archive contains the official 're-enable LZW support' patch,
> it is NOT applied to the source archive and the files in the binary
> package do NOT include that functionality. If you want it, you have to
> build it yourself (although the README file in
> /usr/doc/Cygwin/tiff-3.5.7.README contains step-by-step instructions
> for doing this, intended for *authorized users* only -- e.g. those
> outside of the US patent jurisdiction, or who have purchased
> a license from Unisys.)
> o Includes several utilities for manipulating tiff files. The binary
> package includes dynamically linked versions of these utilities,
> although the build process will make both dynamically and statically
> linked versions.
> o Building the package from source requires gcc-2.95.3-5 and
> binutils-20011002-1 or later
> o If you are building a package that depends on libjpeg, and you wish to
> link *statically*, just use 'gcc -static' when linking your package.
> There no need to -Ddefine anything special when compiling your object
> o No special -Ddefine options or link options are needed when building a
> package that depends on libjpeg and you want to link dynamically
> o The following packages have been converted from old style
> "-DFOO_STATIC" to the new autoimport style of DLL structure:
> ncurses readline gettext zlib tiff
> libpng xpm-nox jpeg jbig
> The following have not (yet) been converted, and still need
> -DFOO_STATIC for static builds:
> bzip2 gdbm
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html