public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>, cygwin@cygwin.com
Subject: Re: Distributing program compiled with gcc on Cygwin to Windows users
Date: Mon, 15 Oct 2018 20:20:00 -0000	[thread overview]
Message-ID: <841141726.20181015230650@yandex.ru> (raw)
In-Reply-To: <70b9ff4b-bd4c-d94d-9fec-ed3b82c98f2f@t-online.de>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 1496 bytes --]

Greetings, Hans-Bernhard Bröker!

>> I have a program that uses X11/Motif and runs fine, within Cygwin/X on the
>> PC it was compiled on.
>> 
>> What is the *minimum* required set of Cygwin libs and any other files I
>> need to distribute along with, it to end-users who may just have Windows
>> (and not Cygwin) installed?

> I'm reasonably sure that that minimum set would effectively have to be
> an actual Cygwin installation.  You'll need an X server, and that
> requires a pretty complete Unix tool environment.

> And that Cygwin environment will generally not transfer successfully
> from one machine to another by just copying files.  You really have to
> run the Cygwin setup program.

> And that's before we consider what might happen to users who actually
> _do_ already have a Cygwin installation on their machines.  Are you
> prepared to explain to them why you interfered with those?


Bottom line is, you are better off hosting your own Cygwin repository with
your program and tell your clients how to set things up to pull it.

See
> Documentation:         http://cygwin.com/docs.html
as well as setup --help.


-- 
With best regards,
Andrey Repin
Monday, October 15, 2018 23:05:30

Sorry for my terrible english...\x03B‹KCB”\x1c›Ø›\x19[H\x1c™\^[ܝ\x1cΈ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÜ\x1c›Ø›\x19[\Ëš\x1d^[[\x03B‘TNˆ\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ˜\KÃB‘^[ØÝ[Y[\x18]\x1a[ÛŽˆ\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ^[ØÜËš\x1d^[[\x03B•[œÝXœØÜšX™H\x1a[™›Îˆ\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÛ[\vÈÝ[œÝXœØÜšX™K\Ú[\^[\x19CBƒB

  reply	other threads:[~2018-10-15 20:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-14 21:20 hackerwiz
2018-10-14 21:49 ` R0b0t1
2018-10-15 19:32 ` Hans-Bernhard Bröker
2018-10-15 20:20   ` Andrey Repin [this message]
2018-10-16 18:49 ` cyg Simple
2019-04-04 22:16   ` drikosev
2019-04-04 23:20     ` drikosev

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=841141726.20181015230650@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=HBBroeker@t-online.de \
    --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).