Eric, target.list is used only for the verification, it does not replace functionality of the of "configure" or "Makefile". When everything is "installed" (on the host computer), the build script make a list of the installed files and directories, creates target.list.new and diff-s it with the saved target.list reporting any differences. The new built image includes archived source tree (as in /* source is inside */), and that archive has the target.list matching the archived source, so if you build from that archive - target.list should match.
We did have problems when some files were missing on the host computer, and ion the result the built system mas missing some needed files. Of course, the problems were reported in some long build.log files, but it was difficult to notice them. That was why we implemented the target.list - just to make sure all the files that were supposed to be installed are actually installed. Andrey On Fri, Feb 24, 2012 at 2:00 AM, Eric Boudrand <e...@boudrand.net> wrote: > Hi, > > >> 2) target.list - if new files are installed. This file is >> automatically generated (under the name target.list.new) each time you >> re-build the software, and the script reports differences between >> target.list and target.list.new. > > > I do not understand how it works. I added files into two directories > (/lib/firmware and /lib/modules/2.6.19/kernel/net/wireless) in target.list > but when I run "make" the directories are not created. > > I am trying to compile driver for Wifi USB adapter DWA-131. > > Regards. > > Eric > > > > _______________________________________________ > Support-list mailing list > Support-list@support.elphel.com > http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com _______________________________________________ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com