Boost link error, undefined icu reference about xoreos HOT 6 CLOSED

msys/mingw libraries are not compatible with MSVC. You either need boost/icu libraries that were compiled on MSVC, or compile them yourself.

Also make sure that you are using the same runtime in your MSVC build that was used when compiling boost/icu (i.e. /MD, /MT, /MTd, etc.) as otherwise you will get strange crashes

from xoreos.

I'm kinda at a loss here, sorry. This sounds to me like a completely broken Boost installation?

How did you install Boost? If you're using MSYS2 and use the ICU from MSYS2, you need to install the boost libraries using pacman within MSYS2 as well. Some parts of Boost depend on ICU, and you do obviously need the ICU version the Boost libraries were compiled against.

(However, you should be able to install multiple versions of ICU at the same time, as long as they're all compiled to have the version number encoded within the soname. You can even link against several different ICU versions within the same project, since ICU can encode the version number into its namespace as well. Not that I'm saying that's what you should do here, but ICU is able to cope with that.)

from xoreos.

Made mistake, said mingw62, meant mingw64
How did you install Boost?
Used pacman -U mingw64 boost file,1.62 version

Some parts of Boost depend on ICU,
Yeah, locale does.
Installing icu 57, let you know results

from xoreos.

Installed icu 57 using pacman.
Rebuilt common, google test libs.
Using common datetime test for quick build.
Rebuilt common datetime test, same error, boost locale can't find reference to icu_57 objects.
libboost_locale-mt.a(icu_backend.o undefined reference to `icu_57::Locale::Locale()

from xoreos.

It's not clear to me, what you're trying to do. If compiling xoreos using VS 2017 and Boost is what you want, you could always install prebuilt Boost libraries from (https://sourceforge.net/projects/boost/files/boost-binaries/) and pass it to CMake as - DBoost_INCLUDE_DIR. What do mingw and msys have to do with anything? :)

from xoreos.

Yeah, I'm going ahead and close this issue as not a bug. Feel free to reopen with more information if it still occurs.

from xoreos.