All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Franke <Christian.Franke@t-online.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] make install on windows
Date: Sat, 28 Feb 2009 01:32:38 +0100	[thread overview]
Message-ID: <49A88626.4060904@t-online.de> (raw)
In-Reply-To: <5d3bb3090902260849k6e0e7550n918b07b144aaf7c5@mail.gmail.com>

Alexandre Bique wrote:
>   
>> Hi,
>>
>> On windows with cygwin or mingw, when i do make install, it installs
>> linux elf32 files instead of windows *.exe.
>>
>> Here is a patch to install the right file depending on $(EXEEXT).
>>
>> Thank you.
>>     
>
> Ooouuuppss, there is a little mistake : $(EXEXT) instead of $(EXEEXT).
> Take the new patch.
>
>   

> --- Makefile.in    (revision 2001)
> +++ Makefile.in    (working copy)
> @@ -222,14 +222,14 @@
>        $(INSTALL_DATA) $$dir$$file $(DESTDIR)$(pkgdatadir)/$$dest; \
>      done
>      $(mkinstalldirs) $(DESTDIR)$(bindir) $(DESTDIR)$(mandir)/man1
> -    @list='$(bin_UTILITIES)'; for file in $$list; do \
> +    @list='$(bin_UTILITIES:=$(EXEEXT))'; for file in $$list; do \
>        if test -f "$$file"; then dir=; else dir="$(srcdir)/"; fi; \
>        dest="`echo $$file | sed 's,.*/,,' | sed '$(transform)'`"; \

This is not necessary on Cygwin. Its /usr/bin/install handles the .exe 
issue itself, such that most existing Makefiles work OOTB.

Please make sure that /usr/bin/install and no other install is found in 
the PATH.

-- 
Christian Franke




  reply	other threads:[~2009-02-28  0:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-26 16:40 [PATCH] make install on windows Alexandre Bique
2009-02-26 16:49 ` Alexandre Bique
2009-02-28  0:32   ` Christian Franke [this message]
2009-02-28  0:38     ` Alexandre Bique

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49A88626.4060904@t-online.de \
    --to=christian.franke@t-online.de \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.