#13804: osxvnc: allow non-universal build -----------------------------------+---------------------------------------- Reporter: anton@bladehawke.com | Owner: ryandesign@macports.org Type: enhancement | Status: closed Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.6.0 Resolution: fixed | Keywords: -----------------------------------+---------------------------------------- Changes (by ryandesign@macports.org): * status: new => closed * resolution: => fixed * summary: osxvnc: -universal variant => osxvnc: allow non-universal build Comment: I'm happy to change osxvnc so that universal is not the default. I just didn't know exactly how to do it. "`xcode.build.settings ARCHS=$(NATIVE_ARCH)`" is not the solution; the port self-destructs with the message "`can't read "(NATIVE_ARCH)": no such variable`". "`xcode.build.settings ARCHS=\$(NATIVE_ARCH)`" isn't it either; this passes $(NATIVE_ARCH) on to the xcodebuild line, but that then complains with "`sh: line 1: NATIVE_ARCH: command not found`" "`xcode.build.settings ARCHS=\\\$\\(NATIVE_ARCH\\)`" gets past the errors and the build completes, but still ends up being universal. I'm not keen on calling out to `uname -m`... I'll do it the way Anthony Ramine has been doing in his ports for some time. Committed in r35717. Thanks for all the suggestions though! No revision bump is necessary. Users who had the port installed previously automatically had the +universal variant selected. Users who now install the port will get it without +universal, but can select +universal if they want it. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/13804#comment:4> MacPorts </projects/macports> Ports system for Mac OS