This looks like the right behavior and is produced by CMake after processing WConfig.h.in to generate WConfig.h depending on the environment (i. e. third-party libraries, platform, compiler, etc).
The first WConfig.h is from a static build of Wt The second WConfig.h is from a shared build of Wt Please note the witty package builds *both* the static and the shared version, one in build-static and the other in build-shared. Are you sure you are comparing build-shared/WConfig.h to build-shared/WConfig.h, and build-static/WConfig.h to build-static/WConfig.h ? To me, it seems like you are comparting build-shared/WConfig.h to build-static/WConfig.h Could you please check again? If you still see this problem, please post more information about the user/group, hostname, locale, time, toolchain, etc. Some toolchains cannot compile some Boost code and therefore build a non-threaded version of Wt but I am not aware of a toolchain that cannot build a shared or static build*. * Well, I am: on Windows, older version of MSVC had trouble with Boost threads and shared libraries in the way Wt used them, but that does not apply here. Thank you -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer)
