On Fri, Jan 02, 2015 at 04:35:43PM +0100, Jiri Olsa wrote:
> +a) Build makefiles
> +------------------
> +User supplies 'Build' makefiles that contains objects summary,
> +like for example following 'krava/Build' file:
> +
> + perf-y += a.o
> + perf-y += b.o
> +
> +The build framework is triggered by:
> + $ make -f Makefile.build dir=krava obj=perf
> +
> +which produces 'krava/perf-in.o' object file that has both
> +a.o and b.o objects compiled in linked together.
> +
> +The 'Build' makefile can contains multiple objects definitions
> +to allow building separated binaries, like:
> +
> + perf-y += a.o
> + perf-y += b.o
> +
> + libperf-y += c.o
> + libperf-y += d.o
> +
> +If the build framework is triggered by:
> + $ make -f Makefile.build dir=krava obj=libperf
> +
> +it produces 'krava/libperf-in.o' object file that has both
> +a.o and b.o objects compiled in linked together.
Ok, question: you say those "Build" files are supplied by the user. Does
that mean that everyone has to go and write their own or are we still
using Kconfig and doing it in a more user-friendly manner?
I've probably missed this in the whole perf fastlane development... :)
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
