Wat r implications adding depeendamt libs in "Additional Dependencies" while creating a new static lib?
I want to ship a static library to number of users, now I have 2 approaches

1) While creating this static library include the dependent static libraries in the  "Additional Dependencies"section of the Librarian->General and thus get a single large lib

2) Ship this static lib and other static libs as individuals

Please help me with implications of using the either approach wrt debugging, performance, maintainabiltiy.

Does the option1 make debugging hard?
I want to distribute this library to large number of customers and mind u all the lib does is call LoadLibrary(), GetProcAddr() to make a DLL usable before the program starts.

Kind of workaround for implicit loading of DLL... for solving exception running this program as service in win2008.

Thank you in advance

Wat r implications adding depeendamt libs in "Additional Dependencies" while creating a new static lib?
===

I want to ship a static library to number of users, now I have 2 approaches

1) While creating this static library include the dependent static libraries in the  "Additional Dependencies"section of the Librarian->General and thus get a single large lib

2) Ship this static lib and other static libs as individuals

Please help me with implications of using the either approach wrt debugging, performance, maintainabiltiy.

Does the option1 make debugging hard?
I want to distribute this library to large number of customers and mind u all the lib does is call LoadLibrary(), GetProcAddr() to make a DLL usable before the program starts.

Kind of workaround for implicit loading of DLL... for solving exception running this program as service in win2008.

Thank you in advance
