hotplug plans - issue 1 (ideas welcome)
airlied at gmail.com
Tue Mar 6 11:59:56 PST 2012
> c) try and share the code as much as possible: This relies on keeping
> the internals of the exposed structures quite similiar. We have to
> take every file that can be shared and template it to deal with both
> sets of types, above and below the impedance layer. We would probably
> have to generate a large tables of #defines to prefix all the function
> names with a new identifier and also rework the code where there are
> differences or cannot share. This could be something as leaving the
> current types and function names in place and using a large sed
> scripts to build new C files on the fly that we compile into new
> modules, or something more complex involving changing function names
> and types so the code gets built in one of the other modes.
I've started looking at this option, bash + sed crazy scripts for now.
Probably need some help later integrating it with automake.
> This is of course only one of the issues I face, but I would need to
> get some ideas on merging and keeping the tree in some ways stable.
More information about the xorg-devel