Static build with Visual Studio

[tanshihaj]

I'm wonder is it possible to build static version of libiio using Visual Studio compiler? Currently when I try to do it I get LNK2019 unresolved external symbol imp errors since here

libiio/iio.h

Lines 75 to 79 in 99ef201

	# ifdef LIBIIO_EXPORTS
	# define __api __declspec(dllexport)
	# else
	# define __api __declspec(dllimport)
	# endif

it defines __api either as __declspec(dllexport) or __declspec(dllimport), so linker, that links this library to my test program, thinks that this symbols should be defined in .dll.

Usually if you need to link static library __api should be defined as empty:
https://github.com/substack/libssh/blob/c073979235eb0d0587ac9cb3c192e91e32d34b06/include/libssh/libssh.h#L26-L42

Is it possible to add some kind of LIBIIO_STATIC definition to make it possible to link libiio as static library?

[tanshihaj]

I've tried to do it and it work in my case: tanshihaj@3b9305e

[dNechita]

I think we can add an option to build libIIO as a static library.

[rgetz]

Just as a reminder - libiio is LGPL. From the GNU.org website emphasis in mine:

(1) If you statically link against an LGPLed library, you must also provide your application in an object (not necessarily source) format, so that a user has the opportunity to modify the library and relink the application.
(2) If you dynamically link against an LGPLed library already present on the user's computer, you need not convey the library's source. On the other hand, if you yourself convey the executable LGPLed library along with your application, whether linked with statically or dynamically, you must also convey the library's sources, in one of the ways for which the LGPL provides.

It's not hard/difficult - but you must comply with the obligations of the license.