Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #31940 > unrolled thread
| Started by | MRAB <python@mrabarnett.plus.com> |
|---|---|
| First post | 2012-10-23 17:40 +0100 |
| Last post | 2012-10-23 17:40 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Compiling extension module (linker error) MRAB <python@mrabarnett.plus.com> - 2012-10-23 17:40 +0100
| From | MRAB <python@mrabarnett.plus.com> |
|---|---|
| Date | 2012-10-23 17:40 +0100 |
| Subject | Re: Compiling extension module (linker error) |
| Message-ID | <mailman.2673.1351010435.27098.python-list@python.org> |
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 top | Article view | comp.lang.python
csiph-web