yang686526

dwgdirect libs on macintosh
dwgdirect libs on macintosh
i'm just getting started making the switch from opendwg to dwgdirect. i downloaded cw8shared.sit, no problem. the documentation states that static libs are available for all platforms, but so far i have been unable to find static libs for mac. also, even when i do #define _toolkit_in_dll_, i still get 101 undefined symbols when linking the odreadex sample program, using metrowerks codewarrior 9.3 under osx. i feel that i'm just missing something...
what library files do i need to add to my project, or what part of the documentation did i simply miss?
k. lathan
the libraries you are using are gcc compiled and your development environment is codewarrior.
hence the errors.
cw compiled libs seem to be available only for carbon target and not macho.
i too would like to get a codewarrior 9.x compiled macho libraries of dwgdirect.
static libs for mac
actually, i would be happy to have carbon libs for codewarrior. the app i am developing has been done according to carbon specs for years, as we have many customers who are reluctant to leave the classic environment, and other customers who prefer osx. but codewarrior does not seem happy with the gcc libs.
but even when i am using the shared libs, i still get link errors, so i am probably missing something vital.
any clues would be welcome.
we'll look into providing mach-0 libs built using codewarrior.
what linker errors are you getting using the cw8 shared libs?

shared lib problem
i am trying to run the odreadex sample program using metrowerks 9.3 in os x 10.2.8, and in despesration, on a different machine with os x 10.3.7.
two linker things: one is actually a set of warnings for multiple definitions, for example odgesurface::__vt in dd_ge.shlb previously defined in dd_db.shlb. that's not so bad; it doesn't seem to stop the app from running.
but on launch, the dynamic linker issues a statement:
the application "(null)" could not be launched because of a shared library error.
"1<dwgreader><dd_alloc.shlb><msl_all_carbon.shlb>< >"
as nearly as i can interpret this message, it looks as though something within msl_all_carbon.shlb is trying to import an entry point from an unnamed library.
i have copies of all of the shared libraries that i have explicitly linked to the app present in the same folder where the app resides.
ken lathan
same problem
i have the same problem but using codewarrior 8.3.
also: "i have copies of all of the shared libraries that i have explicitly linked to the app present in the same folder where the app resides."
but with the same error.
do you solve this problem?
are there some codewarriors projects to guide how are the libraries to be linked?
thank you
quote:
originally posted by ken lathan
i am trying to run the odreadex sample program using metrowerks 9.3 in os x 10.2.8, and in despesration, on a different machine with os x 10.3.7.
two linker things: one is actually a set of warnings for multiple definitions, for example odgesurface::__vt in dd_ge.shlb previously defined in dd_db.shlb. that's not so bad; it doesn't seem to stop the app from running.
but on launch, the dynamic linker issues a statement:
the application "(null)" could not be launched because of a shared library error.
"1<dwgreader><dd_alloc.shlb><msl_all_carbon.shlb>< >"
as nearly as i can interpret this message, it looks as though something within msl_all_carbon.shlb is trying to import an entry point from an unnamed library.
i have copies of all of the shared libraries that i have explicitly linked to the app present in the same folder where the app resides.
ken lathan
our odvectorizeex sample project links in msl_all_carbon.shlb and msl_runtime_ppc.lib, in addition to our dwgdirect shared libraries. our faq is not correct--we do not link in msl_appruntime_ppc.lib. also, our odvectorizeex project specifies __start for it's main entry point, and the initialization and termination points are blank. you might try changing your project settings to this, to see if that makes any difference.
if this does not help, please send mail to and we will provide further assistance.