Mir

The include directory structure isn't discriminating enough

Bug #1152688 reported by Alan Griffiths
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
Undecided
Alan Griffiths

Bug Description

There is a lack of precision around our mir directory structure, and it is
beginning to matter.

What I think we need is four separate roots for include files (not sure of the names. please bear with me):

1. server_include
2. shared_include
3. client_include
4. test_include

Different parts of the codebase should be compiled with appropriate combinations of the above.

1. server_include & 2. shared_include

server_include and shared_include should have both mir and mir_toolkit subdirectories (Examples of what belongs in shared_include/mir are graphics and protobuf - the rest of include/mir belongs to server_include)

3. client_include

I think client_include just needs a toolkit subdirectory.

4. test_include

test_include would include the current mir_test, mir_test_cucumber, mir_test_doubles and mir_test_framework

Packaging the client toolkit headers would pick up shared_include/mir_toolkit and client_include/mir_toolkit

~~~~

One obvious alternative is:

1. include/server
2. include/shared
3. include/client
4. include/test

With subdirectories as above.

Related branches

Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.0.2

Changed in mir:
status: New → Fix Committed
Changed in mir:
milestone: none → 0.0.3
assignee: nobody → Alan Griffiths (alan-griffiths)
Changed in mir:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.