mirror of
https://sourceware.org/git/binutils-gdb.git
synced 2024-12-15 04:31:49 +08:00
7fb45a6895
When configuring with '--enbale-cgen-maint' the default for both the opcodes/ and sim/ directories is to assume that the cgen source is within the binutils-gdb source tree as binutils-gdb/cgen/. In the old cvs days, this worked well, as cgen was just another sub-module of the single cvs repository and could easily be checked out within the binutils-gdb directory, and managed by cvs in the normal way. Now that binutils-gdb is in git, while cgen is still in cvs, placing the cgen respository within the binutils-gdb tree is more troublesome, and it would be nice if the two tools could be kept separate. Luckily there is already some initial code in the configure.ac files for both opcodes/ and sim/ to support having cgen be located outside of the binutils-gdb tree, however, this was speculative code written imagining a future where cgen would be built and installed to some location. Right now there is no install support for cgen, and so the configure code in opcodes/ and sim/ doesn't really do anything useful. In this commit I repurpose this code to allow binutils-gdb to be configured so that it can make use of a cgen source directory that is outside of the binutils-gdb tree. With this commit applied it is now possible to configure and build binutils-gdb like this: /path/to/binutils-gdb/src/configure --enable-cgen-maint=/path/to/cgen/src/cgen/ make all-opcodes make -C opcodes run-cgen-all Just in case anyone is still using cgen inside the binutils-gdb tree, I have left the default behaviour of '--enable-cgen-maint' (with no parameter) unchanged, that is it looks for the cgen directory as 'binutils-gdb/cgen/'. opcodes/ChangeLog: * configure.ac (enable-cgen-maint): Support passing path to cgen source tree. * configure: Regenerate. sim/ChangeLog: * common/acinclude.m4 (enable-cgen-maint): Support passing path to cgen source tree. * cris/configure: Regenerate. * frv/configure: Regenerate. * iq2000/configure: Regenerate. * lm32/configure: Regenerate. * m32r/configure: Regenerate. * or1k/configure: Regenerate. * sh64/configure: Regenerate. |
||
---|---|---|
.. | ||
aclocal.m4 | ||
arch.c | ||
arch.h | ||
ChangeLog | ||
config.in | ||
configure | ||
configure.ac | ||
cpu2.c | ||
cpu2.h | ||
cpu.c | ||
cpu.h | ||
cpuall.h | ||
cpux.c | ||
cpux.h | ||
decode2.c | ||
decode2.h | ||
decode.c | ||
decode.h | ||
decodex.c | ||
decodex.h | ||
dv-m32r_cache.c | ||
dv-m32r_cache.h | ||
dv-m32r_uart.c | ||
dv-m32r_uart.h | ||
m32r2.c | ||
m32r-sim.h | ||
m32r.c | ||
m32rx.c | ||
Makefile.in | ||
mloop2.in | ||
mloop.in | ||
mloopx.in | ||
model2.c | ||
model.c | ||
modelx.c | ||
README | ||
sem2-switch.c | ||
sem-switch.c | ||
sem.c | ||
semx-switch.c | ||
sim-if.c | ||
sim-main.h | ||
syscall.h | ||
traps-linux.c | ||
traps.c |
This is the m32r simulator directory. It is still work-in-progress. The current sources are reasonably well tested and lots of features are in. However, there's lots more yet to come. There are lots of machine generated files in the source directory! They are only generated if you configure with --enable-cgen-maint, similar in behaviour to Makefile.in, configure under automake/autoconf. For details on the generator, see ../../cgen. devo/cgen isn't part of the comp-tools module yet. You'll need to check it out manually (also akin to automake/autoconf).