Per-target names for Xcode stlib project

In article <131le1tdg71ca3b DeleteThis @corp.supernews.com>,
SM Ryan <wyrmwif DeleteThis @tango-sierra-oscar-foxtrot-tango.fake.org> wrote:

> I'm not sure, but perhaps in the Project Info >> Build, add
> a new variable, say librarysuffix, and give it different values
> like "_d" or "" in different configurations. Then in the target
> Info >> Build >> Product Name, use the variable in the value,
> such as stlib$(librarysuffix). I haven't done this specifically,
> so I'm not sure if it will work.

Yes! This is immensely helpful. Thank you. :)
 >> Stay informed about: Per-target names for Xcode stlib project 

Steven Fisher <sdfisher.RemoveThis@spamcop.net> wrote:
# How can I control the name of the output file of a static library
# project on a per-configuration basis? I'm using Xcode 2.4.1.
#
# I know the usual way is to use the same name in per-configuration
# folders, but I am supposed to put everything in a single folder and use
# a _d suffix on debug executables. If it can't be done, fine, but I'd
# like to make sure it can't be done before I say that. :)

I'm not sure, but perhaps in the Project Info >> Build, add
a new variable, say librarysuffix, and give it different values
like "_d" or "" in different configurations. Then in the target
Info >> Build >> Product Name, use the variable in the value,
such as stlib$(librarysuffix). I haven't done this specifically,
so I'm not sure if it will work.

You can also add a script phase and refer to $librarysuffix, such as
cp libsomething.a libsomething$librarysuffix.a

--
SM Ryan http://www.rawbw.com/~wyrmwif/
Don't say anything. Especially you.
 >> Stay informed about: Per-target names for Xcode stlib project