Message74758
| Author |
aheider |
| Recipients |
aheider, loewis |
| Date |
2008年10月14日.17:57:14 |
| SpamBayes Score |
4.2908393e-08 |
| Marked as misclassified |
No |
| Message-id |
<1224007041.21.0.0167658397735.issue4120@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Ok, point taken, so lets aim at v2.6. Should i open a new issue then?
Attached you'll find a new diff against v2.6. This time pyd_d.vsprops
gets patched too and the linker doesn't even generate a .manifest file.
So no, the *.pyd files do not get any manifest info, neither a loose
*.pyd.manifest nor an embedded one.
I checked a per-user v2.6 install with the CRT manifest pointing at
"..". I also tried this approach for our software, but i couldn't get it
working on w2k3.
The solution i am proposing doesn't need a CRT manifest file in
"./DLLs". This approach works on w2k3, but i can not test this on vista SP1. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2008年10月14日 17:57:21 | aheider | set | recipients:
+ aheider, loewis |
| 2008年10月14日 17:57:21 | aheider | set | messageid: <1224007041.21.0.0167658397735.issue4120@psf.upfronthosting.co.za> |
| 2008年10月14日 17:57:15 | aheider | link | issue4120 messages |
| 2008年10月14日 17:57:14 | aheider | create |
|