Adding support to include detected configuration makefile
into the build process. This will allow the Build objects
to be configurable based on the config data, like:
perf-$(CONFIG_KRAVA) += krava.o
The configuration is stored in '.config-detected' file,
which is generated for each compilation.
Adding support to include detected configuration makefile
into the build process. This will allow the Build objects
to be configurable based on the config data, like:
perf-$(CONFIG_KRAVA) += krava.o
The configuration is stored in '.config-detected' file,
which is generated for each compilation.
On Thu, Jan 15, 2015 at 08:50:40AM -0700, David Ahern wrote:
> On 1/15/15 5:54 AM, Jiri Olsa wrote:
> >Adding support to include detected configuration makefile
> >into the build process. This will allow the Build objects
> >to be configurable based on the config data, like:
> >
> > perf-$(CONFIG
On 1/15/15 5:54 AM, Jiri Olsa wrote:
Adding support to include detected configuration makefile
into the build process. This will allow the Build objects
to be configurable based on the config data, like:
perf-$(CONFIG_KRAVA) += krava.o
The configuration is stored in '.config-detected' file,
Adding support to include detected configuration makefile
into the build process. This will allow the Build objects
to be configurable based on the config data, like:
perf-$(CONFIG_KRAVA) += krava.o
The configuration is stored in '.config-detected' file,
which is generated for each compilation.
5 matches
Mail list logo
