On Apr 19, 7:01 am, Benjamin Smedberg <benja...@smedbergs.us> wrote: > On 4/18/10 4:25 PM, n179911 wrote: > > > In 'gtkmozembed_glue.cpp', it has this comment '// This file is an > > implementation file, meant to be #included in a > > // single C++ file of an embedding application. It is called after > > // XPCOMGlueStartup to glue the gtkmozembed functions.' > > > My question is why it is not compile like the rest of the cpp files in > > src directory (e.g. EmbedProgress.cpp) and have TestXXX.cpp in test > > directory linked to the library created in src? > > Mostly because it would have to be a static library different from the > existing files in that directory, and by the limitations of our build system > we would have to put it in a different directory, and it wasn't worth the > hassle. > > What do we gain by making it a separate/new static library, instead of just > #including it as documented? > > --BDS
Thanks. I think I have questions about the embedding browser build system. Are these 2 directories compiled in 1 static library? or 2? From the Makefile.in, it looks like they are the same 'module'. embedding/browser/gtk/tests/ embedding/browser/gtk/src/ My understanding is gtk/tests is compiled into 1 executable and gtk/ src/ is compiled into 1 static library. Is that right? So if gtk/tests (an executable) can be linked to gtk/src (a static library), why can't we add anther file (gtkmozembed_glue.cpp) to that library (the library from browser/gtk/src) and have gtk/tests to link against it. I have tried that, but it won't linked. But i am not sure why. _______________________________________________ dev-embedding mailing list dev-embedding@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-embedding
