Cross-Prelink
Project Background
The upstream prelink project was founded by Jakub Jelinek at Red Hat. The upstream project is primarily focused on self-hosted configurations and does not support prelinking a target filesystem in a cross-development environment.
This limitation is due to the prelink software requiring the runtime linker to be available in order to resolve linking dependencies.
The cross prelink patches began at MontaVista around 2003 in order to work around this limitation. The original patches added the ability to emulate a runtime linker, as well as enabled a sysroot option. Over time, this work was continued by MontaVista, Wind River and CodeSourcery. Unfortunately, while all of the patches had been made public in one fashion or another, there was no central location that gathered and offered to manage these changes. Starting with the Yocto Project we have decided to put together these patches and make them available as a single unit, with a clear upstream that will happily accept patches.
Upstream Prelink
The upstream prelink project is located at sourceware.org.
For mailing lists, see: http://sourceware.org/ml/prelink/
For SVN access to the upstream tree, see: svn://sourceware.org/svn/prelink/
Yocto Project Cross-Prelink
See the https://www.yoctoproject.org/tools-resources/projects/cross-prelink page on the website for more information on this project.
Mark Hatle -- User:Mhatle is the project maintainer for the cross-prelink component of the Yocto Project.
Patch Submission
For Yocto-generic information on patch submission, see the Contribution Guidelines.
For cross-prelink specific information, see README.cross.
Git Archive Branches
The main branches of interest of the git archive are:
- cross_prelink contains the cross-prelink sources.
- cross_prelink_staging contains proposed changes for the cross-prelink sources.
- master tracks the upstream prelink tree. Note that this may or may not be up to date.