Opened 17 years ago
Closed 16 years ago
#1958 closed defect (fixed)
Building python bindings with Visual C++ fails in debug mode
| Reported by: | Mateusz Łoskot | Owned by: | Mateusz Łoskot |
|---|---|---|---|
| Priority: | high | Milestone: | 1.5.0 |
| Component: | ConfigBuild | Version: | svn-trunk |
| Severity: | critical | Keywords: | nmake visualc++ python debug |
| Cc: |
Description
Last update int nmake.opt file (r12549) added more debug flags and linking to debug version of run-time libraries additional. After these changes, linker throws following error when building Python bindings with Visual C++ (Visual C++ 8.0 in this case):
LINK : fatal error LNK1104: cannot open file 'python24_d.lib'
There is no python24_d.py shipped in the official Python distribution.
Change History (5)
comment:1 by , 17 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 17 years ago
| Milestone: | → 1.5.0 |
|---|
comment:3 by , 17 years ago
Deeper discussion on the #gdal channel with Frank and Hobu led is to better solution. We've decided to build Python bindings always in optimized mode, regardless of global settings in nmake.opt. New patch is under construction.
comment:4 by , 17 years ago
Fixed gdal_array.h so that builds are unbusted when numpy is available (r12597).
Note:
See TracTickets
for help on using tickets.
Applied patch solving the problem (r12592) but there is still uncertain how SWIG will handle it, perhaps it will overwrite these changes.