On 02/10/2015 10:33 PM, Thiago Macieira wrote: > Before I can offer suggestions, I'd like to ask what our .so / .dll file > outputs > shall be. Will we have: > > a) one DLL for the C SDK, one for the base discovery & connectivity, one (or > more) for service? > b) one DLL for the C SDK and one for the C++ bits? > c) one DLL for everything?
Ooh. This is going to be a bit more problematic if DLLs need to be produced. Doing DLLs of the C++ parts is going to be extremely problematic (due to the OS and tool conventions on Windows). There also generally would be a need to support interesting combinations of static & dynamic on many fronts (static library linked to dynamic runtime, static library linked to static runtime...) So we might need to split the C into one or more DLLs and the C++ into one or more static libs. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com
