Menu

#78 SConstruct fails to find static build of QT

version 1.11
closed-out-of-date
5
2007-10-20
2007-10-02
Anonymous
No

The SConstruct function CheckForQtAt (line 84) fails if QT is build statically only.

I'm trying to build Lprof statically on OS X - as a workaround I am making CheckForQtAt always return true.

Actually it is AttemptLinkWithVariables that is causing the trouble, I'm not sure where that comes from.

Cheers
Mark
dev@cinescan.com

Discussion

  • Hal Engel

    Hal Engel - 2007-10-02
    • milestone: --> version 1.11
    • assigned_to: nobody --> hvengel
     
  • Hal Engel

    Hal Engel - 2007-10-02

    Logged In: YES
    user_id=1052244
    Originator: NO

    AttemptLinkWithVariables ends up calling DoWithVariables where it builds a command that looks like this when expanded:

    context.TryLink(""
    #include <qapplication.h>
    int main(int argc, char **argv) {
    QApplication qapp(argc, argv);
    return 0;
    }
    "" , ".cpp")

    context contains the location of Qt (IE. normally the same as QTDIR for most builds). Perhaps it has the wrong QTDIR when only statically linking? Just before the call to AttemptLinkWithVariables you can do

    print QTDIR

    to see what value it is using. If this is not the location of the static Qt installation (or a valid Qt installation) then the call to AttemptLinkWithVariables will fail.

    This Qt checking code is borrowed from another project so I am far from an expert on how it works. But you may be trying to do something for which it will need to be modified to work.

    Since you currently have a work around I will hold off doing anything with this until the other issues you are having are worked out.

     
  • Hal Engel

    Hal Engel - 2007-10-20

    Logged In: YES
    user_id=1052244
    Originator: NO

    Changed how this works. So it should no longer be an issue.

     
  • Hal Engel

    Hal Engel - 2007-10-20
    • status: open --> closed-out-of-date
     

Log in to post a comment.