Eshell: Running GNU Make (Cygwin) on Windows 7

Eshell: Running GNU Make (Cygwin) on Windows 7

[William Crandall]

Hello,

Is there a "best" way to run Cygwin's GNU Make from Eshell
on Windows 7?

GNU Make 3.82.90 (Built for i686-pc-cygwin) runs fine in the
Cygwin shell, called from Cygwin's directory: /usr/bin/make

How would you call it from Eshell?

Thanks for any pointers!

-BC

Emacs: 24.1.50.1
Windows 7

Re: Eshell: Running GNU Make (Cygwin) on Windows 7

[William Crandall]

Dan Espen writes:

> Why Eshell?
>
> M-x compile
>
> --
> Dan Espen

Thanks Dan, but M-x compile gives me:

--------------------------------------------------
Compilation started at Thu Jun 07 18:51:13

make -k
'make' is not recognized as an internal or external command,
operable program or batch file.

Compilation exited abnormally with code 1 at Thu Jun 07 18:51:13
--------------------------------------------------

Cygwin 'make' works on Windows, in the Cygwin shell.

And I can do much of what I want in eshell, git, etc.
So it would be nice to be able to call Cygwin/make from there.

-BC


On Thu, Jun 7, 2012 at 5:10 PM, William Crandall <bc3141592@gmail.com> wrote:
> Hello,
>
> Is there a "best" way to run Cygwin's GNU Make from Eshell
> on Windows 7?
>
> GNU Make 3.82.90 (Built for i686-pc-cygwin) runs fine in the
> Cygwin shell, called from Cygwin's directory: /usr/bin/make
>
> How would you call it from Eshell?
>
> Thanks for any pointers!
>
> -BC
>
> Emacs: 24.1.50.1
> Windows 7

Re: Eshell: Running GNU Make (Cygwin) on Windows 7

[Eli Zaretskii]

> Date: Thu, 7 Jun 2012 18:59:58 -0700
> From: William Crandall <bc3141592@gmail.com>
> 
> Dan Espen writes:
> 
> > Why Eshell?
> >
> > M-x compile
> >
> > --
> > Dan Espen
> 
> Thanks Dan, but M-x compile gives me:
> 
> --------------------------------------------------
> Compilation started at Thu Jun 07 18:51:13
> 
> make -k
> 'make' is not recognized as an internal or external command,
> operable program or batch file.
> 
> Compilation exited abnormally with code 1 at Thu Jun 07 18:51:13
> --------------------------------------------------
> 
> Cygwin 'make' works on Windows, in the Cygwin shell.

That's your problem, right there: you haven't set the Windows PATH to
find the Cygwin 'make'.  The directory /usr/bin/ doesn't really exist
on your filesystem, as far as Windows is concerned, it is an illusion
created by Cygwin.  Find its real name (something like
C:\Cygwin\usr\bin perhaps?) and add it to the Windows PATH.  Then you
will be able to call it from "M-x compile" and from Eshell alike.

Alternatively, install the Cygwin build of Emacs, which will find
'make' like the Cygwin shell does.

IOW, mixing Cygwin and native Windows tools needs extra work.

Re: Eshell: Running GNU Make (Cygwin) on Windows 7

[William Crandall]

Thank Eli!

That's it exactly.
I added the real directory to PATH and we're right as rain.

Thanks again,

-BC


Eli Zaretskii writes:

> That's your problem, right there: you haven't set the Windows PATH
> to find the Cygwin 'make'.  The directory /usr/bin/ doesn't really
> exist on your filesystem, as far as Windows is concerned, it is an
> illusion created by Cygwin.  Find its real name (something like
> C:\Cygwin\usr\bin perhaps?) and add it to the Windows PATH.  Then
> you will be able to call it from "M-x compile" and from Eshell
> alike.
>
> Alternatively, install the Cygwin build of Emacs, which will find
> 'make' like the Cygwin shell does.
>
> IOW, mixing Cygwin and native Windows tools needs extra work.


On Thu, Jun 7, 2012 at 6:59 PM, William Crandall <bc3141592@gmail.com> wrote:
> Dan Espen writes:
>
>> Why Eshell?
>>
>> M-x compile
>>
>> --
>> Dan Espen
>
> Thanks Dan, but M-x compile gives me:
>
> --------------------------------------------------
> Compilation started at Thu Jun 07 18:51:13
>
> make -k
> 'make' is not recognized as an internal or external command,
> operable program or batch file.
>
> Compilation exited abnormally with code 1 at Thu Jun 07 18:51:13
> --------------------------------------------------
>
> Cygwin 'make' works on Windows, in the Cygwin shell.
>
> And I can do much of what I want in eshell, git, etc.
> So it would be nice to be able to call Cygwin/make from there.
>
> -BC
>
>
> On Thu, Jun 7, 2012 at 5:10 PM, William Crandall <bc3141592@gmail.com> wrote:
>> Hello,
>>
>> Is there a "best" way to run Cygwin's GNU Make from Eshell
>> on Windows 7?
>>
>> GNU Make 3.82.90 (Built for i686-pc-cygwin) runs fine in the
>> Cygwin shell, called from Cygwin's directory: /usr/bin/make
>>
>> How would you call it from Eshell?
>>
>> Thanks for any pointers!
>>
>> -BC
>>
>> Emacs: 24.1.50.1
>> Windows 7

Re: Eshell: Running GNU Make (Cygwin) on Windows 7

[Dan Espen]

William Crandall <bc3141592@gmail.com> writes:

> Hello,
>
> Is there a "best" way to run Cygwin's GNU Make from Eshell
> on Windows 7?
>
> GNU Make 3.82.90 (Built for i686-pc-cygwin) runs fine in the
> Cygwin shell, called from Cygwin's directory: /usr/bin/make
>
> How would you call it from Eshell?
>
> Thanks for any pointers!

Why Eshell?

M-x compile

-- 
Dan Espen

Re: Eshell: Running GNU Make (Cygwin) on Windows 7

[rusi]

On Jun 8, 5:10 am, William Crandall <bc3141...@gmail.com> wrote:
> Hello,
>
> Is there a "best" way to run Cygwin's GNU Make from Eshell
> on Windows 7?
>
> GNU Make 3.82.90 (Built for i686-pc-cygwin) runs fine in the
> Cygwin shell, called from Cygwin's directory: /usr/bin/make
>
> How would you call it from Eshell?
>
> Thanks for any pointers!
>
> -BC
>
> Emacs: 24.1.50.1
> Windows 7

These kind of questions bugged me (when I last used cygwin) and there
must be a more cygwin-ish way of handling paths.
1. The proper way is probably to use http://www.emacswiki.org/emacs/cygwin-mount.el
   I remember trying it and not getting it to work -- but I did not
try very hard
2. An improper way recommended by Steve Yegge is to install cygwin not
in c:/cygwin but in C: then everything "just works".  This of course
flies in the face of strong strictures from cygwin
3. Maybe you can just set the eshell-path-env and it works as you
want?
4. Getting compile to work is better as Dan suggests. Maybe you can
adjust compile-command?