[QBS] Platform specific Depends

Oswald Buddenhagen oswald.buddenhagen at nokia.com
Fri Sep 14 16:09:13 CEST 2012

On Fri, Sep 14, 2012 at 07:13:27PM +0600, ext Ruslan Nigmatullin wrote:
> 14.09.2012, 15:47, "Joerg Bornemann" <joerg.bornemann at nokia.com>:
> > On 13/09/2012 18:34, ext Сидоров Алексей wrote:
> >
> >>  How should be called platform specific modules?
> >>
> >>  Whether to use a prefix for the platform specific modules in Depends and whether to add condition variable?
> >
> > I vote for a prefix that corresponds to the platform's name.
> > Depends { name: "mac.Cocoa" }
> > Depends { name: "windows.user32" }
> >
yes, but we need to be very strict about what we permit into these

> But what to do with linux-specific libraries as libunity/glib/gtk/telepathy-*/etc?
> And should Growl (3rd-party library, but it's mac-specific) be in mac's namespace?
the namespacing vs. "trademarks" is one reason why i don't like this
namespacing too much.

the other reason is that many libraries are ported at some point and
suddenly are not platform-specific any more. which means we may only
namespace libraries which by definition cannot ever be useful on a
different platform (because both trademarks and pragmatism preclude it)
- for the mac and windows system dlls this would be true, while anything
from linux & unix is potentially portable.

related to that topic, it's also possible to have modules which are
dummies on some platforms - for libraries which may or may not actually
exist (e.g., bsd sockets as part of glibc, vs. separate libsocket on

More information about the Qbs mailing list