On Tue, Jan 14, 2014, Peter Kümmel wrote: > On 13.01.2014 18:21, Adrien Nader wrote: > > On Mon, Jan 13, 2014, Peter Kümmel wrote: > >> What's mingw-w64's "state-of-the-art" way of cross compiling on Linux > >> (Ubuntu)? > > > > As Ruben pointed out, you can use the binaries from your distribution. > > In the case of Ubuntu, you inherit the ones from Debian most probably. > > However that means it's going to lag quite a lot, especially if there is > > no corresponding maintainer on ubuntu's side. > > > >> Could Win-builds be used without learning a new build system? > > > > You will obviously have some learning to do but it's very small and > > straightforward. Build scripts are raw shell scripts which run "make > > install DESTDIR=/tmp/foo" and then create a tar archive from these > > files; there is a bit more but that is enough to cover 95% of cases. > > OK, seems I was confused by some mails about a yy??? tool.
The yypkg tool is a tool used by win-builds; "yypkg" was part of the name of the project before but I renamed the project to avoid name clashes. > > That said, you only need to know that if you plan on making packages. If > > you only want to use the binaries, you don't need to know anything > > besides the few commands which are on the main documentation page. > > > > By the way, binary compatibility between distributions on Linux is done > > through a chroot. It's very compatible and fast to install but it's less > > nice to work with (although you can script a few things and be fine). > > That's why the next version will also make it possible to build and use > > your own compiler binaries; the downside is that it will take more time > > to build. I've already started working on that and it should be > > available in a few days. > > I like the idea to build everything from scratch. Do you know > www.buildroot.org ? > It's Makefile based, with embedded systems as targets, not sure if > win32 would be to exotic. I didn't know of buildroot back when I started. I think that when I started, buildroot was actually fairly young. That said, I'm not sure it makes a lot of sense to integrate into buildroot. First, buildroot generates images and from what I'm being told at work, it's not good at all when it comes to packages (it has not been made with that in mind). Then, that would require some changes to buildroot which might not be received so well (add clutter for a platform most don't use) but I'm speculating a bit here. There is also the fact that win-builds inherits from the slackware package scripts which are simple shell scripts and it also reuses the software versions in use there. This has reduced packaging work a _lot_ (it is most usually trivial) and helps keep up with security updates. As for building from scratch, it's a fully supported approach in win-builds and actually something I do fairly often. It is described at http://win-builds.org/1.3.0/diy.html . The main additional requirement is that you need a slackware mirror available. As I said, I hope to make the chroot a possibility and not a requirement anymore in the next few days and I actually _need_ that by the end of next week. Regards, Adrien Nader ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
