* How to "make install"?
@ 1999-09-02 7:47 Stefan PETRUCHA
1999-09-02 8:22 ` Charles S. Wilson
1999-09-30 23:42 ` Stefan PETRUCHA
0 siblings, 2 replies; 4+ messages in thread
From: Stefan PETRUCHA @ 1999-09-02 7:47 UTC (permalink / raw)
To: cygwin
Hi,
I think it is obvious that the install utility program doesn't work for
binary executables because of .exe suffix. I saw some scripting solution
here so I tried it. I made shell script adding .exe to appropriate
parameters and calling the original install hidden somewhere out of
$PATH. Then I 'make install' just made groff package. Make passed but
oops! - all binary programs were installed to their locations without
the .exe suffix == unuseable. OK, I checked all files in /usr/local/bin
and added .exe to binary programs per script, but I don't like this as a
solution.
Has somebody something better? How do you "make install"?
Stefan Petrucha
--
http://www.isnet.sk/petrucha
____________________________________________________________________
Get free email and a permanent address at http://www.netaddress.com/?N=1
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to "make install"?
1999-09-02 7:47 How to "make install"? Stefan PETRUCHA
@ 1999-09-02 8:22 ` Charles S. Wilson
1999-09-30 23:42 ` Charles S. Wilson
1999-09-30 23:42 ` Stefan PETRUCHA
1 sibling, 1 reply; 4+ messages in thread
From: Charles S. Wilson @ 1999-09-02 8:22 UTC (permalink / raw)
To: cygwin
Stefan PETRUCHA wrote:
> Hi,
>
> I think it is obvious that the install utility program doesn't work for
> binary executables because of .exe suffix. I saw some scripting solution
> here so I tried it. I made shell script adding .exe to appropriate
> parameters and calling the original install hidden somewhere out of
> $PATH. Then I 'make install' just made groff package. Make passed but
> oops! - all binary programs were installed to their locations without
> the .exe suffix == unuseable. OK, I checked all files in /usr/local/bin
> and added .exe to binary programs per script, but I don't like this as a
> solution.
ftp://ftp.franken.de/pub/win32/develop/gnuwin32/cygwin/porters/Humblet_Pierre_A/install-cygwin-b20-sh
works fine for me. Download that shell script. Rename install.exe to
"cyg_install.exe". Rename this shell script to "install". Done.
>
> Has somebody something better? How do you "make install"?
>
> Stefan Petrucha
> --
> http://www.isnet.sk/petrucha
>
> ____________________________________________________________________
> Get free email and a permanent address at http://www.netaddress.com/?N=1
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to "make install"?
1999-09-02 8:22 ` Charles S. Wilson
@ 1999-09-30 23:42 ` Charles S. Wilson
0 siblings, 0 replies; 4+ messages in thread
From: Charles S. Wilson @ 1999-09-30 23:42 UTC (permalink / raw)
To: cygwin
Stefan PETRUCHA wrote:
> Hi,
>
> I think it is obvious that the install utility program doesn't work for
> binary executables because of .exe suffix. I saw some scripting solution
> here so I tried it. I made shell script adding .exe to appropriate
> parameters and calling the original install hidden somewhere out of
> $PATH. Then I 'make install' just made groff package. Make passed but
> oops! - all binary programs were installed to their locations without
> the .exe suffix == unuseable. OK, I checked all files in /usr/local/bin
> and added .exe to binary programs per script, but I don't like this as a
> solution.
ftp://ftp.franken.de/pub/win32/develop/gnuwin32/cygwin/porters/Humblet_Pierre_A/install-cygwin-b20-sh
works fine for me. Download that shell script. Rename install.exe to
"cyg_install.exe". Rename this shell script to "install". Done.
>
> Has somebody something better? How do you "make install"?
>
> Stefan Petrucha
> --
> http://www.isnet.sk/petrucha
>
> ____________________________________________________________________
> Get free email and a permanent address at http://www.netaddress.com/?N=1
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* How to "make install"?
1999-09-02 7:47 How to "make install"? Stefan PETRUCHA
1999-09-02 8:22 ` Charles S. Wilson
@ 1999-09-30 23:42 ` Stefan PETRUCHA
1 sibling, 0 replies; 4+ messages in thread
From: Stefan PETRUCHA @ 1999-09-30 23:42 UTC (permalink / raw)
To: cygwin
Hi,
I think it is obvious that the install utility program doesn't work for
binary executables because of .exe suffix. I saw some scripting solution
here so I tried it. I made shell script adding .exe to appropriate
parameters and calling the original install hidden somewhere out of
$PATH. Then I 'make install' just made groff package. Make passed but
oops! - all binary programs were installed to their locations without
the .exe suffix == unuseable. OK, I checked all files in /usr/local/bin
and added .exe to binary programs per script, but I don't like this as a
solution.
Has somebody something better? How do you "make install"?
Stefan Petrucha
--
http://www.isnet.sk/petrucha
____________________________________________________________________
Get free email and a permanent address at http://www.netaddress.com/?N=1
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~1999-09-30 23:42 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-09-02 7:47 How to "make install"? Stefan PETRUCHA
1999-09-02 8:22 ` Charles S. Wilson
1999-09-30 23:42 ` Charles S. Wilson
1999-09-30 23:42 ` Stefan PETRUCHA
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).