Thanks all for the quick OS X education on frameworks. It has been a
long time since I tried to create one so I had forgotten all the
nuances. I think for my project I am going to stick with a
traditional Unix layout of Dylibs and Includes. The largest reason
among them I think I would
On 8/6/08 8:52 PM, Bill Hoffman said:
It was told to me by Mac experts, that the debug post fix should be
ignored for frameworks.
To expand on what others have said... here are some docs:
system-provided _debug variants:
http://developer.apple.com/technotes/tn2004/tn2124.html#SECDEBUGLIB
On 8/7/08, Mike Jackson [EMAIL PROTECTED] wrote:
Thanks all for the quick OS X education on frameworks. It has been a
long time since I tried to create one so I had forgotten all the
nuances. I think for my project I am going to stick with a
traditional Unix layout of Dylibs and Includes. The
I have the following:
SET_TARGET_PROPERTIES(${MXADATAMODEL_LIB_NAME} PROPERTIES
#DEBUG_OUTPUT_NAME ${MXA_LIBRARY_RELEASE}
#RELEASE_OUTPUT_NAME ${MXA_LIBRARY_RELEASE}
FRAMEWORK TRUE
FRAMEWORK_VERSION ${MXADATAMODEL_VER}
RESOURCE
DEBUG_POSTFIX _debug
)
and
Mike Jackson wrote:
I have the following:
SET_TARGET_PROPERTIES(${MXADATAMODEL_LIB_NAME} PROPERTIES
#DEBUG_OUTPUT_NAME ${MXA_LIBRARY_RELEASE}
#RELEASE_OUTPUT_NAME ${MXA_LIBRARY_RELEASE}
FRAMEWORK TRUE
FRAMEWORK_VERSION ${MXADATAMODEL_VER}
RESOURCE
On Aug 6, 2008, at 6:52 PM, Bill Hoffman wrote:
Mike Jackson wrote:
I have the following:
SET_TARGET_PROPERTIES(${MXADATAMODEL_LIB_NAME} PROPERTIES
#DEBUG_OUTPUT_NAME ${MXA_LIBRARY_RELEASE}
#RELEASE_OUTPUT_NAME ${MXA_LIBRARY_RELEASE}
FRAMEWORK TRUE
FRAMEWORK_VERSION
