Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #3167
| References | <BANLkTin6W64V30CtFXyT8AZTt2U-nZ1YcA@mail.gmail.com> <BANLkTi=CW4LMmUYr6k=wxZUwMSgweoS-Pw@mail.gmail.com> <BANLkTi=U18x0fqnyDgNFChqUZS=BEsxVsA@mail.gmail.com> <BANLkTimHpZ1jZ711S6_A5bPFZ2C69Qqfew@mail.gmail.com> |
|---|---|
| Date | 2011-04-13 20:35 -0700 |
| Subject | Re: looking for libpython31.a 64bit (missing from python-3.1.3.amd64.msi) |
| From | Nathan Coulson <conathan@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.342.1302752136.9059.python-list@python.org> (permalink) |
On Wed, Apr 13, 2011 at 7:53 PM, David Cournapeau <cournape@gmail.com> wrote: > On Thu, Apr 14, 2011 at 11:28 AM, Nathan Coulson <conathan@gmail.com> wrote: > >> actually figured out a neat trick, mingw-w64 can link directly to the .dll. >> gcc file.c python31.dll -o file.exe >> >> no .a needed. >> >> http://www.mingw.org/wiki/sampleDLL >> >> (have yet to find out if it actually works yet, but so far looks promising) > > Note the "If this method works for your application then there is > usually no need for an import library.". Whether it works or not is > often found the hard way (i.e. you won't have a linking error, but > subtle bugs). Building a .a library is more stable in my experience > (even in 32 bits). > > In any case, note the -DMS_WIN64 which is mandatory if you want to > make it work (without this define, mingw will use the python headers > for 32 bits, with pointers typedef defined for 32 bits pointers > instead of 64 bits, which will not work very well :) ). > > cheers, > > David very good note, had no clue. -- Nathan Coulson (conathan) ------ Location: British Columbia, Canada Timezone: PST (-8) Webpage: http://www.nathancoulson.com
Back to comp.lang.python | Previous | Next | Find similar
Re: looking for libpython31.a 64bit (missing from python-3.1.3.amd64.msi) Nathan Coulson <conathan@gmail.com> - 2011-04-13 20:35 -0700
csiph-web