Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-99048

As a user of a custom Qt build, I want do define my own deprecated-API cutoff version

    XMLWordPrintable

Details

    • User Story
    • Resolution: Duplicate
    • P2: Important
    • None
    • None
    • None

    Description

      We're using a custom Qt build (configure -list-features) to minimize the footprint of the Qt library on our embedded systems. That already helps a lot. However, we're also always working with the latest stable Qt version, and disable deprecated API. However, we don't seem to be able to reap the benefit of that constant porting work, because there doesn't seem to be a way to configure a Qt build with a custom QT_DISABLE_DEPRECATED_BEFORE . Seeing as you now have added that QT_REMOVED_SINCE/removed_api.cpp, we'd really like to be able to say

      confgure -disable-deprecated-before=0x060300
      

      in order to not have to carry all that ABI retained for BC. For us, that's just useless ballast.

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              cnn Qt Core & Network
              mmutz Marc Mutz
              Vladimir Minenko Vladimir Minenko
              Alex Blasche Alex Blasche
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes