> Maybe instead of adding code to a port as a portgroup, it's a post-process
> step run by MacPorts main that looks for all *.dylib, *.so and executables,
> gets the debugging symbols from them and drops them into
> ${prefix}/lib/debug. This way it's not associated with the port itself.
>
> In fact, this seems much cleaner. Instead of making it a +debug option, it
> can be a macports.conf option.
Not bad, but how would a port be built with "-O0 -g"? I find that a
lot of times variables are optimized out during a gdb session.
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
