public inbox for newlib-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jturney@sourceware.org>
To: cygwin-cvs@sourceware.org, newlib-cvs@sourceware.org
Subject: [newlib-cygwin] Cygwin: Add .appveyor.yml
Date: Sat, 29 Aug 2020 14:42:13 +0000 (GMT)	[thread overview]
Message-ID: <20200829144213.D4AD6385043D@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=a07872603774c369e5eec69f3f650bf1153842d8

commit a07872603774c369e5eec69f3f650bf1153842d8
Author: Jon Turney <jon.turney@dronecode.org.uk>
Date:   Sun Aug 23 20:33:22 2020 +0100

    Cygwin: Add .appveyor.yml
    
    This is a slightly more polished version of the configuration being used
    for CI builds at https://ci.appveyor.com/project/cygwin/cygwin, which is
    not currently under version control.

Diff:
---
 .appveyor.yml | 69 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 69 insertions(+)

diff --git a/.appveyor.yml b/.appveyor.yml
new file mode 100644
index 000000000..602c189cd
--- /dev/null
+++ b/.appveyor.yml
@@ -0,0 +1,69 @@
+version: '{build}'
+
+branches:
+  only:
+  - master
+  - /cygwin/
+
+skip_tags: true
+shallow_clone: true
+
+environment:
+  APPVEYOR_SAVE_CACHE_ON_ERROR: true
+  CACHE: C:\cache
+  CYGWIN_MIRROR: http://cygwin.mirror.constant.com
+  matrix:
+  - BUILD: x86_64-pc-cygwin
+    CYGWIN_ROOT: C:\cygwin64
+    PKGARCH: mingw64-x86_64
+    SETUP: setup-x86_64.exe
+  - BUILD: i686-pc-cygwin
+    CYGWIN_ROOT: C:\cygwin
+    PKGARCH: mingw64-i686
+    SETUP: setup-x86.exe
+
+cache: C:\cache
+
+install:
+- if not exist %CACHE% mkdir %CACHE%
+- appveyor DownloadFile http://cygwin.com/%SETUP% -FileName %CACHE%\%SETUP%
+- "%CACHE%\\%SETUP% -qnNdO -R %CYGWIN_ROOT% -s %CYGWIN_MIRROR% -l %CACHE% -g -P \
+gcc-core,\
+gcc-g++,\
+make,\
+perl,\
+patch,\
+cocom,\
+gettext-devel,\
+libiconv-devel,\
+zlib-devel,\
+%PKGARCH%-gcc-core,\
+%PKGARCH%-gcc-g++,\
+%PKGARCH%-zlib,\
+dblatex,\
+docbook2X,\
+docbook-xml45,\
+docbook-xsl,\
+xmlto,\
+python3-lxml,\
+python3-ply"
+
+build_script:
+- '%CYGWIN_ROOT%/bin/bash -lc "cd $APPVEYOR_BUILD_FOLDER; mkdir build install"'
+- '%CYGWIN_ROOT%/bin/bash -lc "cd $APPVEYOR_BUILD_FOLDER/build; ../configure --prefix=$(realpath $(pwd)/../install) -v"'
+- '%CYGWIN_ROOT%/bin/bash -lc "cd $APPVEYOR_BUILD_FOLDER/build; make"'
+- '%CYGWIN_ROOT%/bin/bash -lc "cd $APPVEYOR_BUILD_FOLDER/build; make install"'
+- '%CYGWIN_ROOT%/bin/bash -lc "cd $APPVEYOR_BUILD_FOLDER/build; cd */newlib; make info man"'
+- '%CYGWIN_ROOT%/bin/bash -lc "cd $APPVEYOR_BUILD_FOLDER/build; cd */newlib; make install-info install-man"'
+
+test: off
+deploy: off
+
+# irc notification via notifico
+notifications:
+- provider: Webhook
+  url: http://n.tkte.ch/h/4848/0nqixIBiOFzf-S_N2PY83dGB
+  method: GET
+  on_build_success: false
+  on_build_failure: false
+  on_build_status_changed: true


                 reply	other threads:[~2020-08-29 14:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200829144213.D4AD6385043D@sourceware.org \
    --to=jturney@sourceware.org \
    --cc=cygwin-cvs@sourceware.org \
    --cc=newlib-cvs@sourceware.org \
    /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).