Opened 10 years ago
Closed 10 years ago
#46523 closed update (fixed)
Update: swig 3.0.3
| Reported by: | Schamschula (Marius Schamschula) | Owned by: | michaelld (Michael Dickens) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.3.3 |
| Keywords: | haspatch | Cc: | |
| Port: | swig |
Description
swig has been updated to version 3.0.3. New this version:
- Add support for C++11 strongly typed enumerations. - Numerous bug fixes and minor enhancements for C#, D, Go, Java, Javascript, PHP, Perl and Python wrappers.
Attachments (1)
Change History (6)
Changed 10 years ago by Schamschula (Marius Schamschula)
| Attachment: | Portfile-swig.diff added |
|---|
comment:1 Changed 10 years ago by michaelld (Michael Dickens)
comment:2 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | michaelld@… removed |
|---|---|
| Owner: | changed from macports-tickets@… to michaelld@… |
comment:4 Changed 10 years ago by michaelld (Michael Dickens)
Sorry for not reporting back here. 3.0.4 fixes part of the Python issue, but not all of it. 3.0.5 will fix the whole issue; I'm waiting for them to release it before updating. Anyway, I was told by the SWIG devs that 3.0.5 would be out "shortly" ... no idea what that actually means.
I also have a "swig-devel" set of ports, but there are issues using them because of the way Portfiles implement the "path" dependency concept -- so, I'm not convinced having these devel ports are the way to go. The problem is that I need to use "path:share/swig/VERSION/LANGUAGE:swig-LANGUAGE", without knowing beforehand the VERSION (so, e.g., using "*"). I've worked out a way to do it, but it's not pretty (like using "path..." should be).
comment:5 Changed 10 years ago by michaelld (Michael Dickens)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Updated to 3.0.5 in r132523. I reverted back to the original Portfile before updating; swig-devel is a nice idea, but impractical to implement concisely and without a lot of work. I've no time for a lot of this sort of work ;)
Unfortunately, SWIG 3.0.3 has some issues with the new Python wrappers that make it backward incompatible with 3.0.2. The SWIG devs are working on a fix, and will push 3.0.4 (or 3.0.3.1) out ASAP once everything is verified working. They consider this a critical bug, and I agree because the generated Python wrapper code is not valid (code generated by 3.0.2 might not be easy to read, but at least it works). Once the fixes are in place, I'll update the SWIG ports. See also for more info: http://sourceforge.net/p/swig/mailman/message/33224489/
All of the above said, I'm also trying to get a "swig-devel" set of ports in place for folks wanting to test the most recent commits.