Objection!
Unless you throw out decades of Unix experience and the ability to nest Unix commands in makefiles, you cannot have only one style of bracketing.
Unless your goal is to create yet another incompatible, self contained build system that cannot leverage off of anything else, you should use the well established Unix conventions. ${VARIABLE} is the standard within scripts. $(VARIABLE) is either an error, or means something else.
On Jun 27, 2005, at 2:56 PM, Scott Tooker wrote:
File a bug on that. We really want to standardize on one style of bracketing in the future and $() looks to be the winner.
Scott
On Jun 27, 2005, at 12:34 PM, Jonas Maebe wrote:
On 27 jun 2005, at 20:15, Scott Tooker wrote:
Maybe the script itself can compare the build configuration using a ${XXX} define? If so, what's the define for the current build configuration?
Actually, that should be $(CONFIGURATION) (note the use of parens).
Well, inside the script it most certainly has to be ${CONFIGURATION} (at least since Xcode 2.1).
