Forum Replies Created
-
Posts
-
Hi,
This is the directory where the Android Studio/gradle expect the native files. The problem is that the native support there is currently broken, so when Gradle tries to build the native files, it could:
- Generate a Makefile that won’t build on Windows due to problems with parsing Windows-style paths
- Strip the symbol information from the built libraries, making the debugging impossible
The exact gradle bugs change from version to version, so our current recommendation is to keep the source files in the app\jni directory and let VisualGDB handle the build. This will ensure that you won’t get strange build errors and that your symbols will be generated correctly. As soon as the Gradle support for native symbols becomes stable, we will update our tutorials to use the recommended paths.
This would cause several bugs with the NDK tools. If you don’t want to move the actual files, you can create a symbolic link using the mklink command, i.e.
mklink /d C:\Users\nzmora\AndroidStudioProjects\CameraProcessor\app\jni C:\Users\nzmora\AndroidStudioProjects\CameraProcessor\app\src\main\jni
Hi,
Normally the USB clock needs to be 48 MHz. Please use the STM32CubeMX tool to validate your clock parameters:
You can read here about integrating code generated by STM32CubeMX into VisualGDB projects.
Hi,
Please try installing the Qt addin: https://wiki.qt.io/Visual_Studio_Add-in
Hi,
We have investigated the problem. Looks like our Beaglebone toolchain is missing one important file. We will update it soon.
As a workaround please create a file called ld.so.conf in d:/sysgcc/beagledebian/arm-linux-gnueabihf/sysroot/etc and put the following contents there:
# Multiarch support /lib/arm-linux-gnueabihf /usr/lib/arm-linux-gnueabihf # libc default configuration /usr/local/lib
Please use comma instead of space after the -Wa option, i.e.:
- Modify the .c file rule this way:
$(BINARYDIR)/%.o : %.c $(all_make_files) |$(BINARYDIR) $(CC) $(CFLAGS) -c $< -o $@ -MD -MF $(@:.o=.dep) -Wa,-adhlns=$(@:.o=.lst)
- Change the contents of the SOURCEFILES statement (e.g. remove one file) so that VisualGDB regenerates the rules your Makefile.
- Build your project.
Hi,
We have simplified the integration with STM32CubeMX in VisualGDB 5.0 Beta 3 and added a detailed tutorial showing how to use it: http://visualgdb.com/tutorials/arm/stm32/cube/
Do those files (e.g. libSM.so.6) exist in your toolchain’s sysroot? If yes, what is the directory containing them?
Hi,
Please try adding the flags directly to the targets and target templates, e.g.:
$(BINARYDIR)/%.o : %.cpp $(all_make_files) |$(BINARYDIR) $(CXX) $(CXXFLAGS) -c $< -o $@ -MD -MF $(@:.o=.dep) <add your flags here>
Looks like you are missing some libraries in your project properties. Search the sysroot\usr\lib directory for files containing the undefined symbols from the error message and add the found library names (without ‘lib’ prefix and extension) to the library list in VisualGDB Project Properties.
Regarding real-time IntelliSense, you can try enabling Tools->Options->C/C++(VisualGDB)->Advanced->Code Completion->Suggest names while typing. If this is not what you meant, please provide us with a better example of what you are trying to achieve.
Please contact our sales at sales@sysprogs.com for details about the number of machines.
The Visual Studio compiler and GCC are not 100% compatible when it comes to complex C++ templates. You may need to adjust your code so that both compilers can handle this (the problem is well-known, so googling for specific errors should easily get the fixing instructions).
You can specify -std=c++11 or -std=c++14 in CFLAGS on the Makefile Settings page of VisualGDB Project Properties.
Hi,
Please add the directory containing the missing header file to the “Include Directories” field on the Makefile Settings page of VisualGDB Project Properties. Adding the file to the Solution Explorer simply makes it easier to open, but does not affect search paths used by the #include<> directives.
