Split interfaces to the glue layer and backend into different files#5180
Split interfaces to the glue layer and backend into different files#51809rnsr merged 1 commit intodlang:masterfrom
Conversation
|
See also #5082 |
|
I would prefer the idea of |
|
What would that gain? I don't see the point. I'm thinking about splitting out the 'driver' code (mars, lib_, scan_, inifile, link etc) from the rest of the frontend, and as you know I'd like to ban glue/backend references from the rest of the frontend. |
|
Well, apart from It could be at least be used as a connector for alternate backends, eg, As for the ban on references, I'm certainly not against the idea of using a common name/alias for backend types so long as they have a consistent naming scheme. And so on... |
Think of it as temporary! The problem with the current system of using |
|
I can accept this temporary change, after the Darwin_64_32 breaking is fixed. |
296ac1e to
be9c324
Compare
|
@9rnsr Updated. |
|
Auto-merge toggled on |
Split interfaces to the glue layer and backend into different files
|
Thanks! |
And add make rules to build a backendless dmd.
In order to generate header files for dmd, I need a working dmd binary with the c++ header generation enabled. Until the frontend headers are built it's impossible to build the dmd glue layer or backend.
So the steps are:
This process will let us move to generated headers without changing build dependencies.