I'm not sure I understand your question-- If you're using gbs as your build tool, only packages with updates will be rebuilt. Is that what you are asking for?
Paul Paul Hanchett ------------------- Infotainment Engineer MSX on behalf of Jaguar Land Rover One World Trade Center, 121 Southwest Salmon Street, 11th Floor, Portland, Oregon, 97204 Email: phanc...@jaguarlandrover.com ------------------- Business Details: Jaguar Land Rover Limited Registered Office: Abbey Road, Whitley, Coventry CV3 4LF Registered in England No: 1672070 On Tue, Feb 4, 2014 at 8:18 PM, Madhu Kumar <gogetit2...@gmail.com> wrote: > Hi All, > > Is it a workable solution to use the already built RPMS packages in the > subsequent builds and reduce the over all build time? > For example, we know that toolchain packages also gets built when we build > Tizen platform sources. Is it possible to re-use these toolchain built RPMS > (from the very first build) in another new system so that the overall build > time there gets reduced? > > Below is what I tried and was not successful. After analysis of the build > time, observed that webkit-efl package takes long time build. I tried > excluding this package from the build and observed that overall packages to > built came to around 410. Tried building it but many packages failed to > build giving "error nothing provides" :( > > My idea is to reuse some of the built RPMS and other components, obtained > from the fresh build, and reduce the over all build time on a new system. > > Please provide any inputs or pointers for the same. > > Thanks in advance. > > > _______________________________________________ > Application-dev mailing list > Application-dev@lists.tizen.org > https://lists.tizen.org/listinfo/application-dev > >
_______________________________________________ Application-dev mailing list Application-dev@lists.tizen.org https://lists.tizen.org/listinfo/application-dev
