| 1 |
On 14-07-2009 14:26:26 +0200, Markus Duft wrote: |
| 2 |
> I'm just working on making preserved libs work on interix and winnt. |
| 3 |
> right now I'm trying to get an overview of the linkage map code in |
| 4 |
> dbapi/vartree.py ... now i wonder why there is a separate |
| 5 |
> LinkageMapMachO? what was the reason for not hacking this into the |
| 6 |
> existing LinkageMap? |
| 7 |
|
| 8 |
It uses a different strategy, which seems close, but is not entirely |
| 9 |
like it. (Darwin Mach-O vs ELF) |
| 10 |
|
| 11 |
> would you advise to create a separate LinkageMapInterix/LinkageMapWinnt |
| 12 |
> class for each platform, also if i would only need a few small changes? |
| 13 |
|
| 14 |
Depends. Mach-O uses absolute paths instead of just filenames, that's |
| 15 |
why it's a separate case. The freedom you get from implementing your |
| 16 |
own LinkageMap is that you don't have to 'if' so much. Also, you can |
| 17 |
use your own data file (NEEDED.XXXX.VER) if necessary. Reusing the ELF |
| 18 |
or MACHO ones for another format is really ugly. |
| 19 |
|
| 20 |
|
| 21 |
-- |
| 22 |
Fabian Groffen |
| 23 |
Gentoo on a different level |
Archives