CEGUI (Crazy Eddie's GUI) Forums

I finally could build CEGUI. *happy* Im not sure why, but after I removed everything, then recompiled bjam, boost and CEGUI I only had a slight difference in Lib names: libboost_signals-vc71-mt-gd-1_32.lib vs. libboost_signals-mt-gd-1_32.lib which doesnt seem to make a difference after renaming. And...

I couldnt get it to work, so I now got me VC7.1. So far everything worked (compiling boost from cvs and CEGUI from cvs) but the linking fails. CEGUI wants to link: libboost_signals-vc71-mt-gd-1_31.lib Now I wonder how the name of this lib is generated. Im using boost from cvs which produces: libboos...

Maybe Im doing something stupidly wrong building boost? What I do is:
>bjam "-sTOOLS=msvc-stlport" "-sSTLPORT_VERSION=4.6" "-sSTLPORT_PATH=D:\cvs\STLport-4.6"

Anyone knows about the autolink mechanism of boost? I found this in the CEGUI code: // setup auto-link for boost.signals (works only with _MSC_EXTENSIONS on and with MSCV or Borland compilers, so they say...) // if this can't be used obviously you need to link with the appropriate version of the lib...

Sorry, no offense ment.

Its just 30 degree celsius and im trying to get this to work since 2 days.

Thnx saetrum, but it seems just not right that in order to get a lib working (even if its as great as CEGUI ) to downgrade (in case of STLPort) to older versions of other libs.

Thnx a lot for the quick answer. -- My project (debug): I set _STLP_DEBUG but now I end up with: LINK : fatal error LNK1104: cannot open file "libboost_signals-vc6-mt-sgdp-1_31.lib" With the manually build from boost: I double checked to have the right headers included, even set some pragm...

Im using VC6 SP4, cvs Ogre, STLPort4.6. I 1st tried to compile with the cvs version from boost, but failed utterly (s.b.). Now i tried to use the dependency packages above and end up with: debug - CEGUI compiles ok. but then building my project: warning: STLPort debug versions are built with /D_STLP...