| www.delorie.com/archives/browse.cgi | search |
| X-Recipient: | archive-cygwin AT delorie DOT com |
| X-SWARE-Spam-Status: | No, hits=-4.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,T_RP_MATCHES_RCVD |
| X-Spam-Check-By: | sourceware.org |
| X-IronPortListener: | Outbound_SMTP |
| X-IronPort-Anti-Spam-Filtered: | true |
| X-IronPort-Anti-Spam-Result: | AucAAJVOkU2cKEcV/2dsb2JhbACYEI05d6s0mW+FagSQZohr |
| From: | "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder AT niaid DOT nih DOT gov> |
| To: | "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>, |
| "'moss AT cs DOT umass DOT edu'" <moss AT cs DOT umass DOT edu> | |
| Date: | Mon, 28 Mar 2011 23:19:16 -0400 |
| Subject: | RE: Bash: Cannot execute binary file |
| Message-ID: | <0105D5C1E0353146B1B222348B0411A209E396A241@NIHMLBX02.nih.gov> |
| References: | <31263793 DOT post AT talk DOT nabble DOT com> <20110329013343 DOT GD12793 AT ednor DOT casa DOT cgf DOT cx> <31263838 DOT post AT talk DOT nabble DOT com> <20110329015306 DOT GE12793 AT ednor DOT casa DOT cgf DOT cx> <4D914393 DOT 5090409 AT cs DOT umass DOT edu> |
| In-Reply-To: | <4D914393.5090409@cs.umass.edu> |
| MIME-Version: | 1.0 |
| X-IsSubscribed: | yes |
| Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
| List-Id: | <cygwin.cygwin.com> |
| List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
| List-Archive: | <http://sourceware.org/ml/cygwin/> |
| List-Post: | <mailto:cygwin AT cygwin DOT com> |
| List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
| Sender: | cygwin-owner AT cygwin DOT com |
| Mail-Followup-To: | cygwin AT cygwin DOT com |
| Delivered-To: | mailing list cygwin AT cygwin DOT com |
Eliot Moss sent the following at Monday, March 28, 2011 10:28 PM
>Why not just use the Windows version and invoke it from cygwin (if
>cygwin is the environment from which you want to do that)? It is easy
>to invoke Windows programs from cygwin; you just need to remember to
>format any arguments in the form the Windows program wants. To that end,
>cygpath is a useful utility, e.g.:
>
>function acrobat () { }
> command acrobat $(cygpath -wa ${1})
>}
>
>in your .bashrc file allows you to invoke Windows acrobat with a path
>rewritten from cygwin format to Windows format. This can be improved to
>check for presence of the argument ${1}, etc., but perhaps you get the
>idea.
- You should probably also add some quotes, in case your paths have spaces.
- A complete path to acrobat will avoid needing to have it in your path.
- Using cygstart will get you back to your command prompt.
function acrobat () {
if [ -f "${1}" ]
then
cygstart '/path/acrobat' "$(cygpath -wa "${1}")"
else
echo "error: file `${1}' not found!"
fi
}
Note: I have not tested the above. Debugging is left as an exercise for
the user.
- You also might look at cyg-wrapper.sh, found here:
http://hermitte.free.fr/cygwin/
Note: I don't use it so YMMV.
Good luck.
- Barry
Disclaimer: Statements made herein are not made on behalf of NIAID.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |