X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=3.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 Date: Thu, 3 Mar 2011 11:54:52 +0800 Message-ID: Subject: distributing executables for windows From: anctop To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com I'd like to ask a question about distributing programs compiled with cygwin to windows. I've compiled some utility programs (e.g. "grep") in the cygwin bash environment, then copied the executables and the dependent libraries (e.g. "grep.exe" and "cygwin1.dll", "cygintl-8.dll", "cygiconv-2.dll", "cyggcc_s-1.dll", "cygpcre-0.dll") back to windows. For those programs with only text outputs, this method gives a working windows port of the software, but it is not the case for those terminal handling programs (e.g. "less"). I can still compile and distribute, but the program works correctly only within the cygwin bash. Under windows, all the terminal capabilities are lost, with the "WARNING: terminal is not fully functional" message. I'm eager to know how to make the terminal features work in windows as well. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple