Hi Emese, 2016-03-15 5:52 GMT+09:00 Emese Revfy <re.emese@xxxxxxxxx>: > On Fri, 11 Mar 2016 15:25:19 +0900 > Masahiro Yamada <yamada.masahiro@xxxxxxxxxxxxx> wrote: > >> Maybe scripts/gcc-plugins/ is better than tools/gcc ? >> >> In the directory "scripts/", we have several tools used during >> building the kernel image. >> We have some optional programs in the directory "tools/", which are not used >> for building the kernel image itself. >> >> Please correct me if I am wrong. > > I think scripts isn't the right place because there are tools there which don't get used > during the building of vmlinux (e.g., coccinelle, checkpatch). No, this is not what I meant. What I want to say is: All the host tools used for building vmlinux should be located in the directory "scripts/", but the directory may also other host tools that are not used for building vmlinux (such as checkpatch). > The scripts name also doesn't describe gcc plugins well. With my suggestion "scripts/gcc-plugins/", the sub-directory name describes it very well. > Plugins take part in the image building process > in a different way than these tools and scripts do. > Since there doesn't seen to be a good place for compiler plugins, maybe we should create a new toplevel directory > called "build". Compiler plugins and other existing build tools could live there. What do you think? In my understanding, they are plug-in'ed into the cross-compiler that compiles vmlinux. If so, GCC plugins should be happy in "scripts/" because Kbuild descends into "scripts/" before building any objects for vmlinux. -- Best Regards Masahiro Yamada -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
