> Sam Ravnborg wrote: > >> The big issue with Kerntypes is that to be complete you need to link in >> files from different places. >> To create just a single Kerntypes.o file you can add the following to >> kernel/Makefile, drivers/Makefile or similar. > > no good way to do multiple .o's though? The challenge here is to know when all .o files are valid. Think of a make -j 64 scenario. Some of the big iron machine uses this now and then.
You could link the .o files together in boot/Makefile. At this point in time the rest of the kernel tree is visited. Use the same trick as before with always, but replace $(CC) with $(LD) and use appropriate flags. Sam ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click _______________________________________________ kbuild-devel mailing list kbuild-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kbuild-devel
