Re: What's in git.git

From: Junio C Hamano <junkio@cox.net>
Date: Aug 3, 2006, 09:16 UTC
Message-ID: <7vmzamqivk.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <81b0412b0608030109g6f49113ep5cf577475117469b@mail.gmail.com>

"Alex Riesen" <raa.lkml@gmail.com> writes:

Show 9 quoted lines

>> What's the standard workflow/procedure ActiveState users would
>> use to build and install .xs extensions?  Maybe they have their
>> own $(MAKE) equivalent that groks such a Makefile with
>> backslashed pathnames and CRLF endings?
>
> I don't know. It's a bit more than backslashes and CRLF. The pathnames
> must be _completely_ converted from windows to cygwin. Cygwin even
> provides an utility for that (cygpath). Besides, there still is that stupid
> case-sensitivity problem.

What I meant to say was that the real mistake might be for us to try using the Cygwin toolchain (GNU make, gcc and GNU C library) while working with ActiveState.

Now, I admit I know very little about ActiveState and know nothing about Windows build environment, but I would not be surprised if in ActiveState land there were a MakeMaker equivalent that spits out Makefile equivalent that is suitable for MS development environment, and the users are expected to work in that environment, perhaps using MS C compiler toolchain, to produce object files if they want to link with ActiveState stuff. If that were the case, maybe what is needed is to port the build infrastructure to MS development environment, and making Makefile generated from perl/Makefile.PL usable might not be of much use.