My opinion? Probably dynamic, unless your application just so happens to be so terribly suited to static linking for some reason. But this is just out of what seems to be a general convention more than any compelling reason otherwise and I trust you not to take my word as some sort of gospel (duh). I'm going more with instinct than any facts and figures that make either way compelling.
Good old hell with those DLLs is one of the major problems with dynamic linking and something you want to avoid (who wouldn't?), but what with things like Microsoft's 'side-by-side' facilities, a bit of common sense and perhaps a teeny tiny bit of luck you shouldn't really have a problem with that. At least, not in this day and age. You'd think.
If I remember correctly Boost is a bunch of C++ utilities and "things" that just make your life easier. Something like that I might just statically link for speed/"so I know it works", and because it might not inflate the .exe as much as say, statically linking all of DirectX in.
Do you like answers that are basically 'maybe'? To be honest your linking method is probably rather inconsequential.
|
|
Bookmarks