From: Adrien Nader <adrien@notk.org>
To: caml-list@inria.fr
Subject: [Caml-list] [ANN] Win-builds 1.3 RC1 - Package manager on/for Windows with cross-compilers
Date: Mon, 23 Dec 2013 21:29:32 +0100 [thread overview]
Message-ID: <20131223202932.GC3114@notk.org> (raw)
Hi,
I've released version 1.3 RC1 of my Win-builds project, formerly known
as "yypkg mingw-builds".
Win-builds is a software distribution which targets Windows with both
native and cross toolchains from Linux and provides around 60 packages
of libraries and applications. It is supported by the yypkg package
manager both on Windows and Linux.
Why you shouldn't use this project:
- it works and is therefore going to be fairly boring
- it makes things too easy when dealing with Windows
- it has up-to-date components and is even going to feature security
update
- but it's not going to be bleeding-edge, which makes it even more
boring
- binary packages mean you don't get to pass -fomg-optimize and
-funroll-loops to GCC
- there is too litle Javascript and CSS on its website
- you might find bugs in your own software and build guilt about not
fixing them
- 1.3 is a bit cumbersome to setup on Linux (although it will work on every
distribution) and that will only be fixed during January or February
- you might have built your own system or want to do so in the future
- it's not on github
- I still haven't finished pushing my new 10-minutes introduction to
lablgtk and you resent me from not doing so
Website: http://win-builds.org/
Bug Tracker: http://win-builds.org/bugs
Documentation: http://win-builds.org/stable/
Downloads: the links are hidden inside the documentation
PS: the cross-compilation aspect is in my first reply to this message to
make things a bit clearer/cleaner.
--
Adrien Nader
next reply other threads:[~2013-12-23 20:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 20:29 Adrien Nader [this message]
2013-12-23 20:38 ` Adrien Nader
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=20131223202932.GC3114@notk.org \
--to=adrien@notk.org \
--cc=caml-list@inria.fr \
/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 NNTP newsgroup(s).