On Tue, 26 Mar 2019 15:35:28 +0200 "Yordan Karadzhov (VMware)" <y.karadz@xxxxxxxxx> wrote: > > I really don't want any build artifacts in the executable. This will > > mean that you need to do special arrangements to build kernelshark and > > then move it to another machine. > > I am confused. I do not know how we can make possible to build > kernelshark on one machine and then move it to another machine and > guarantee that it will work. Note that trace-cmd is not the only > external dependency. We depend on OpenGL, Qt, .... > > Qt itself depends on big number of things. > > Is this really doable? Yes, I've done it myself several times. One only needs the "-dev" packages to build kernelshark. But if you want to run it, you just need the normal packages. I have those packages installed on several machines. In fact, I may only want to build kernelshark on one box, and then copy it to other boxes that don't have the "-dev" packages. There's also a case for cross compiling, where Qt, OpenGL and others are already installed on those other boxes. Package managers will let you know this is done all the time, right Patrick? ;-) -- Steve
|