linking to a static 0MQ library in VS

Question

This may be a Visual Studio question more than anything else...
I\'m trying to build a 0MQ C++ example using VS10 and ZeroMQ 2.2.0.
I downloaded the windows sources and

Answer 1

Is the static linking very important to you? If not, you can try out the second answer by elnino_9 here. Elaborating elnino_9's answer:

• Download the sources and unzip to some local folder (say C:\dev\zeromq).
• Go to C:\dev\zeromq-2.2.0\builds\msvc and open the msvc.sln solution. MS2010 will upgrade from a VS2008 to a VS2010 project
• Build all of the projects.
• The build should generate the two following files:
  • C:\dev\zeromq\lib\libzmq.lib - this is what you will need to reference in your project's linker options
  • C:\dev\zeromq_boaz\builds\msvc\Release\libzmq.dll - this you will need to copy to the same folder as your project's executable in order to run it (if your build was configured to 'Debug', the path would be C:\dev\zeromq\builds\msvc\ Debug \libzmq.dll)
• Create your solution and project. Do the following:
  • In the Solution Explorer, right-click on you project, and select 'Properties' (at the very bottom).
  • Navigate to 'C/C++ --> General --> Additional Include Directories' and add C:\dev\zeromq\include. This will reference 0MQ's header files.
  • Navigate to 'Linker --> Input --> Additional Dependencies' and add the full path to the 'libzmq.dll' file from the previous step.
  • Build your project - this should go without errors now.
• Copy 'libzmq.dll' to the same folder as your executable - your project should now run.

Some comments:

• I am not sure why you need to reference the 'libzmq.lib' file. It is not needed by the executable (you can delete it, and it will still run, as the necessary logic resides in the dll). Can someone explain this?
• Notice one caveat in the example for Windows users - the second binding statement (publisher.bind("ipc://weather.ipc");) will cause an exception. As explained here (though in fine-print), the Inter-Process Transport is not supported on Windows.

EDIT

I think the answer to my first comment can be found in MSDN:

"When the source code for the calling executable is compiled or assembled, the DLL function call generates an external function reference in the object code. To resolve this external reference, the application must link with the import library (.lib file) provided by the maker of the DLL."