public inbox for cygwin-announce@cygwin.com
 help / color / mirror / Atom feed
From: Bill Hoffman <bill.hoffman@kitware.com>
To: cygwin-announce@cygwin.com, cmake@public.kitware.com
Subject: Updated: CMake 2.6.4-1
Date: Fri, 22 May 2009 15:54:00 -0000	[thread overview]
Message-ID: <4A16B1E5.2080201@kitware.com> (raw)

CMake CMake 2.6.4-1  is now available on Cygwin mirrors.

If you have any problems or find any bugs, please report them at
www.cmake.org/Bug.

A full list of changes for the 2.6 release tree can be found here:

   http://www.cmake.org/files/v2.6/CMakeChangeLog-2.6.4

Some notable changes are:

- Fix broken OSXX11 CPack generator
- Fix #8843 ctest system information was not always correct on linux
- Fix transitive linking of imported libraries
- Fix CDash only submit with ctest_submit
- Fix scope issue with CMAKE_CURRENT_LIST_FILE  and macros
- Fix crash in include_directories #8704
- Do not warn if LIBPATH is not set for nmake
- No longer mark header files as HEADER_FILE_ONLY automatically,
   this gets rid of the ugly red marks in Visual Stuido
- Enforce unique binary directories
- Clarify docs of old *_OUTPUT_PATH vars
- Fix svn update logic for modified files
- Add get_filename_component(... REALPATH)



*** 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.com@cygwin.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 this URL.



Bill Hoffman
Cygwin CMake maintainer

                 reply	other threads:[~2009-05-22 15:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A16B1E5.2080201@kitware.com \
    --to=bill.hoffman@kitware.com \
    --cc=cmake@public.kitware.com \
    --cc=cygwin-announce@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).