diff options
author | Mike Frysinger <vapier@gentoo.org> | 2023-01-01 17:35:16 -0500 |
---|---|---|
committer | Mike Frysinger <vapier@gentoo.org> | 2023-01-01 17:35:16 -0500 |
commit | 508de6412084dc70a90d60de252edc7d70cbecbf (patch) | |
tree | 87697f302464bb068119ccf4a5ca94f0b97f4d88 /sim/README-HACKING | |
parent | 0d9d77e506c42d48327a10a6ffa18964f54fd064 (diff) | |
download | fsf-binutils-gdb-508de6412084dc70a90d60de252edc7d70cbecbf.zip fsf-binutils-gdb-508de6412084dc70a90d60de252edc7d70cbecbf.tar.gz fsf-binutils-gdb-508de6412084dc70a90d60de252edc7d70cbecbf.tar.bz2 |
sim: drop mention of & support for subdir configure
Now that no ports use these common configure APIs, delete the logic
and remove it from the documentation.
Diffstat (limited to 'sim/README-HACKING')
-rw-r--r-- | sim/README-HACKING | 50 |
1 files changed, 2 insertions, 48 deletions
diff --git a/sim/README-HACKING b/sim/README-HACKING index eddd7d5..d2b2786 100644 --- a/sim/README-HACKING +++ b/sim/README-HACKING @@ -31,24 +31,6 @@ in configure.ac and Makefile.in, and it also provides a foundation for enhancing the simulators uniformly (e.g. the more they share in common the easier a feature added to one is added to all). -The configure.ac of a simulator using the common framework should look like: - ---- snip --- -dnl Process this file with autoconf to produce a configure script. -AC_INIT(Makefile.in) -AC_CONFIG_MACRO_DIRS([../common ../.. ../../config]) - -... target specific additions ... - -SIM_AC_OUTPUT ---- snip --- - -SIM_AC_OUTPUT: - -- creates the symbolic links defined in sim_link_{files,links} -- creates config.h -- creates the Makefile - The Makefile.in of a simulator using the common framework should look like: --- snip --- @@ -81,7 +63,7 @@ SIM_EXTRA_CLEAN = ... target specific rules ... --- snip --- -COMMON_{PRE,POST}_CONFIG_FRAG are markers for SIM_AC_OUTPUT to tell it +COMMON_{PRE,POST}_CONFIG_FRAG are markers for configure to tell it where to insert the two pieces of common/Make-common.in. The resulting Makefile is created by doing autoconf substitions on both the target's Makefile.in and Make-common.in, and inserting @@ -107,35 +89,7 @@ are greppable and appear in the TAGS file. Generating "configure" files ============================ -For targets using the common framework, "configure" can be generated -by running `autoconf'. - -To regenerate the configure files for all targets using the common framework: - - $ cd devo/sim - $ make -f Makefile.in SHELL=/bin/sh autoconf-common - -To add a change-log entry to the ChangeLog file for each updated -directory (WARNING - check the modified new-ChangeLog files before -renaming): - - $ make -f Makefile.in SHELL=/bin/sh autoconf-changelog - $ more */new-ChangeLog - $ make -f Makefile.in SHELL=/bin/sh autoconf-install - -In a similar vein, both the configure and config.in files can be -updated using the sequence: - - $ cd devo/sim - $ make -f Makefile.in SHELL=/bin/sh autoheader-common - $ make -f Makefile.in SHELL=/bin/sh autoheader-changelog - $ more */new-ChangeLog - $ make -f Makefile.in SHELL=/bin/sh autoheader-install - -To add the entries to an alternative ChangeLog file, use: - - $ make ChangeLog=MyChangeLog .... - +"configure" can be generated by running `autoreconf'. C Language Assumptions ====================== |