#197 closed defect (released)
Can't build SWIG on Windows, thus can't build bindings
| Reported by: | Charlie Hull | Owned by: | New Bugs |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Build system | Version: | SVN trunk |
| Severity: | normal | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Operating System: | Microsoft Windows |
Description
We can't successfully build the imported version of SWIG on a Windows system using MSYS. Following the instructions at http://www.swig.org/Doc1.3/Windows.html#swig_exe causes a bug just like this: http://thread.gmane.org/gmane.comp.programming.swig.devel/17218
The workaround is to import the generated files from another system with a working SWIG (for example, xapian-bindings/python/modern).
Change History (8)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
| Status: | new → assigned |
|---|
comment:3 by , 18 years ago
Does this tip help?
http://article.gmane.org/gmane.comp.programming.swig.devel/17467
Not doing that would probably lead to config.status containing carriage returns, with the symptoms you suggest.
comment:5 by , 18 years ago
Ping!
I believe that this should work with the version of SWIG which Xapian's SVN now pulls in. Charlie: can you confirm?
comment:6 by , 18 years ago
Yes, I can now build Swig successfully (sorry for the delay, busy with other things). However I still haven't verified I can build the bindings; I'll try tomorrow and if so close the bug.
comment:7 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Bindings now build successfully on Windows using the supplied SWIG.
comment:8 by , 18 years ago
| Operating System: | → Microsoft Windows |
|---|---|
| Resolution: | fixed → released |

Is your SVN tree under a directory containing a space character? That's not supported.
If not, check the end of line characters in the generated file config.status. The shell might not be happy with CR+LF, so if it has CR strip them out and see if that works, e.g. using:
perl -pi -e 's/\rg' config.status
If that's the issue, we can probably address it.