From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: Issue with CYGWIN :(
Date: Tue, 17 Apr 2018 11:56:00 -0000 [thread overview]
Message-ID: <48976567-0a82-b3a5-62c2-0e646f4a17dd@cs.umass.edu> (raw)
In-Reply-To: <CAJ-ah2wT=Fy0KvxtfRA8JtRJ3UH6_9LJ62XyT=zGnjk8O6or8A@mail.gmail.com>
On 4/17/2018 2:35 AM, Imran Khan wrote:
> Hi BeCygwin,
> Can you help me in resolving the issue?
> 1. cd to LIVE-555 folder
> ************@DESKTOP-PUEEUEA /cygdrive/e/*****/*****/sw/LIVE-555*
> 2. execute the ndk-build command
> *$
> E:/********/*****/android-ndk-r10e-windows-x86_64/android-ndk-r10e/ndk-build*
> *Android NDK: Your APP_BUILD_SCRIPT points to an unknown file:
> E:\*******\******\android-ndk-r10e-windows-x86_64\android-ndk-r10e/jni/Android.mk*
>
*/cygdrive/e/Imran/REPO/android-ndk-r10e-windows-x86_64/android-ndk-r10e/build/core/add-application.mk:199
> <http://add-application.mk:199/>: *** Android NDK: Aborting... . Stop.*
Looks to me that ndk-build figures it's on a Windows machine and is using Windows-style
paths, etc. cygwin tries to make things *look* mostly Posixy, but if something insists
on realizing it is on Windows, then it is that thing that you need to adjust. I would
start by seeing how ndk-build determines what flavor of OS it's on, and seeing if you
can convince it to do more linux-style things. Of course, while any things build more
or less out of the box on cygwin, but everything will ...
Regards - Eliot Moss
--
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
prev parent reply other threads:[~2018-04-17 11:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 6:35 Imran Khan
2018-04-17 11:56 ` Eliot Moss [this message]
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=48976567-0a82-b3a5-62c2-0e646f4a17dd@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=cygwin@cygwin.com \
/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 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).