Lines Matching full:build
21 <li><a href="#build">Help! My project won't build in Eclipse</a></li>
27 <li><a href="#signingcalendar">I can't compile my app because the build tools generated an expired debug certificate</a></li>
130 <a name="build"></a><h2>Help! My project won't build in Eclipse</h2>
131 <p>If your project doesn't build, you may notice symptoms such as new
161 To clean the project (a good idea with any kind of build error), select
289 <h2 id="signingcalendar">I can't compile my app because the build tools generated an expired debug certificate</h2>
291 <p>If your development machine uses a locale that has a non-Gregorian calendar, you may encounter problems when first trying to compile and run your application. Specifically, you may find that the Android build tools won't compile your application because the debug key is expired. </p>
293 build tools — fails to properly handle non-Gregorian locales and may create validity dates that are in the past. That is, it may generate a debug key that is already expired, which results in the compile error.</p>
298 <li>First, delete the debug keystore/key already generated by the Android build tools. Specifically, delete the <code>debug.keystore</code> file. On Linux/Mac OSX, the file is stored in <code>~/.android</code>. On Windows XP, the file is stored in <code>
303 <li>Temporarily change your development machine's locale (date and time) to one that uses a Gregorian calendar, for example, United States. Once the locale is changed, use the Android build tools to compile and install your app. The build tools will regenerate a new keystore and debug key with valid dates. Once the new debug key is generated, you can reset your development machine to the original locale. </li>
