[103473] trunk/dports/graphics

[Ryan Schmidt]

On Feb 26, 2013, at 16:51, cal at macports.org wrote:

> Revision: 103473
>          https://trac.macports.org/changeset/103473
> Author:   cal at macports.org
> Date:     2013-02-26 14:51:32 -0800 (Tue, 26 Feb 2013)
> Log Message:
> -----------
> birdfont: new port, see https://lists.macosforge.org/pipermail/macports-users/2013-February/031931.html
> 
> Added Paths:
> -----------
>    trunk/dports/graphics/birdfont/
>    trunk/dports/graphics/birdfont/Portfile
>    trunk/dports/graphics/birdfont/files/
>    trunk/dports/graphics/birdfont/files/patch-scripts__macports_build.py-use-cc-cflags-ldflags.diff
> 
> Added: trunk/dports/graphics/birdfont/Portfile
> ===================================================================
> --- trunk/dports/graphics/birdfont/Portfile	                        (rev 0)
> +++ trunk/dports/graphics/birdfont/Portfile	2013-02-26 22:51:32 UTC (rev 103473)
> @@ -0,0 +1,57 @@
> +# -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- vim:fenc=utf-8:filetype=tcl:et:sw=4:ts=4:sts=4
> +# $Id$
> +
> +PortSystem          1.0
> +
> +name                birdfont
> +version             0.18
> +revision            1

Not critically important, but the revision should typically start at 0.


> +distname            birdfont-${version}

This is the default, so it can be removed.


> +compiler.blacklist  clang

There should be a comment explaining why. It has already been announced that Xcode 4.6 is the last version that will include any compiler other than clang, so getting ports to work with clang is important.


> +configure.cmd       ./scripts/macport_configure.py
> +configure.args      --prefix=${prefix}

--prefix=${prefix} is already in configure.pre_args for you.

What's so special about MacPorts that it needs its own configure, build and install scripts?


> +build.cmd           ./scripts/macport_build.py
> +build.args          --prefix=${prefix} \
> +                    --cc=${configure.cc} \
> +                    --cflags=${configure.cflags} \
> +                    --ldflags=${configure.ldflags}

Might need to pass [get_canonical_archflags] in the cflags and ldflags too.