Skip to content
Snippets Groups Projects
  1. Sep 15, 2010
    • Tobias Hunger's avatar
      Parser debugging/testing improvements · 0204ef21
      Tobias Hunger authored
       * Set objectname on all parsers to be able to distinguish between
         them more easily when debugging
       * Add some unit tests about pass-through of data we need in the
         gcc parser to the parsers that enhd up in front of the gcc parser
         This is to address QTCREATORBUG-1917.
      0204ef21
  2. Mar 12, 2010
  3. Mar 05, 2010
  4. Jan 11, 2010
  5. Dec 09, 2009
    • Tobias Hunger's avatar
      Rework Build Parser handling · ec025c6d
      Tobias Hunger authored
       * Rework IBuildParser:
          * Remove name() method.
          * Remove enterDirectory and leaveDirectory signals.
          * Allow chaining of parsers.
       * Rename IBuildParser to IOutputParser.
       * Implement GnuMakeParser.
          * Remove entering/leaving directory related code from all other parsers
          * Move filename fixup heuristic based on entering/leaving directory
            massages from gnumake here from AbstractMakeStep.
       * Add outputParser method to ToolChain: This removes the need to map
         toolchains to BuildParser names in the BuildSteps.
       * Enhance AbstractProcessStep to accept a IOutputParser to parse its output.
       * Remove AbstractMakeStep.
       * Set the appropriate Parsers in all classes deriving from AbstractProcessStep
         and append the ToolChain's parser to the parser chain.
       * Remove BuildParserFactories: There is no more need for them.
       * Remove constants used to identify the BuildParsers.
       * Clean up some names:
          * Replace stdOut with stdOutput.
          * Replace addToTaskWindow with addTask and addToOutputWindow with
            addOutput. Do this wherever it is not yet clear that this will end up
            in the Task/Output window.
      
      Reviewed-by: dt
      ec025c6d
  6. Nov 12, 2009
    • Tobias Hunger's avatar
      Use Task class in addToTaskWindow(...) signal. · b2f68033
      Tobias Hunger authored
       * Use Task class in addToTaskWindow(...) signal. This introduces
         support for task categories into the BuildParsers.
       * Add a task category for buildsystem issues.
       * Update existing BuildParsers to new API and assign their
         tasks to the Compile or Buildsystem task category.
      
      Reviewed-By: dt
      b2f68033
  7. Nov 11, 2009
  8. Nov 10, 2009
  9. Nov 09, 2009
Loading