git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's in git.git

From
Alex Riesen <raa.lkml@gmail.com>
Date
Aug 3, 2006, 12:32 UTC
Message-ID
<81b0412b0608030532v4241322dted5f42baa196af88@mail.gmail.com>
In-Reply-To
<7vmzamqivk.fsf@assigned-by-dhcp.cox.net>
On 8/3/06, Junio C Hamano <junkio@cox.net> wrote:
Show 13 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.

Luckily, only ActiveState Perl users are hit. Which, I suppose, is not all that much (it's really crappy environment to work in, an only real stupid corporate users can keep doing that), and they're used to pain.

Show 6 quoted lines
> 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,

AFAICS, it is not suitable for anything: generated Makefile is not parsable by nmake(what MS thinks is a make) and is more like a broken gmake Makefile. Also -fno-strict-aliasing points at gcc.

Show 5 quoted lines
> 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.

I'd suggest to add NO_PERL_XS option to the top-level Makefile. Really core tools do not need Git.pm.

Previous: Junio C HamanoNext: Alex Riesen
Message 8 of 20 in “What's in git.git”
  1. Junio C HamanoAug 1, 2006
  2. Johannes SchindelinAug 2, 2006
  3. Junio C HamanoAug 2, 2006
  4. Alex RiesenAug 2, 2006
  5. Junio C HamanoAug 3, 2006
  6. Alex RiesenAug 3, 2006
  7. Junio C HamanoAug 3, 2006
  8. Alex RiesenAug 3, 2006
  9. Alex RiesenAug 3, 2006
  10. carbonated beverageAug 2, 2006
  11. Junio C HamanoAug 3, 2006
  12. A Large Angry SCMAug 3, 2006
  13. carbonated beverageAug 3, 2006
  14. carbonated beverageAug 3, 2006
  15. carbonated beverageAug 3, 2006
  16. carbonated beverageAug 3, 2006
  17. Junio C HamanoAug 3, 2006
  18. carbonated beverageAug 3, 2006
  19. carbonated beverageAug 3, 2006
  20. Jakub NarebskiAug 3, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.