Carlo Bramini

I compiled and installed Boost 1.90.0 and the problem is gone. I think you can close this issue. I also agree that configure should also return an error if boost < 1.69.

Since Boost C++ libraries don't provide support for pkg-config or others (unless provided by the package maintainers for a particular distro), perhaps it would be worth to support some variables for letting the users to handle this event. The configure script already provides support for some variables defined by the user, as you can see from the output on the console, see attached screenshot. So, I would like to suggest to add something like BOOST_CXXFLAGS and BOOST_LIB for letting the user to select...

Since Boost C++ libraries don't provide support for pkg-config or others (unless provided by the package maintainers for a particular distro), perhaps it would be worth to support some variables for letting the users to handle this event. The configure script already provides support for some variables defined by the user, as you can see from the output on the console, see attached screenshot. So, I would like to suggest to add something like BOOST_CXXFLAGS and BOOST_LIB for letting the user to select...

I'm using boost-1.66.0-1

MINGW: Cannot build C::B, missing link to boost_system library.

Besides doing it manually with Visual Studio and create a number of sub-projects and static libraries like autoconf/automake does, probably the best and easier to maintain solution is to write something for creating everything on the fly with CMake. Today, I started to do something, it is not difficult but it requires some time.

Hello, I did a solution with a project file that you can use for building X64 emulator with resid. Resid has been added with a separate project file and compiled as static library, otherwise there is a conflict because there are source file with the same file and so the object files are overwritten. The attached file provides the new project. Don't forget to adjust again the path where sdlmain.lib is stored.

After reading your message, I also tried and you are right. I'm 100% sure that the Microsoft C/C++ compiler doesn't define WIN32 but only _WIN32 (I just tried to make a test) and in the past I was forced to do that change because an error happened. But now it works because the WIN32 macro has been added into the project file by Visual Studio, as you can see from the attached screenshot. So, it seems that the patch is no longer needed until WIN32 is defined somewhere. PS: I just read that you too...