On 26 September 2013 01:29, Fabien Chouteau <chout...@adacore.com> wrote: > On 09/25/2013 05:51 PM, Peter Maydell wrote: >> On 26 September 2013 00:38, Fabien Chouteau <chout...@adacore.com> wrote: >> It doesn't matter very much, but monitor.h seems the obvious >> place. You probably don't want qom/cpu.h to have to drag in >> monitor.h so a 'struct MonitorDef;' forward declaration in cpu.h >> will let you avoid that (we do that already for a few other structs). > > I think that's what I did. I think the problem was to include > 'monitor.h' in 'target-*/cpu.c'.
Why doesn't that work? In any case, you just need to disentangle stuff so you can get the right definitions and function prototypes available to the target specific code. We could have a target-*/monitor.c if that's an easier approach -- we already have a gdbstub.c, for example. -- PMM
