{"id":105,"date":"2015-04-29T18:28:29","date_gmt":"2015-04-29T18:28:29","guid":{"rendered":"http:\/\/visualgdb.com\/w\/?p=105"},"modified":"2015-07-19T08:33:29","modified_gmt":"2015-07-19T15:33:29","slug":"android-vs-android-intellisense","status":"publish","type":"post","link":"https:\/\/visualgdb.com\/tutorials\/android\/vs-android\/intellisense\/","title":{"rendered":"Configuring IntelliSense for vs-android"},"content":{"rendered":"

This tutorial shows how to configure IntelliSense for vs-android to automatically parse include files from the Android NDK and support all involved GNU extensions.<\/p>\n

    \n
  1. Install VisualGDB<\/a> 5.0 or later (ensure that “Android Edition” is checked in the installer). This will add support for debugging and Clang-based IntelliSense to vs-android projects.<\/li>\n
  2. Start Visual Studio. Select “Android->Setup SDK\/NDK Locations”. Specify the paths to your Android tools and click “Add Support” to select VisualGDB as a default debugger for vs-android projects:\"01-locations\"<\/a><\/li>\n
  3. Open a vs-android project (in this example we will use the san-angeles demo) and ensure you can build it successfully:\"02-build\"<\/a><\/li>\n
  4. Open one of the source files. Although the syntax highlighting and IntelliSense will work, you will most likely see some error messages:\"03-errors\"<\/a><\/li>\n
  5. This happens because the NDK uses some GNU extensions that are not enabled with Clang by default. As of NDK r10, the following extensions are used:
    \n\n\n\n\n\n
    Extension<\/th>\nExample<\/th>\nOption to enable<\/th>\n<\/tr>\n
    Named variadic macros<\/td>\n#define __builtin_warning(x, y…)<\/td>\n-Wno-variadic-macros<\/td>\n<\/tr>\n
    Zero-length arrays<\/td>\nchar _pad[0]<\/td>\n-Wno-zero-length-array<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Furthermore, the san-angeles example uses some C functions without declaring them and this will be treated as an error unless -Wno-implicit-function-declaration<\/strong> is specified.<\/p>\n

    To enable those extensions, double-click on the errors in Error List and, then select the smart tag in the code at the error location and select “ignore this issue for the project”:\"03a-tag\"<\/a><\/li>\n

  6. Once you have enabled all relevant extensions, you can get an overview of the added IntelliSense flags by right-clicking on your project in Solution Explorer, selecting VisualGDB Project Properties, going to the IntelliSense Settings page and checking the “Additional flags for C files” field:\"04-properties\"<\/a><\/li>\n
  7. Press OK to apply the new settings. The error messages will now disappear and the IntelliSense engine will be able to parse the code correctly. Right-click on appRender() and select “Find all references” to test it out. \"05-refs\"<\/a>Note that clang-powered “Find All References” command will also look into references within preprocessor macro expansions and will work instantly even for huge projects.<\/li>\n
  8. You can also quickly explore the structure of the source code by right-clicking on a function and selecting “Explore call hierarchy”. You can then choose to browse called functions, calling functions, or both:\"06-calls\"<\/a><\/li>\n
  9. Start debugging your app by pressing F5 (given that you have enabled debugger integration as described in the beginning of this tutorial). Set a breakpoint in camTrack(). Once it is triggered, try entering a complex expression (e.g. cam->dest) in the Watch window. The auto-completion work there same way as when debugging C# programs:\"07-sense\"<\/a><\/li>\n
  10. You can also use preprocessor macros in Watch expressions or hover mouse over them to see their value in the current context:\"08-macro\"<\/a><\/li>\n
  11. When you are done debugging, press Shift-F5 to end the debugging session.<\/li>\n<\/ol>\n

     <\/p>\n","protected":false},"excerpt":{"rendered":"

    This tutorial shows how to configure IntelliSense for vs-android to automatically parse include files from the Android NDK and support<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19],"tags":[31,52,48],"_links":{"self":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts\/105"}],"collection":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/comments?post=105"}],"version-history":[{"count":1,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts\/105\/revisions"}],"predecessor-version":[{"id":181,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts\/105\/revisions\/181"}],"wp:attachment":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/media?parent=105"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/categories?post=105"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/tags?post=105"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}