#45170: gtk-doc: remove source-highlight dependency or make it optional ---------------------------+---------------------- Reporter: ryandesign@… | Owner: devans@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: gtk-doc | ---------------------------+---------------------- Comment (by egall@…): iirc, source-highlight is just one of multiple highlighting options that gtk-doc can use. The others are: * Just-plain "highlight" (whose port also has a dependency on boost) * `vim` (not sure if we'd need to use the port for it, or if the system one works) * maybe one other? Anyways, sounds like a case where variants would make sense... -- Ticket URL: <https://trac.macports.org/ticket/45170#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X

#45170: gtk-doc: remove source-highlight dependency or make it optional ---------------------------+---------------------- Reporter: ryandesign@… | Owner: devans@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: gtk-doc | ---------------------------+---------------------- Comment (by devans@…): Although source highlighting is technically optional in gtk-doc, it is used extensively in GNOME API docs so I'm not so enthusiastic about just turning it off. As stated above, the problems are * source highlighting is a build option for vim and so is not always enabled. This may also be version dependent. At any rate, the vim port has the circular dependency problem (can this be fixed?). * source-highlight and highlight both use boost. Even if we avoid using these, there are other boost based ports (e.g. inkscape, gimp2) which must not build on the earlier platforms if boost won't build there (but I haven't heard any complaints and don't have an appropriate test environment). The gtk-doc configure file prefers source-highlight and is least happy about vim hence the current choice. The earlier version of the port (without source-highlight) did not disable source highlighting so configuration fell back to system vim if source-highlight or highlight were not used. I'm not sure if disabling source highlighting altogether will just eliminate the highlighting from generated documentation or cause a build failure. Will take a look. Best would be to fix boost on the earlier platforms but I realize that may be problematic. Otherwise, looks like disabling source highlighting on 10.5 and earlier may be the least offensive alternative if it doesn't break anything. -- Ticket URL: <https://trac.macports.org/ticket/45170#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X

#45170: gtk-doc: remove source-highlight dependency or make it optional ---------------------------+---------------------- Reporter: ryandesign@… | Owner: devans@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: gtk-doc | ---------------------------+---------------------- Comment (by ryandesign@…): Unfortunately fixing boost to build on older systems may be difficult. The boost portfile blacklists all compilers included in Xcode on those versions of OS X, and even some older clang ports, and newer clang ports don't build on older systems and Jeremy doesn't plan to fix that either. Using a gcc port may still be a possibility though that implies mixing the system's libstdc++ with libgcc's libstdc++ which can be problematic. -- Ticket URL: <https://trac.macports.org/ticket/45170#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X

#45170: gtk-doc: remove source-highlight dependency or make it optional ---------------------------+---------------------- Reporter: ryandesign@… | Owner: devans@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: haspatch Port: gtk-doc | ---------------------------+---------------------- Comment (by ryandesign@…): Thanks. Let's hold off on this for a moment. I believe I was able to fix boost for Tiger and Leopard just by removing the gcc 4.2 blacklisting; apparently whatever was preventing earlier versions from building with gcc 4.2 is no longer a problem. -- Ticket URL: <https://trac.macports.org/ticket/45170#comment:8> MacPorts <http://www.macports.org/> Ports system for OS X