Message144162
| Author |
amaury.forgeotdarc |
| Recipients |
Christophe Simonis, Garen, Nam.Nguyen, amaury.forgeotdarc, arekm, asvetlov, barry, doko, eric.araujo, georg.brandl, jcea, jeremybanks, lars.gustaebel, leonov, loewis, nadeem.vawda, nicdumz, nikratio, ockham-razor, pitrou, proyvind, rcoyner, shirish, strombrg, thedjatclubrock, tshepang, ysj.ray |
| Date |
2011年09月16日.21:15:00 |
| SpamBayes Score |
7.4156503e-10 |
| Marked as misclassified |
No |
| Message-id |
<1316207701.26.0.62836662317.issue6715@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I'm a bit worried by the Windows version:
- liblzma can't be compiled by Visual Studio: too many C99 isms, mostly variables declared in the middle of a block. It's doable for sure, but it's a lot of work.
- liblzma is normally compiled with mingw, but we have to be sure that is uses the correct MSCRT C runtime, and what about debug builds?
- All extension modules use static libraries: zlib, expat, sqlite. But a gcc static library can't be used by Visual Studio.
- The way recommended by XZ is to use a precompiled liblzma.dll; Then it should be easy to build an extension module, but its would be the first time that we distribute an extension module which needs a non-system DLL. Is it enough to copy it next to _lzma.pyd? Is there some work to do in the installer?
Too many "but"s :) |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2011年09月16日 21:15:01 | amaury.forgeotdarc | set | recipients:
+ amaury.forgeotdarc, loewis, barry, georg.brandl, doko, jcea, arekm, lars.gustaebel, pitrou, nadeem.vawda, nicdumz, eric.araujo, Christophe Simonis, rcoyner, proyvind, asvetlov, nikratio, leonov, Garen, ysj.ray, thedjatclubrock, ockham-razor, strombrg, shirish, tshepang, jeremybanks, Nam.Nguyen |
| 2011年09月16日 21:15:01 | amaury.forgeotdarc | set | messageid: <1316207701.26.0.62836662317.issue6715@psf.upfronthosting.co.za> |
| 2011年09月16日 21:15:00 | amaury.forgeotdarc | link | issue6715 messages |
| 2011年09月16日 21:15:00 | amaury.forgeotdarc | create |
|