On 15/01/2015 16:56, ISHIKAWA,chiaki wrote: > On 2015/01/15 10:37, Steve Fink wrote: >> On 01/14/2015 11:26 AM, Ehsan Akhgari wrote: >>> From now on, the only supported build mode is unified compilation. I >>> am planning to follow-up with removing support for the >>> --disable-unified-compilation configure option altogether in bug >>> 1121000. >> >> I commented in the bug, but I guess this is probably a better forum. >> >> Why is the configure option being removed? I understand always building >> unified in automation, but not having a straightforward way at all to >> see if your code is buggy seems... suboptimal. If someone wants to go >> through occasionally and make our codebase valid C++, how should they do >> it after this change? >> >> Perhaps the previous dev-platform thread would provide enlightenment and >> I ought to go back and reread it :( , but I do not offhand recall it >> deciding to remove the configure option altogether. >> > > I have an issue here, too. > > Debugging using gdb will be very difficult when the unified build > creates a source file on the fly (but it is removed, correct?). > > No sane compiler/debugger combination can help me do > the source level debugging if the source code that the compiler > compiled is gone by the time debugger tries to find it... > > Maybe I am missing something... I have a similar question about static analysis tools (clang analyzer, coverity, etc).
Doing the SA on the whole unified file is going to produce some useless results if all the files content gets merged. But maybe I am just missing the point. Cheers, Sylvestre _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
