public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Darik Horn <dajhorn@vanadac.com>
To: cygwin@cygwin.com
Subject: Re: compile ncurses "hello world" to run independent of cygwin?
Date: Mon, 02 Nov 2015 04:09:00 -0000	[thread overview]
Message-ID: <CAPbcu1PQOi4xTTHpbvc1UV_zoj5wpL=E_nRsPV=xQ0p6OLL1XQ@mail.gmail.com> (raw)
In-Reply-To: <5636D2C5.6020309@ehdp.com>

On Sun, Nov 1, 2015 at 10:04 PM, Daniel Goldman <dgoldman@ehdp.com> wrote:
>
> What am I doing wrong? How do I use cygwin to compile the test ncurses
> program so it can run in a dos terminal, independent of cygwin? I looked
> around the docs and archives and could not figure out.

Was libncurses built for the MinGW target on the Cygwin host?

Keep in mind that this job is a cross compile, so ncurses and every
other dependency must be built for the MinGW runtime.  The mingw-* and
mingw64-* packages for Cygwin are just the toolchain plus some
essentials; there is no mingw-libncurses-devel package in
distribution.

Unless there is a specific reason to cross through Cygwin, it could be
easier to use the native MinGW environment directly:

* http://www.mingw.org/wiki/Getting_Started

And link against the ncurses redistributable:

* http://invisible-mirror.net/ncurses/ncurses.html

--
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

  reply	other threads:[~2015-11-02  4:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-02  3:04 Daniel Goldman
2015-11-02  4:09 ` Darik Horn [this message]
2015-11-02 12:48   ` cyg Simple
2015-11-02 15:14     ` Greg Freemyer
2015-11-02 15:34       ` Darik Horn
2015-11-02 15:49       ` Corinna Vinschen
2015-11-02 12:42 ` cyg Simple

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='CAPbcu1PQOi4xTTHpbvc1UV_zoj5wpL=E_nRsPV=xQ0p6OLL1XQ@mail.gmail.com' \
    --to=dajhorn@vanadac.com \
    --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).