Open Analyzer report in browser after generating it
Closes#104
See merge request eng/ide/gnatstudio!271
(cherry picked from commit d966a569ee)
ef8431b7 Open Analyzer report in browser after generating it
Replace use of "CodePeer" in pragma Annotate and review dialog
Closes#87
See merge request eng/ide/gnatstudio!275
(cherry picked from commit 646e2c76a8)
e6f62c3a Replace use of "CodePeer" in pragma Annotate and review dialog
Fix Codepeer object dir computation
See merge request eng/ide/gnatstudio!278
(cherry picked from commit 47bd686f37)
b94fe50d Fix Codepeer object dir computation
Quickfix for Analyzer'Switches attribute:
It's too different between Codepeer and Analyzer.
Fix Object_Dir, the Build Target was adding "codepeer" in the path.
We need to do it manually for gnatsas.
(cherry picked from commit 11c424b427)
- Don't use a special build mode for gnatsas (update Object_Dir
computation to reflect it)
- Add action to load and display SAM baseline
- Replace calls of cpm_bridge by gnatsas review
(cherry picked from commit ac195ba8d8)
- Fix project attributes: they need to be computed on the fly.
- Load GNATSAS module earlier: to properly set Is_GNATSAS as soon
as possible.
- Fix contextual action "GNATSAS/Hide Messages"
- Remove SCIL action/menu for GNATSAS
(cherry picked from commit 50834b557a)
- Display => use a different executable
- HTML/CVS => replace by a run of gnatsas report
- Regenerate Report => it was using the old codepeer target
- Log => use gnatsas.log
(cherry picked from commit e28ea7548c)
- Remove switches like compiler-mode
- Separate Run in 2 phases: analyze and then report
- CPL is no longer supported, reuse part of it for GNATSAS
- Handle path not yet transitioned to GNATSAS
- Create Actions and menu for GNATSAS
- Only show Codepeer when GNATSAS is not available
eng/ide/gnatstudio#54
(cherry picked from commit 36079ee283)
In Inspector, BT library is used by BE.Backtraces.Xml_Files to write
XML files with backtraces and Inspector values. In GNAT Studio, BT
library is used to read XML files with Inspector values.
There was one copy of the library in Inspector's repo and one in GS
repo and these two copies were supposed to be manually synchronized.
However, since there is only a little intersection between the part
of the library used in Inspector and in GS, we decided to split the
library into two parts - Inspector part and GS part and to stop
synchronizing these systematically.
This commit puts comments to the parts of the splitted library that
still needs to synchronized, but it is very unlikely that these
will need to be modified. Here is the list of sources with some
intersection between Inspector and GS part:
bt.ads
- small part of the file containing the definition of source code
position; very unlikely need to be synchronized
bt-xml.{abs, adb}
- definitions of names of XML entities and attributes + the function
Xml_Vals_File_Name
Then, this commit makes the following changes:
* bt-xml-reader.{adb, ads} - keep only the part necessary for
reading XML files with Inspector values
* bt.adb - remove - not used in GS
* bt.ads - keep only types representing source positions and values
of value numbers
* bt-xml.{adb, ads} - keep only string constants for names of XML
entities and attributes necessary to read XML files with Inspector
values, keep the function Xml_Vals_File_Name
* message_kinds.{adb, ads} - remove - not used by GS
Opening a buffer without a view leaves the responsibility to the
caller to close the buffer manually.
=> this is unsafe: either we are closing a buffer shared
somewhere else or forgetting to close it (= leaking it)
The solution is to always use Buffer_Holder.
This commit patches GS in order to support gnatsas at minima, through
the actual codepeer menu, before the new gnatsas menu.
(cherry picked from commit aa906c22d0)
