On Friday 13 November 2009, bjoern michaelsen - Sun Microsystems - Hamburg Germany wrote: > Hi List, > > While working on the Build Environment Effort(1), we stumbled over the > implicit dependency of all modules generating resource files on > default_images. The resource compiler digs into the default_images > directory for the files specified in the *.src/*.hrc files. However, > since there is no need for rsc to actually read the file contents when > generating *.res files, the dependency is much heavier than needed. > After all, everything rsc needs to know is _if_ there is a file with a > given name, but not its contents. > To get rid of this dependency, we are considering to simply generate a > file containing the dirstate of default_images (for example the output > of "find default_images") and put that in the solver. rsc would > use the contents of that file, and would not try to search > default_images directly. > This would: > - reduce dependencies > - for example allow to build sw without having a complete default_images > around > - ease further efforts like split build/better support for full deps > > Opinions?
Interesting idea. The only question is how to generate the list of images. It can't be generated during build because it will not remove the cyclic build dependency. So, you would need to generate it offline which is a bit error prone. Another possibility would be to hack rsc to generate a list of used images and deliver these lists into the solver. The module default_images might be built as a last module and it might check all those delivered lists and throw an error/warning when am image was used but it is not available. -- Best Regards, Petr Mladek software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: [email protected] Lihovarská 1060/12 tel: +420 284 028 952 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
