Changes between Version 19 and Version 20 of PortfileRecipes


Ignore:
Timestamp:
May 27, 2010, 7:12:45 PM (14 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PortfileRecipes

    v19 v20  
    187187Note: Ensure you use the correct capitalization for each filename. For example, many projects typically use all-caps for most of the documentation files, except for ChangeLog, which is often written in camel-case. If you fail to use the correct capitalization, the port may still install on your system, but will fail for users with case-sensitive filesystems.
    188188
    189 == Removing -arch flags from *-config scripts and *.pc files == #archflags
    190 
    191 MacPorts provides `-arch` flags to ports' configure scripts in CFLAGS, LDFLAGS and similar variables, which tell the port what architecture(s) to build for, but these `-arch` flags should not appear in *-config scripts or pkg-config *.pc files because they will influence the build of dependent ports.
     189== Removing -arch flags from *-config scripts, *.pc files, etc. == #archflags
     190
     191MacPorts provides `-arch` flags to ports' configure scripts in CFLAGS, LDFLAGS and similar variables, which tell the port what architecture(s) to build for, but these `-arch` flags should not appear in *-config scripts or pkg-config *.pc files or the like because they will influence the build of dependent ports.
    192192
    193193Consider: [browser:trunk/dports/mail/libetpan/Portfile libetpan] @0.58_0+universal is installed. Its [changeset:66602 libetpan-config script contains -arch flags]. I now want to build etpan which depends on libetpan. [changeset:65910 etpan cannot be built universal] so I do not request the +universal variant when building etpan. Yet it still tries to build universal because it got the universal `-arch` flags from libetpan's config script, so the build fails.