> >> +obj-unicore32-y += softmmu.o > >> + > > > > You need to rebase this and put this line (actually > > obj-$(CONFIG_SOFTMMU) += softmmu.o) in > > target-unicore32/Makefile.objs. > > Noticed this, too. I wonder if Xuetao could place the new puv3.c > machine file into hw/unicore32/ now, if he wanted? > The devices now compiled through hw/Makefile.objs should probably > remain in hw/? Or is it acceptable to have "unicore32/puv3.o" in > hw/Makefile.objs with the new build system? > > General design question. :)
In my intention, having device model sources in hw/TARGET would be mostly limited to boards and other special cases like interrupt controllers. All other devices should gain a CONFIG_* symbol and be moved to hw/Makefile.objs, like you did with the Xilinx stuff recently. Having common-obj-y or hw-obj-y definitions in Makefiles named according to the target still could make sense for boards/PICs if you are building your target multiple times (e.g. with different endianness). Paolo