summaryrefslogtreecommitdiff
path: root/support/sdbinutils/bfd/version.h
diff options
context:
space:
mode:
authorXavier ASUS <xavi92psx@gmail.com>2019-10-18 00:31:54 +0200
committerXavier ASUS <xavi92psx@gmail.com>2019-10-18 00:31:54 +0200
commit268a53de823a6750d6256ee1fb1e7707b4b45740 (patch)
tree42c1799a9a82b2f7d9790ee9fe181d72a7274751 /support/sdbinutils/bfd/version.h
downloadsdcc-gas-268a53de823a6750d6256ee1fb1e7707b4b45740.tar.gz
sdcc-3.9.0 fork implementing GNU assembler syntax
This fork aims to provide better support for stm8-binutils
Diffstat (limited to 'support/sdbinutils/bfd/version.h')
-rw-r--r--support/sdbinutils/bfd/version.h22
1 files changed, 22 insertions, 0 deletions
diff --git a/support/sdbinutils/bfd/version.h b/support/sdbinutils/bfd/version.h
new file mode 100644
index 0000000..3d00b31
--- /dev/null
+++ b/support/sdbinutils/bfd/version.h
@@ -0,0 +1,22 @@
+/* The date below is automatically updated every day by a bot. During
+ development, we include the date in the tools' version strings
+ (visible in 'ld -v' etc.) because people build binutils from a
+ variety of sources - git, tarballs, distro sources - and we want
+ something that can easily identify the source they used when they
+ report bugs. The bfd version plus date is usually good enough for
+ that purpose.
+
+ During development, this date ends up in libbfd and libopcodes
+ sonames because people naturally expect shared libraries with the
+ same soname to have compatible ABIs. We could bump the bfd version
+ on every ABI change, but that's just another thing contributors and
+ maintainers would need to remember. Instead, it's much easier for
+ all if the soname contains the date. This is not perfect but is
+ good enough.
+
+ In releases, the date is not included in either version strings or
+ sonames. */
+#define BFD_VERSION_DATE 20180127
+#define BFD_VERSION @bfd_version@
+#define BFD_VERSION_STRING @bfd_version_package@ @bfd_version_string@
+#define REPORT_BUGS_TO @report_bugs_to@