summaryrefslogtreecommitdiff
path: root/misc/abi-compliance-checker.txt
diff options
context:
space:
mode:
authorAlbrecht Schlosser <albrechts.fltk@online.de>2020-07-01 18:03:10 +0200
committerAlbrecht Schlosser <albrechts.fltk@online.de>2020-07-06 20:28:20 +0200
commitf09e17c3c564e8310125a10c03397cbf473ff643 (patch)
tree8d0fd4a28e3686c33aaa140d07ddba26ab28bdc2 /misc/abi-compliance-checker.txt
parentb0e0c355edaa2e23148cb0260ada907aec930f05 (diff)
Remove $Id$ tags, update URL's, and more
- remove obsolete svn '$Id$' tags from all source files - update .fl files and generated files accordingly - replace 'http://www.fltk.org' URL's with 'https://...' - replace bug report URL 'str.php' with 'bugs.php' - remove trailing whitespace - fix other whitespace errors flagged by Git - add and/or fix missing or wrong standard headers - convert tabs to spaces in all source files The only relevant code changes are in the fluid/ folder where some .fl files and other source files were used to generate the '$Id' headers and footers.
Diffstat (limited to 'misc/abi-compliance-checker.txt')
-rw-r--r--misc/abi-compliance-checker.txt74
1 files changed, 37 insertions, 37 deletions
diff --git a/misc/abi-compliance-checker.txt b/misc/abi-compliance-checker.txt
index 097daeedb..649878ecc 100644
--- a/misc/abi-compliance-checker.txt
+++ b/misc/abi-compliance-checker.txt
@@ -20,17 +20,17 @@ with the current version (1.3.5) before it will be released.
(2) Use two different Git checkout (working) directories to build libs,
for instance (as used in this example):
- (new) /git/fltk-1.3 current version = 1.3.5
- (old) /git/fltk-1.3.4-1 previous version = 1.3.4-1 [1]
+ (new) /git/fltk-1.3 current version = 1.3.5
+ (old) /git/fltk-1.3.4-1 previous version = 1.3.4-1 [1]
[1] The second working directory can be created from the first
- git working tree ( /git/fltk-1.3 ) with these commands:
+ git working tree ( /git/fltk-1.3 ) with these commands:
- $ cd /git/fltk-1.3
- $ git worktree add /git/fltk-1.3.4-1 release-1.3.4-1
+ $ cd /git/fltk-1.3
+ $ git worktree add /git/fltk-1.3.4-1 release-1.3.4-1
- This creates the worktree in /git/fltk-1.3.4-1 and checks the
- tag 'release-1.3.4-1' out.
+ This creates the worktree in /git/fltk-1.3.4-1 and checks the
+ tag 'release-1.3.4-1' out.
(3) Create two xml descriptions to test library compatibility in
@@ -94,31 +94,31 @@ with the current version (1.3.5) before it will be released.
$ cd /git/workdir
$ /git/abi-compliance-checker/abi-compliance-checker.pl \
-lib fltk -old fltk-1.3.4-1.xml -new fltk-1.3.5.xml
- Preparing, please wait ...
- Using GCC 7 (x86_64-linux-gnu, target: x86_64)
- WARNING: May not work properly with GCC 4.8.[0-2], 6.* and higher
- due to bug #78040 in GCC. Please try other GCC versions with the
- help of --gcc-path=PATH option or create ABI dumps by ABI Dumper
- tool instead to avoid using GCC. Test selected GCC version first
- by -test option.
- ------------------------------------------------------------------
- --> ignore warning (but run `abi-compliance-checker.pl -test')
- ------------------------------------------------------------------
- Checking header(s) 1.3.4-1 ...
- WARNING: can't find 'ctags' program
- Checking header(s) 1.3.5 ...
- WARNING: can't find 'ctags' program
- ------------------------------------------------------------------
- --> ignore warning (or install 'ctags' and repeat)
- ------------------------------------------------------------------
- Comparing ABIs ...
- Comparing APIs ...
- Creating compatibility report ...
- Binary compatibility: 100%
- Source compatibility: 100%
- Total binary compatibility problems: 0, warnings: 0
- Total source compatibility problems: 0, warnings: 1
- Report: compat_reports/fltk/1.3.4-1_to_1.3.5/compat_report.html
+ Preparing, please wait ...
+ Using GCC 7 (x86_64-linux-gnu, target: x86_64)
+ WARNING: May not work properly with GCC 4.8.[0-2], 6.* and higher
+ due to bug #78040 in GCC. Please try other GCC versions with the
+ help of --gcc-path=PATH option or create ABI dumps by ABI Dumper
+ tool instead to avoid using GCC. Test selected GCC version first
+ by -test option.
+ ------------------------------------------------------------------
+ --> ignore warning (but run `abi-compliance-checker.pl -test')
+ ------------------------------------------------------------------
+ Checking header(s) 1.3.4-1 ...
+ WARNING: can't find 'ctags' program
+ Checking header(s) 1.3.5 ...
+ WARNING: can't find 'ctags' program
+ ------------------------------------------------------------------
+ --> ignore warning (or install 'ctags' and repeat)
+ ------------------------------------------------------------------
+ Comparing ABIs ...
+ Comparing APIs ...
+ Creating compatibility report ...
+ Binary compatibility: 100%
+ Source compatibility: 100%
+ Total binary compatibility problems: 0, warnings: 0
+ Total source compatibility problems: 0, warnings: 1
+ Report: compat_reports/fltk/1.3.4-1_to_1.3.5/compat_report.html
(6) Check the generated report (last line above) with a browser:
@@ -135,9 +135,9 @@ with the current version (1.3.5) before it will be released.
(8) Done.
-Note 1: The report as given above issued 100% ABI compatibility. The only
- warning was the different patch version number.
+Note 1: The report as given above issued 100% ABI compatibility. The only
+ warning was the different patch version number.
-Note 2: There are other recommended methods to use abi-compliance-checker
- together with abi-dumper, but this is not (yet) covered here (see
- abi-compliance-checker documentation).
+Note 2: There are other recommended methods to use abi-compliance-checker
+ together with abi-dumper, but this is not (yet) covered here (see
+ abi-compliance-checker documentation).