Mailing-List: contact cygwin-announce-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-announce-owner AT cygwin DOT com Reply-To: The Cygwin Mailing List Delivered-To: mailing list cygwin-announce AT cygwin DOT com Delivered-To: moderator for cygwin-announce AT cygwin DOT com Message-ID: <3F5575FA.7080001@ece.gatech.edu> Date: Wed, 03 Sep 2003 01:02:50 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cygwin-announce AT cygwin DOT com Subject: Updated: ncurses, libncurses7, libncurses-devel, ncurses-demo -5.3-4 [Requires cygwin-1.5.3+] Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit ncurses is a package that provides character and terminal handling libraries, including 'gui-like' panels and menus. It is often used instead of termcap. This release is built against the cygwin-1.5.x kernel; it will not work with 1.3.22. CHANGES * compiled against the 1.5.2 kernel * minor bugfix to the postinstall script * Fixed a number of minor packaging errors (all readmes +were+ in ncurses- and not split among the tarballs as the were intended) * updated to a recent (20030802) official patchlevel -- most of the earlier cygwin-specific patches have been folded in to those official patchlevels. However... * Added a lot of support for building shared libs using libtool ( !!!! THANK YOU Nicholas Wourms !!!! ). Unfortunately, I was not able to actually RELEASE the libtool-built ncurses, for the reasons detailed in the NOTES section, below. -- Charles Wilson ncurses volunteer maintainer for cygwin To update your installation, click on the "Install Cygwin now" link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Then, run setup and answer all of the questions. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from 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: cygwin-announce-unsubscribe-you=yourdomain DOT com AT cygwin DOT com If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at the above URL. ------------------------------------------------------- NOTES: * Added a lot of support for building shared libs using libtool ( !!!! THANK YOU Nicholas Wourms !!!! ). Unfortunately, I was not able to actually RELEASE the libtool-built ncurses, for the reasons detailed below: 1) Requires Yet Another DLL rename. cygncurses7.dll --> cygncurses-5.dll (or some other number; the ncurses maintainer does not use the same variable to set DLL versions when building non-libtool and when building libtool). But simply the '-' is problematic, even if I make both numerals '7'. Libtool insists on the '-'. So, I figured I'd spare everybody another version split -- especially as so many packages which depend on ncurses have just been rebuilt against 5.3-4/1.5.3+; to bump the version again so soon would require all of those to be rebuilt, which is really unnecessary at this time. 2) The libtool wrapper I released recently (with the "WANT_LIBTOOL_VER" environment variable) are *almost* right. But not quite. So, I need to release another set of wrappers before using them to build one of my maintained packages. 3) libtool itself has a bug with multilanguage support and relinking. The '--tag=' is required...but libtool doesn't store the tag info in the uninstalled .la file. So, when installing, libtool tries to relink the shared library, but without the --tag=CXX flag. This, of course, fails. I've reported this to the libtool developers, and provided a simpler testcase, but no joy yet. So, *EVENTUALLY* I'll move ncurses to use libtool, but not just yet. However, my investigations led to a whole new set of patches, derived from Nicholas's contributions, that should -- once libtool-wrapper and libtool itself are fixed -- allow an immediate and painless (for me, ?) switchover to libtool-based builds.