Messages in this thread | | | Date | Fri, 25 Nov 2011 15:11:10 +0100 | From | Robert Richter <> | Subject | Re: libperf interface stability |
| |
On 25.11.11 09:46:11, Arnaldo Carvalho de Melo wrote: > 1) get the above list of c files except for util/python.c that is just > glue stuff for the python binding and make it the new libperf.a > > 2) make a perf.a that just is libperf.a + the rest of the .c files today > in libperf.a, i.e. perf.a would be the "just for perf tools for now" > bundle > > 3) make the python binding be just this new libperf.a + util/python.c > > 4) make libperf.so.0.0.1 be just what is in this new libperf.a
Yeah, I was thinking about something like this.
-Robert
-- Advanced Micro Devices, Inc. Operating System Research Center
| |