Em Sábado 30. Janeiro 2010, às 16.56.17, Oswald Buddenhagen escreveu: > On Sat, Jan 30, 2010 at 04:49:40PM +0100, Thiago Macieira wrote: > > Em Sábado 30. Janeiro 2010, às 16.34.27, Oswald Buddenhagen escreveu: > > > > You don't link to applications. You link to libraries. > > > > > > > > This includes plugins: plugins link to libraries. > > > > > > uhm ... so? > > > - the application needs to provide headers which define the interface > > > - the application may provide an internal library to link against > > > > It's not internal. It's a public library, with installed headers. > > > > It is so because the hypothetical plugin we have in mind here comes from > > a separate module. > > well, yes. but one wouldn't put that library into a separate module, as > it is intrinsically part of the application. this breaks your concept > which doesn't permit dependencies on modules which are not explicitly > libraries.
But the application could put its library in a Library module. Then both the application and the plugin can link to that library. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Senior Product Manager - Nokia, Qt Development Frameworks PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-scm-interest mailing list Kde-scm-interest@kde.org https://mail.kde.org/mailman/listinfo/kde-scm-interest