Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <427B3AF0.1000807@x-ray.at> Date: Fri, 06 May 2005 11:37:52 +0200 From: Reini Urban User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.8b) Gecko/20050217 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Using -mno-cygwin flag References: <20050504091922.GD7475@monster.octa4.net> <42789D45.6F74436D@dessent.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Sam Steingold schrieb: >>* Brian Dessent [2005-05-04 03:00:37 -0700]: >>-mno-cygwin does not just "make things that doesn't depend on the >>cygwin DLL", it removes Cygwin from the equation entirely. > > this is very unfortunate, actually. > things like berkeley-db, postgresql, pcre &c all have a native win32 > port, and it it a pity that -mno-cygwin does not use them. You have to talk to them how they reached their goal. PostgresQL for example had to reinvent a fair certain percentage of IPC and filesystem stuff from cygwin only for their native Win32 port. To support POSIX unlink(), symlink(), and IPC without cygwin caused major troubles. select() and threads may have advantages in the win32 world, but then you have to re-invent the wheel. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ http://phpwiki.org/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/