Hi René and Ryan, On 27 Oct 2014, at 01:04 , René J.V. Bertin <[email protected]> wrote: > I've started calling the variant +devel since that discussion. But AFAIC it > doesn't need to be included in an official port …
ok, removing this variant might be a way to go… >> there is a “debug” variant already available due to the kde portgroup... >> Why did you need to introduce a “nostrip” variant? Is that because of >> CMAKE_STRIP:FILEPATH? > > The KDE +debug variant requires qt4-mac +debug, and that's a sort of > frankenmonster I'd prefer to avoid. I see what you mean, of course. :) > It's basically useless, most importantly because AFAIK it doesn't allow > post-mortem debugging. > My variant builds with RelWithDebInfo (as opposed to Release used by normal > MacPorts builds) and takes an extra step to prevent that debug info from > being stripped. I've never been very good with names, so called it +nostrip. Hmm, ok. This is a discussion we started a while ago on MacPorts-devel, but introducing a dedicated debug-kde variant never took off... Ryan, any suggestions? Greets, Marko _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
