Hello Mahesh,
You don't say which build environment you're using, but I'll assume you're
using CodeWarrior. You've mentioned you don't want to link against
CarbonLib, so I'll also assume you don't want a Carbon build.
So this means you're doing a Classic build. The DOMPrint.mcp sample project,
which comes with Xerces-C, is actually a good example of this case. It has
build targets for both Classic and Carbon. In its Classic target, It links
against the following libraries:
- InterfaceLib
- TextEncodingConverter
- TextCommon
- UnicodeConverter
- UnicodeUtilitiesLib
- URLAccessLib
- MathLib
- MPLibrary
- CarbonAccessor.o
Needless to say, it is the MPLibrary that is supplying the MP... calls that
you query about below...
Good luck, and please let me know if you've got any questions.
-jdb
On 6/14/01 12:37 PM, "Mahesh Paranjape" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> We are using Xerces C++ XML parser library on Mac 9.0.
> We are using this Xerces library in another library and while making the
> project it comes with unresolved external
> symbols viz. MPExitCriticalRegion, MPEnterCriticalRegion etc.
> The linker errors go if we include CarbonLib in the project, but we want
> to avoid it this.
> Any pointers are welcome.
>
> Thanks and Best Regards,
> Mahesh
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
