Summary: | break off QT related functions into qt.eclass | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | SpanKY <vapier> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 18661 | ||
Bug Blocks: |
Description
SpanKY
2003-09-14 23:39:59 UTC
You can do all this already with kde-functions.eclass. It doesn't include any global-section code, so the kde-related functions there are harmless. # add requested version to DEPEND and stuff inherit kde-functions; need-qt $VER # return the base qt dir ... if [version number] is not specified, default to # whatever is in installed, or to latest version if more than 1 is installed inherit kde-functions; set-qtdir $VER; now $QTDIR is set. Ugly, yes, and if you really want one we can add a wrapper # similar to above as above, use $QTDIR/include If any of the above isn't good enough, why? # get qt cflags If you just need to get the cflags necessary to compile a QT app, then AFAIK just using -I$QTDIR/include should always work. (You do need to add $QTDIR/bin to the beginning of PATH to make sure to use the correct moc and uic.) Otherwise we'd need a qt pkg-config file or a qt-config utility. Opinions? yeah, ive realized this over time but just forgot about this bug as far as i'm concerned, kde-functions does everything i need |