TrustedUser
2,147
edits
Difference between revisions of "HOWTO-Dynamic Modules"
m
Text replacement - "</source>" to "</syntaxhighlight>"
m (Text replacement - "<source lang=" to "<syntaxhighlight lang=") |
m (Text replacement - "</source>" to "</syntaxhighlight>") |
||
| Line 45: | Line 45: | ||
#endif // defined(DYNAMIC_MODULES) && defined(FOOBAR) | #endif // defined(DYNAMIC_MODULES) && defined(FOOBAR) | ||
</ | </syntaxhighlight> | ||
==== Making the plugin linker script for your backend ==== | ==== Making the plugin linker script for your backend ==== | ||
| Line 55: | Line 55: | ||
{ | { | ||
plugin PT_LOAD ; | plugin PT_LOAD ; | ||
}</ | }</syntaxhighlight> | ||
*Set the start address of the file to be 0 (since this will be linked in at a different address later), usually you can do this by replacing the first line in SECTIONS with <code>. = 0;</code>, though different ld scripts may require different modifications. | *Set the start address of the file to be 0 (since this will be linked in at a different address later), usually you can do this by replacing the first line in SECTIONS with <code>. = 0;</code>, though different ld scripts may require different modifications. | ||
*Place the first section (as listed under the SECTIONS command) into the "plugin" segment you defined in PHDRS by appending <tt>:plugin</tt> to the first sections-command, i.e <code>.text . : { *(.text) } :plugin</code>. As long as there aren't any other PHDRS, this should ensure the entire linked file is put in the "plugin" segment, since future sections assume they are to be put in the same segment as the previous section unless specified otherwise (via <tt>:phdr</tt> or <tt>:NONE</tt>). | *Place the first section (as listed under the SECTIONS command) into the "plugin" segment you defined in PHDRS by appending <tt>:plugin</tt> to the first sections-command, i.e <code>.text . : { *(.text) } :plugin</code>. As long as there aren't any other PHDRS, this should ensure the entire linked file is put in the "plugin" segment, since future sections assume they are to be put in the same segment as the previous section unless specified otherwise (via <tt>:phdr</tt> or <tt>:NONE</tt>). | ||
| Line 72: | Line 72: | ||
KEEP (*(.dtors)) | KEEP (*(.dtors)) | ||
___plugin_dtors_end = .; | ___plugin_dtors_end = .; | ||
}</ | }</syntaxhighlight> | ||
*That's it! If you have trouble with any of these instructions or need to further modify the linker script for something specific to your platform, see [http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/gnu-linker/scripts.html] for linker script documentation and peruse the various <tt>plugin.ld</tt> files in the subdirectories of <tt>backends/plugins/</tt>. TODO: Add stuff about MIPS-specific linker script modifications, namely the "shorts" segment. | *That's it! If you have trouble with any of these instructions or need to further modify the linker script for something specific to your platform, see [http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/gnu-linker/scripts.html] for linker script documentation and peruse the various <tt>plugin.ld</tt> files in the subdirectories of <tt>backends/plugins/</tt>. TODO: Add stuff about MIPS-specific linker script modifications, namely the "shorts" segment. | ||
| Line 84: | Line 84: | ||
PRE_OBJS_FLAGS := -Wl,--whole-archive | PRE_OBJS_FLAGS := -Wl,--whole-archive | ||
POST_OBJS_FLAGS := -Wl,--no-whole-archive | POST_OBJS_FLAGS := -Wl,--no-whole-archive | ||
</ | </syntaxhighlight> | ||
As you can see, these modifications mainly deal with making sure the plugins are dependent on the main executable and use the custom linker script. | As you can see, these modifications mainly deal with making sure the plugins are dependent on the main executable and use the custom linker script. | ||