X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=VTK77oqn1lfBL2aC
	1iMjb4t4NiVr4TLowRxvRxhP5pBjLOkvv/F7tPDWtQKxVVsS9ZJXp82fx6A5eT06
	yFWMckC6d+QQMhBvo9gC2DInBioi21P6+kbLlLu4r0GoY5BZgH3IWKj+i9Ylg7Lk
	m/7zwD3IIh2Rd+AlDw47sfU9voY=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=qzOjM0AqvpAVr8INj3zvnv
	RFlCY=; b=WaFgPKisVv9qKxf3ZU/VU9rVLmAjmT6fJnXbON6VcZqzig+YIJ+9ck
	mGL9SvbEhhfKazkvND22yZGbEy27Tmbg1mwmhbO5fby8D3RhDkBn7VWtYWMY7Hhu
	Rv/beoOtOOGg8A4RyGMOhH4oICzpxiqz1E59++cCXJXGrreGplEsE=
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
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,KAM_NUMSUBJECT,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 spammy=php, ruby, whereas, mate
X-HELO: smtp-out-so.shaw.ca
Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject: Re: cygwin can not be compiled with gcc 8.3.0
To: cygwin AT cygwin DOT com
References: <CALK-3mKzG-1zhMQE5yV1fZyp_hWp1cRyOBQM4Tfqyins8KEfRA AT mail DOT gmail DOT com> <3a8155076bbb80ecf8a7a8d3076a331f AT smtp-cloud8 DOT xs4all DOT net> <CALK-3mKKB3ZcRczoPaGym97mgNe8pskEEW2B3nuPVou5RqNvcg AT mail DOT gmail DOT com> <8040fde0c0402fc3361515edbdd26d01 AT smtp-cloud8 DOT xs4all DOT net>
From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Openpgp: preference=signencrypt
Message-ID: <18676e31-a74b-b205-6cba-92303b589faf@SystematicSw.ab.ca>
Date: Sat, 6 Jul 2019 08:29:06 -0600
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <8040fde0c0402fc3361515edbdd26d01@smtp-cloud8.xs4all.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 2019-07-06 02:24, Houder wrote:
> On Fri, 5 Jul 2019 22:33:20, Biswapriyo Nath  wrote:
>>> cygwin is built using cygport ...
>> Is there any docs about it? I don't find the cygwin.cygport file in source
>> tree. Also I don't use source tarballs, git is my first choice. Also the
>> configure script or Makefile didn't warn me that I've not that cygport
>> package/script.
> Documents about using cygport? Well, sort of ...
>  - https://cygwin.com/packages.html
>  - https://cygwin.com/packaging-contributors-guide.html
>  - https://cygwinports.github.io/cygport/cygport.1.html
>  - https://github.com/cygwinports/cygport/blob/master/README
>  - https://cygwinports.github.io/cygport/toc_index.html
> Using (Cygwin) git as starting point?
>  - https://cygwin.com/git/gitweb.cgi?p=newlib-cygwin.git
>  - git is 'bleeding edge' (unstable by definition)
> cygwin.cygport file?
>  - No, not present in git ... (not present in the git for newlib-cygwin)
>  - a cygwin source tarball (to be found on any Cygwin mirror) is composed
>    of a tarball, which represents git at a 'specific moment' in time plus
>    the cygwin.cygport file
>  - specific moment? Look for the 'cygwin-3_x_y' tags in git ...
> mirrors: https://cygwin.com/mirrors.html
> cygport build/ cygport package
>  - the cygport build system is basically a wrapper around autoconf etc.
>    (and build systems like cmake)
>  - i.e. configure, make (Makefile) do not know about cygport

Files like ....cygport and ....hint are for packaging and appear only in
packaged sources not git repos.

Install cygport package and dependencies then:

	$ cygstart /usr/share/doc/cygport/html/manual/index.html
or
	https://cygwinports.github.io/cygport/

There are also source snapshots after Cygwin or newlib patches:

	https://cygwin.com/snapshots/
e.g.
	https://cygwin.com/snapshots/x86_64/cygwin-20190628-src.tar.xz

Using cygport makes it relatively trivial to build upstream packages, from
standard upstream mirrors or repos; using standard autotools, or configure and
make; cross building libraries for Mingw; addon modules for girepository, lua,
ocaml, perl, php, python2, python3, R, ruby, tcl, tex, vala; GUI libraries for
widget sets like qt and wx; or desktop window manager environments like GNOME,
KDE, LXDE, MATE, XFCE.

Whereas cygport automates a lot of the standard upstream source download, build
and package requirements, and Cygwin package repo upload, on the packager
maintainer client; calm automates a lot of the standard uploaded Cygwin package
repo checks, and maintenance of setup.ini entries, on the package repo primary
server.
Many source package builds also generate ...-debuginfo packages as well as
binary packages for both architectures, so there are three packages added to
each of the arch repos.
Library packages may also generate separate ...-devel packages for each arch to
support developer APIs, as well as the cyg....dlls in the binary packages.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

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