Hi, Actually Open C and flame should not used same code base. The reason that open C can use flame before is we use the build for msm8x10 in the beginning. After that, we add some specific features like NFC in flame. That's why some of errors happened if you only have open C in your hand.
https://bugzilla.mozilla.org/show_bug.cgi?id=1016867#c1 Here's a quick fix to use the first version for device-flame. That's pretty close to pure msm8x10 from CAF should work for open C Regards, viral ----- Original Message ----- From: xlaur...@gmail.com To: mozilla-dev-...@lists.mozilla.org Sent: Tuesday, May 27, 2014 3:20:06 PM Subject: Re: [b2g] ZTE Open C Hi, The commit for adding nfc libs on flame device is causing me the same troubles: https://github.com/mozilla-b2g/device-flame/commit/59296869473fdb38fda79123605e68a9d959c964 The build works fine when reverting this change. Since Open C does not support nfc, maybe a dedicated device should be forked from the flame? Regards Le mardi 27 mai 2014 07:50:11 UTC+2, Chris Mills a écrit : > On 26 May 2014, at 22:04, Philip Wright <horus...@gmail.com> wrote: > > > > > On Sunday, 25 May 2014 20:13:51 UTC+1, pul...@gmail.com wrote: > > >> Hi, > > >> > > >> i tried to build by the guide (hope i did), it didn't work. > > >> > > >> > > >> > > >> Command ./build.sh gecko will fail with nfc libs missing... > > > > > > any chance you could post full details of the failure, we may be able to > > work around it > > > > Yes, please do, so we can solve this issue and improve the instructions. > > > > Best, > > > > > > Chris Mills > > Senior tech writer || Mozilla > > developer.mozilla.org || MDN > > cmi...@mozilla.com || @chrisdavidmills _______________________________________________ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g _______________________________________________ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
