Re: Separate build rules (was Re: [Mingw-cross-env-list] Mingw64)

[Tony Theodore]

On 19 December 2010 03:16, Tony Theodore <address@hidden> wrote:

> Having said that, I thought I'd go ahead with a proof-of-concept,
> changesets attached.

I've progressed to building all of mingw-cross-env using the mingw.org
runtime, and qt using mingw-w64. I've set up a repository here:

https://bitbucket.org/tonyt/mce-multi-target/

Everything seems to be working correctly, with a couple of observations.

1. Build order can be a little confusing. It initially looks like it's
building i686 targets, then switches to x86_64 after the first
specified package is reached. If you're calling "make package" this is
all fine, but a plain "make" will build atk_i686 and all i686 deps,
then switch.

2. Changing a *.mk file causes both targets to be rebuilt. This is
probably obvious, but it can be very annoying, especially for large
packages. There's no real way around this, other than specifying
TARGETS when you're debugging something.

3. There's lot's of flexibility with consolidating common build
sections. freetds, openssl, and qt are examples of "good?" style, gcc
probably isn't. We'd want to establish some conventions around this as
you can do some elaborate and complex things.

4. Still need to decide what to do with "empty" build rules, and
possibly find a way of distinguishing between a know failure and
package that simply downloads a tarball. At some stage, we might want
to parse the src/*.mk files and update the package list in the docs
with their 64-bit support.

Cheers,

Tony