Most likely, the Jamfile which controls how that particular solution is configured neglects to add appropriate linkage directives. (From evidence presented, it seems like it might be using Unix linkage directives rather than MSVC.) I have not personally had a chance to investigate it, but perhaps the person who set it up originally can provide more insight.
-- ES Emanuele Bertoldi wrote: > Ok, but the question is: why? :) > > My steps: > > 1 - Building "CS/MSVC9/wkstypical" solution (Debug with static libs). > 2 - Building "CS/MSVC9/wkspytypical" solution (Debug with static libs). > 3 - Building "CEL/MSVC9/wkscel" solution (Debug with static libs). > 4 - Building "CEL/MSVC9/wkspycel" solution (Debug with static libs). > > Now, the step 4 fails with 51 linking errors: > > - fatal error LNK1120: 8 unresolved externals "...\CEL\blpython.dll" > (line 1) > - fatal error LNK1120: 40 unresolved externals "..\..\_blcelc.pyd" > - error LNK2019: unresolved external symbol > "__imp__Py_InitModule4TraceRefs" referenced in function "void __cdecl > InitPytocel(void)" (?InitPytocel@@YAXXZ) (pytocel.obj) > - error LNK2019: unresolved external symbol > "__imp___PyObject_DebugMalloc" referenced in function > "_PySwigObject_New" (blpython.obj) > ... > - error LNK2019: unresolved external symbol > "__imp___invalid_parameter_noinfo" referenced in function "public: bool > __thiscall std::_Tree<class std::_Tmap_traits<void *,struct > Swig::GCItem_var,struct std::less<void *>,class std::allocator<struct > std::pair<void * const,struct Swig::GCItem_var> >,0> > >::const_iterator::operator==(class std::_Tree<class > std::_Tmap_traits<void *,struct Swig::GCItem_var,struct std::less<void > *>,class std::allocator<struct std::pair<void * const,struct > Swig::GCItem_var> >,0> >::const_iterator const &)const " > ([EMAIL PROTECTED]@[EMAIL PROTECTED]@Swig@@[EMAIL PROTECTED]@std@@[EMAIL > PROTECTED]@[EMAIL PROTECTED]@@@std@@@[EMAIL > PROTECTED]@@std@@@std@@QBE_NABV012@@Z) > (blcel.obj) > ... > - error LNK2001: unresolved external symbol "__imp___Py_RefTotal" > (pytocel.obj) > - error LNK2001: unresolved external symbol "unsigned int const > pycel_py_wrapper_size" (?pycel_py_wrapper_size@@3IB) (blpython.obj) > - error LNK2001: unresolved external symbol "public: virtual void > __thiscall celPcCommon::SetTag(char const *)" > ([EMAIL PROTECTED]@@[EMAIL PROTECTED]) (blcel.obj) > ... > > Thank you! > > -- EB > > Eric Sunshine ha scritto: >> These errors imply that the module is not linking against the CS libraries. >> >> -- ES >> >> Emanuele Bertoldi wrote: >> >>> Yes, sure, but linking errors are 285... ;) >>> >>> - error LNK2001: unresolved external symbol "public: static struct iSCF >>> * iSCF::SCF" ([EMAIL PROTECTED]@@[EMAIL PROTECTED]) (rulebase.obj) >>> - ... >>> - error LNK2019: unresolved external symbol >>> "__imp__Py_InitModule4TraceRefs" referenced in function "void __cdecl >>> InitPytocel(void)" (?InitPytocel@@YAXXZ) (pytocel.obj) >>> - error LNK2019: unresolved external symbol >>> "__imp___PyObject_DebugMalloc" referenced in function >>> "_PySwigObject_New" (blpython.obj) >>> - error LNK2019: unresolved external symbol "__imp___PyObject_DebugFree" >>> referenced in function "_PySwigObject_dealloc" (blpython.obj) >>> - ... >>> - error LNK2005: "public: void __thiscall >>> csVector3::Set(float,float,float)" ([EMAIL PROTECTED]@@[EMAIL PROTECTED]) >>> is >>> already defined in "movefact.obj" (libcrystalspace_d.lib) >>> - ... >>> - error LNK2001: unresolved external symbol "__imp___Py_RefTotal" >>> (blpython.obj) >>> - ... >>> - error LNK2001: unresolved external symbol "protected: static struct >>> iObjectRegistry * csApplicationFramework::object_reg" >>> ([EMAIL PROTECTED]@@1PAUiObjectRegistry@@A) (celtest.obj) >>> - ... ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Cel-main mailing list Cel-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cel-main
