Re: building a library with an external dependancy

[Paul Pluzhnikov <ppluzhnikov-nsp@xxxxxxxxxxx>]

"Martijn" <subscription-remove-101@xxxxxxxxxxxxxxxxxxx> writes:

>> Generally, you should list all system libraries *after* all of
>> "user" (i.e. your own) libraries.
>
> I know that this is usually why libraries are at the end of the command
> line, but I didn't realize this problem could exist among libraries as well.
> What can I do with to avoid the dependancy on the comctl32 library?  In the
> future I don't want to bother myself (and maybe others) with the fact that
> linking in my library also requires the comctl32 library to be linked.

You could build your library as a DLL. DLLs "remember" what other
libraries are required.

MSVC also has a special '#pragma comment(linker, "comctl32.lib")'
which allows you to specify that comctl32 should be added to the
link line whenever an object containing the '#pragma' above is
linked. 

AFAICT, gcc does not support this feature, so if you insist on
compiling your library with gcc and do not want to build a DLL,
then you must add libcomctl32 to the link line yourself.

Cheers,
-- 
In order to understand recursion you must first understand recursion.
Remove /-nsp/ for email.