Uploaded image for project: 'Qt Creator'
  1. Qt Creator
  2. QTCREATORBUG-11076

Request to export GccParser and ClangParser

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Invalid
    • Not Evaluated
    • None
    • None
    • None
    • Qt 5+
      Qt Creator 3+
      Linux 64-bit
      GCC 4.8+
      Clang 3+

    Description

      This is follow up to my question on ml
      ProjectExplorer::GccParser not exported?, whereas GnuMakeParser is exported.

      I received answer that

      Symbols are typically exported on an as-needed basis. If you have a
      sensible use case, formerly private things can be made public (...)

      I would like to argue, there is 'market' for those parsers and plugins like managers for new build systems could happily make use of those.
      An alternative is to copy those parsers from Qt Creator codebase into a plugin codebase, which is not optimal for long term maintenance.

      For example, I started developing a plugin to add Boost.Build support:
      https://github.com/mloskot/qt-creator-plugin-boostbuild
      where I use GccParser, ClangParser and LdParser, and in future I'd like to use parsers for all toolsets supported by Qt Creator.

      So, it would be helpful if there was a tradition of exporting the concrete parsers.

      Attachments

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

        Activity

          People

            dt Daniel Teske
            mloskot Mateusz Loskot
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes