Include file_lock.hpp in two compilation units results in multiple definitions at link time (win32)

[jkp@…]

Including the file #include "boost/interprocess/sync/file_lock.hpp" from two seperate compilation units results in multiply defined symbols.

The reason is that the following symbols contain nested class definitions.

static inline bool unlink_file(const char *filename); static inline bool get_file_name_from_handle_function

(void * hFile, wchar_t *pszFilename, std::size_t length, std::size_t &out_length);

Moving the definitions for the functions to a source file and compiling that into the library instead solves the issue.

You can prove that the issue is the nested structs / classes by commenting out the function bodies.

This is a pretty serious issue since it pretty much means you cannot use boost interprocess under windows right now.

I'm compiling under MSVC8.1. The issue does not present itself under GCC, but then, these function implementations are win32 specific.

[jkp@…]

Small test-case to illustrate the issue: compile the code into a dll using VS2005

[jkp@…]

I have confirmed that this bug is confined to VS2005: in VS2008 the problem goes away. This is obviously a serious issue because it means anyone on VS2005 cannot use the library right now.

[Steven Watanabe]

Duplicates #2992.