Include directory structure, and installation packages
Robert Ancell
robert.ancell at canonical.com
Thu Mar 21 21:45:22 UTC 2013
On 21/03/13 14:53, Daniel van Vugt wrote:
> I suggest the best way to establish a header layout is to just say
> what you want users of Mir to include. i.e. Express your opinion on
> the requirements. For example I would say something like:
>
> Clients include:
> #include <mir/client/something.h>
>
> Server includes:
> #include <mir/server/somethingelse.h>
>
> Common stuff (if required at all):
> #include <mir/foo.h>
> or
> #include <mir/common/foo.h>
This makes sense to me.
>
> Please also keep in mind that it's unlikely we will reach a "final
> solution" within the next few commits. The design will be iterated and
> evolve.
+1
More information about the Mir-devel
mailing list