Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <3AE9ECA4.F9B2C8EC@ece.gatech.edu> Date: Fri, 27 Apr 2001 18:03:16 -0400 From: "Charles S. Wilson" X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: "Larry Hall (RFK Partners, Inc)" CC: Jim Hall , cygwin AT cygwin DOT com Subject: Building PERL modules [Was: Re: Any resolution to win32.h problem?] References: <4 DOT 3 DOT 1 DOT 2 DOT 20010427161533 DOT 0261b938 AT pop DOT ma DOT ultranet DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Larry Hall (RFK Partners, Inc)" wrote: > I know nothing about building Perl modules but for me, it stands to reason > that you need a Perl development environment to do so. This would be the > Perl source. I'm sure others on this list that are more Perl savy can > confirm or deny this but in the interim, you might want to try it out. It > will probably save you some time. No, you should be able to build perl modules using just the perl binary, assuming you have the same version of gcc installed, in the same location, as was used to build perl.exe. Perl ordinarily includes all of the necessary perl-specific headers and object files within its /usr/lib/perl5//* tree Since the versions of gcc usually installed on cygwin systems are typically "similar enough" and "always" go in the same locations, there should be no problem building perl modules. (famous last words...) And, FWIW, "win32.h" is a file within the perl source dist and should only be used for native windows builds of perl, not for cygwin. It is NOT a part of the "normal" windows API. --Chuck -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple