cairo universal for Tiger built from Leopard/ppc

[reiffert@…]

When building cairo universal I had to change the Portfile. I am building on leopard/ppc and I want to let this run on tiger/intel.

I was building cairo with:

port install cairo +universal +no_x11 macosx_deployment_target=10.4 

which does the job when I use --host=i686-apple-darwin8 and --host=powerpc-apple-darwin8 like can be found in the patch.

Now it really beats me, when I want to merge my changes to a new Portfile under the circumstances, that this should only be used when building from leopard/ppc.

I was trying something like

platform Darwin 9 powerpc {
   //  my configure here
}

but it gets ignored.

Kind regards
Thomas

[ryandesign@…]

I haven't looked at this problem very much, but this is probably a MacPorts base problem. When running on Leopard, MacPorts uses the 10.5 SDK to make universal binaries, which means universal ports made on Leopard should only be used on Leopard or above. Anders has ​just brought this up on the mailing list and believes he has found ​the better solution. So let's wait for that fix, and then see if any patches to cairo are still necessary.

[afb@…]

The default +universal setup will go back to using 10.4u SDK and i386/ppc. Probably in 1.6.1 even.

[gui_dos@…]

On MacPorts 1.7 from trunk the patch is working only after appending

-mmacosx-version-min=10.4

to my_ldflags

[ryandesign@…]

I'm not applying Thomas' patch; it removes my foreach loop. I want that loop so that it's easy to replace ${my_universal_archs} with ${configure.universal_archs} once that's released from trunk.

[reiffert@…]

It's ok with me, you can close the ticket if you like. I dont plan to use cairo as universal variant in the future.

Kind regards Thomas

[anonymous]

Milestone Port Enhancements deleted

[ryandesign@…]

Replying to reiffert@…:

I am building on leopard/ppc and I want to let this run on tiger/intel.

The code in MacPorts base that once allowed ports built on Leopard to target Tiger (the ability to change the universal SDK) has been removed with MacPorts 1.8.0 so this issue will not be fixed.