Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #31940
| Date | 2012-10-23 17:40 +0100 |
|---|---|
| From | MRAB <python@mrabarnett.plus.com> |
| Subject | Re: Compiling extension module (linker error) |
| References | <CAK38ikTsrBj_GsC35uedk0PWaFGGXek+VFT=AfUqqC9-PfFr6g@mail.gmail.com> <50858A59.5070307@mrabarnett.plus.com> <CAK38ikT4rx79TC2QQF7pvVnwHDiHpCN_Y0RCt4k+drf_VxNsXg@mail.gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.2673.1351010435.27098.python-list@python.org> (permalink) |
On 2012-10-23 08:00, Paul Volkov wrote: > 2012/10/22 MRAB <python@mrabarnett.plus.com>: >> By the way, the recommendation is for module names to be lowercase with >> underscores, so "fund_rose" instead of "FundRose". >> >> Try this code: >> > > I tried as you suggested, but the linker error (unresolved external) > is still there. I found a reference to PyModule_Create2TraceRefs in include\modsupport.h. > I'm sure python33.lib is properly added because if I remove it, there > are 3 errors, not 1. > By the way, what is the difference between python3.lib and python33.lib? > I don't know.
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Compiling extension module (linker error) MRAB <python@mrabarnett.plus.com> - 2012-10-23 17:40 +0100
csiph-web