▁as ▁a ▁result ▁of ▁the ▁build . ▁ ▁The ▁dependency ▁information ▁is ▁stored ▁in ▁a ▁configuration ▁record ▁that ▁can ▁be ▁shown ▁for ▁each ▁derived ▁object . ▁The ▁configuration ▁record ▁can ▁be ▁used ▁to ▁create ▁another ▁view ▁that ▁shows ▁all ▁files ▁that ▁have ▁been ▁previously ▁read ▁during ▁the ▁build ▁time . ▁The ▁configuration ▁record ▁can ▁also ▁be ▁used ▁to ▁apply ▁a ▁label ▁to ▁the ▁files ▁( and ▁versions ) ▁that ▁were ▁read ▁during ▁the ▁build . ▁ ▁The ▁M V FS ▁allows ▁derived ▁objects ▁that ▁were ▁built ▁in ▁one ▁dynamic ▁view ▁to ▁be ▁automatically ▁" cop ied " ▁to ▁another ▁dynamic ▁view ▁that ▁requires ▁" ex actly ▁the ▁same " ▁derived ▁object . ▁Two ▁derived ▁objects ▁are ▁de emed ▁to ▁be ▁" ex actly ▁same " ▁if ▁they ▁have ▁the ▁same ▁configuration ▁record ▁( that ▁is , ▁bill ▁of ▁materials ). ▁The ▁share able ▁derived ▁objects ▁are ▁phys ically ▁present ▁in ▁the ▁V OB ▁server , ▁not ▁in ▁the ▁views ▁that ▁reference ▁them . ▁This ▁feature ▁is ▁called ▁w inking ▁in ▁derived ▁objects ▁and ▁requires ▁that ▁the ▁clear make ▁or ▁o make ▁tool ▁is ▁used ▁for ▁builds . ▁ ▁Clear Case ▁dynamic ▁views ▁are ▁slower ▁than ▁local ▁filesystem s , ▁even ▁with ▁a ▁good ▁network ▁infrastr ucture . ▁Re pe ated ▁subsequent ▁builds ▁may ▁run ▁faster , ▁due ▁to ▁build ▁avoid ance ▁that ▁is ▁enabled ▁by ▁Clear Case ' s ▁make ▁substitute . ▁Because ▁M V FS ▁requires ▁server ▁access ▁every ▁time ▁a ▁file ▁is ▁accessed , ▁the ▁performance ▁of ▁the ▁file ▁system ▁depends