3) lots of RAM and a fast SSD/NVMe drive 4) ensure ccache is configured and in-use On Mon, Jan 16, 2017 at 2:51 PM, Igor Fedotov <ifedotov@xxxxxxxxxxxx> wrote: > My best choices are: > > 1) Use -j switch for make > > 2) Make specific target(s) only, e.g. some UT for the code I'm working on > and proceed with the full build when most of the patch is ready. > > > > On 1/16/2017 10:19 PM, Victor Denisov wrote: >> >> Cephers, >> >> Could you please give me some advice on how to have a faster turn >> around for change - compile process. Currently I usually do a change >> and then compile which often takes quite a while and gets in the way >> of being in the flow. I'm trying to mitigate it by changing as big >> chunks as possible before compiling, but it's not a very pleasant >> experience. So, I thought may be you could share your experience. >> >> Thanks in advance. >> Victor. >> -- >> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html > > > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Jason -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
