Name Conflict when Building Boost libraries with Cygwin/GCC

Question

I'm in the process of migrating a C++ application from VC++ to GCC (running on Windows using Cygwin). My first problem now is that I cannot build the Boost libraries. For example to build Boost.Exception with VC++ I would write: ``` b2 --with-exception variant=debug,release link=static runtime-link=static ``` and I would get the files libboost_exception-vc100-mt-s-1_51.lib and libboost_exception-vc100-mt-sgd-1_51.lib in my stage\lib directory. However when I try the same using GCC form a Cygwin terminal I get errors. I found out that building only debug (or only release) like this works: ``` ./b2 --with-exception variant=debug link=static runtime-link=static ``` It creates libboost_exception.a in my stage\lib directory for both cases (debug and release). So there seems to be a name conflict (same name for debug and release variant). Is this a bug in the boost build system or am I doing something wrong? Edit: The output of ``` ./b2 --with-exception variant=debug,release link=static run…

Accepted Answer

Although the error message is not perfect, this is operator error. By default, the build uses system naming of library -- the naming you would have on your typical Unix system. So, yea, if you try to build both debug and release variant, you get naming clash.

If you add `--layout=tagged` or `--layout=versioned` to your command line, things should work. You can run "./b2 --help" from the top directory to get some explanation for these mean.

Name Conflict when Building Boost libraries with Cygwin/GCC

Solution

Problem