[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #55282] QT_CPPFLAGS and QT_LDFLAGS not always

From: Ben Abbott
Subject: [Octave-bug-tracker] [bug #55282] QT_CPPFLAGS and QT_LDFLAGS not always present when needed
Date: Tue, 25 Dec 2018 19:49:32 -0500 (EST)
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_2) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/12.0.2 Safari/605.1.15


                 Summary: QT_CPPFLAGS and QT_LDFLAGS not always present when
                 Project: GNU Octave
            Submitted by: bpabbott
            Submitted on: Tue 25 Dec 2018 07:49:30 PM EST
                Category: Configuration and Build System
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Build Failure
                  Status: None
             Assigned to: None
         Originator Name: Ben Abbott
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any



The use of QT_CPPFLAGS and QT_LDFLAGS isn't consistent. Presently, it is
necessary to include the Qt flags in CPPFLAGS and LDFLAGS.

One example are the several (all?) Qt tests. For example, the test for
QAbstractItemModel::beginResetModel requires that the Qt flags be included in
CPPFLAGS and LDFLAGS or the test will fail.

A second example is compiling __init_qt__. 

I expect this is a fairly easy problem to fix. Can someone point me to where
flags are added to configure tests? And where flags are added for specific


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]