Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: <421FA54D.6090903@x-ray.at> Date: Fri, 25 Feb 2005 23:23:09 +0100 From: Reini Urban User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.7.5) Gecko/20041217 MIME-Version: 1.0 To: cygwin AT cygwin DOT com CC: Linda W Subject: Re: perl & Win32 lib support References: <4208270D DOT 4080801 AT tlinx DOT org> <20050208063149 DOT GB3096 AT efn DOT org> <42091B63 DOT 1080908 AT tlinx DOT org> <20050208234325 DOT GA2944 AT efn DOT org> <420AAF5E DOT 1030506 AT tlinx DOT org> <420AB5EC DOT 1070904 AT familiehaase DOT de> <420BB627 DOT 7040905 AT tlinx DOT org> <20050210200410 DOT GA3728 AT efn DOT org> <420BEEB6 DOT 3070303 AT x-ray DOT at> <421CCF9A DOT 5010202 AT tlinx DOT org> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Igor Pechtchanski schrieb: > On Wed, 23 Feb 2005, Linda W wrote: >>Not knowing the exact order of how things are released, does announcing >>it on "cygwin-apps" mean that it will be available via setup soon? > > Announcing something on cygwin-apps means that the other maintainers will > look at it if necessary, and that someone with access will eventually > upload it to sourceware.org. Once that happens, the package will be > announced on cygwin-announce, and *that* does mean that it'll be available > via setup soon. :-) You can point setup to http://xarch.tu-graz.ac.at/publ/cygwin/ [Add URL] and install the unsupported and unannounced perl-libwin32 package also. >>When it is, does that mean we should be able to build perl modules/utils >>that inter-operate with the native Win32 interface? > I'll let Reini answer this one. No. To enable building for perl modules/utils that inter-operate with the native Win32 interface you just need the exact c/c++ compiler the cygwin perl was compiled with (see the perl cygwin README), plus gnu make and coreutils of course, plus the dependent packages. If some packages are dependent on some libwin32 package (libwin32 is just a bundle of useful Win32 packages) then you need the perl-libwin32 cygwin package, because building them by your own via CPAN is quite hard. In the next future the libwin32 team will try to incoorporate the current huge cygwin patch into each module step by step. Until this will be done, you'll have to live with the (yet unreleased) cygwin package. Of course building any Win32 package with gcc, which is not supported for cygwin nor mingw, is quite hard, since some Win32 package authors just assume that there only exist ActiveState perl (and MSVC / nmake). And don't accept patches for cygwin/mingw. -- 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/