On 9/14/19 7:35 AM, Julia Lawall wrote: > > > On Sat, 14 Sep 2019, Rohit Sarkar wrote: > >> On Sat, Sep 14, 2019 at 07:57:48AM +0200, Julia Lawall wrote: >>> >>> >>> On Sat, 14 Sep 2019, Jay Aurabind wrote: >>> >>>> Hi Rohit, >>>> >>>> The required config options need to the objects in that folder to be >>>> build. Apparently there is no way to automatically set the required >>>> configs. You can look at the Kconfig files inside drivers/iio/accel >>>> and see what are the dependencies for building various drivers. >>> >>> It looks like some of the drivers are individual files. So you can also >>> just compile them one at a time make staging/drivers.iio/accel/foo.o. >>> >>> julia >>> >> >> Hey julia, >> I ran a `make clean` on that directory by mistake which I realised I >> shouldn't have done. Hence no object files are there. >> >> Giving me this: >> >> ` >> make drivers/staging/iio/adis16240.o staging/git/remove-include >> CALL scripts/checksyscalls.sh >> CALL scripts/atomic/check-atomics.sh >> DESCEND objtool >> make[1]: *** No rule to make target 'drivers/staging/iio/adis16240.o'. Stop. >> Makefile:1772: recipe for target 'drivers/staging/iio/adis16240.o' failed >> make: *** [drivers/staging/iio/adis16240.o] Error 2 >> ` > > OK > >> I guess I will have to enable `CONFIG_IIO` and rebuild? >> Although what I don't understand is if `CONFIG_IIO` was not enabled how >> were there object files in the first place? > > Perhaps the build system is just not very well designed here. > > However, for me > > make allyesconfig That 'allyesconfig' enables CONFIG_IIO. > make drivers/staging/iio/ > > works, and after that it is possible to do: > > make drivers/staging/iio/accel/adis16203.o > > I didn't do anything explicitly with CONFIG_IIO. > > julia > -- ~Randy
