peer23peer

Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • in reply to: VisualGDB 5.0 Intellisens Clang suggestions #6367
    peer23peer
    Participant

    Sorry forgot to mention the flags of the CLANG intellisense:

    Main project:

    CFlag

    –target=x86_64 -IC:\Users\jelle\AppData\Local\VisualGDB\RemoteSourceCache\192.168.178.10006\4.8 -IC:\Users\jelle\AppData\Local\VisualGDB\RemoteSourceCache\192.168.178.10007\4.8 -IC:\Users\jelle\AppData\Local\VisualGDB\RemoteSourceCache\192.168.178.10006\4.8\backward -IC:\Users\jelle\AppData\Local\VisualGDB\RemoteSourceCache\192.168.178.10003\include -IC:\Users\jelle\AppData\Local\VisualGDB\RemoteSourceCache\192.168.178.10000\include\x86_64-linux-gnu -IC:\Users\jelle\AppData\Local\VisualGDB\RemoteSourceCache\192.168.178.10000\include -IC:\Users\jelle\AppData\Local\VisualGDB\RemoteSourceCache\192.168.178.10004\include -include D:\OneDrive\Opleiding\HTS_HAN\Minor2\CPP\VisionSoilAnalyzer\Tests\UnitTest\VSA_UT\VSA_UT\gcc_Debug.h -include C:\Program Files (x86)\Sysprogs\VisualGDB\gcc_compat.h  -std=c++11 -D__SYSPROGS_CODESENSE__

     

    CXX Flag

    –target=x86_64 -IC:\Users\jelle\AppData\Local\VisualGDB\RemoteSourceCache\192.168.178.10006\4.8 -IC:\Users\jelle\AppData\Local\VisualGDB\RemoteSourceCache\192.168.178.10007\4.8 -IC:\Users\jelle\AppData\Local\VisualGDB\RemoteSourceCache\192.168.178.10006\4.8\backward -IC:\Users\jelle\AppData\Local\VisualGDB\RemoteSourceCache\192.168.178.10003\include -IC:\Users\jelle\AppData\Local\VisualGDB\RemoteSourceCache\192.168.178.10000\include\x86_64-linux-gnu -IC:\Users\jelle\AppData\Local\VisualGDB\RemoteSourceCache\192.168.178.10000\include -IC:\Users\jelle\AppData\Local\VisualGDB\RemoteSourceCache\192.168.178.10004\include -include D:\OneDrive\Opleiding\HTS_HAN\Minor2\CPP\VisionSoilAnalyzer\Tests\UnitTest\VSA_UT\VSA_UT\gcc_Debug.h -include C:\Program Files (x86)\Sysprogs\VisualGDB\gcc_compat.h  -std=c++11 -D__SYSPROGS_CODESENSE__

     

    in reply to: VisualGDB 5.0 Intellisens Clang suggestions #6366
    peer23peer
    Participant

    Hi Bazis,

    The errors are always present, it doesn’t matter if I’m currently working in *.h or *.cpp file

    I’m compiling with the -std=c++11  flag and use cmake, building is done using make -j4

    below is the CmakeList.txt of my startup project a BOOST unit test for various custom libraries all compiled with the same flag

    —————————————————————————————————

    #Generated by VisualGDB project wizard.
    #Note: VisualGDB will automatically update this file when you add new sources to the project.

    cmake_minimum_required(VERSION 2.7)
    project(VSA_UT)
    ADD_DEFINITIONS(-DBOOST_TEST_DYN_LINK -DDEBUG)
    SET(CMAKE_INSTALL_RPATH_USE_LINK_PATH TRUE)

    set(LIBRARIES_FROM_REFERENCES ${CMAKE_SOURCE_DIR}/../../../../src/VisionSoilAnalyzer/Vision/Debug/libVision.so ${CMAKE_SOURCE_DIR}/../../../../src/VisionSoilAnalyzer/Soil/Debug/libSoil.so ${CMAKE_SOURCE_DIR}/../../../../src/VisionSoilAnalyzer/SoilPlot/Debug/libSoilPlot.so ${CMAKE_SOURCE_DIR}/../../../../src/VisionSoilAnalyzer/SoilMath/Debug/libSoilMath.so)
    add_executable(VSA_UT VSA_UT.cpp)
    target_link_libraries(VSA_UT -L/usr/local/lib -L/usr/lib/x86_64-linux-gnu/ -lopencv_calib3d -lopencv_core -lopencv_features2d -lopencv_imgproc -lopencv_flann -lopencv_highgui -lopencv_imgcodecs -lopencv_ml -lopencv_objdetect -lopencv_photo -lopencv_shape -lopencv_stitching -lopencv_superres -lopencv_ts -lopencv_video -lopencv_videoio -lopencv_videostab “${LIBRARIES_FROM_REFERENCES}” -lboost_serialization -lboost_unit_test_framework)
    include_directories (/usr/local/include /usr/local/include/opencv /usr/include/boost)
    set(CMAKE_C_FLAGS “${CMAKE_C_FLAGS} -std=c++11”)
    set(CMAKE_CXX_FLAGS “${CMAKE_CXX_FLAGS} -std=c++11”)

    —————————————————————————————————–

    Screenshot doesn’t give clear information, they are all red lines at the first “(” after the return keyword. zie table below for specific line and column

    Severity                                  Description                                                                        Project                       File                  Line Column
    Error [Clang IntelliSense] Error: compound literals are a C99-specific feature Miscellaneous Files emmintrin.h 98 10
    Error [Clang IntelliSense] Error: compound literals are a C99-specific feature Miscellaneous Files emmintrin.h 158 10
    Error [Clang IntelliSense] Error: compound literals are a C99-specific feature Miscellaneous Files emmintrin.h 164 10

    —————————————————————————————————————————

    static __inline__ __m128d __attribute__((__always_inline__, __nodebug__))
    _mm_sqrt_sd(__m128d __a, __m128d __b)
    {
    __m128d __c = __builtin_ia32_sqrtsd(__b);
    return (__m128d) { __c[0], __a[1] };
    }

    ————————————————————————————–

    static __inline__ __m128d __attribute__((__always_inline__, __nodebug__))
    _mm_cmpeq_pd(__m128d __a, __m128d __b)
    {
    return (__m128d)__builtin_ia32_cmpeqpd(__a, __b);
    }

    ——————————————————————————————-

    static __inline__ __m128d __attribute__((__always_inline__, __nodebug__))
    _mm_cmplt_pd(__m128d __a, __m128d __b)
    {
    return (__m128d)__builtin_ia32_cmpltpd(__a, __b);
    }

    This is also the cause for most of the errors that I checked in the files: mmintrin.h , xmmintrin.h

     

    in reply to: problem with Cross-compiling beaglebone black opencv #3514
    peer23peer
    Participant

    Hi Bazis,

    Thank you for the reply. I didn’t test it because it took the admins short of a week to allow my message and I was/am under a lot of time pressure. I therefor didn’t have time to waste and switch to Cmake and an external Linux computer. In this new setup I compile and test general c++ code on an external Linux X64 computer using VisualGDB and switch to my BBB when needed. Although it isn’t cross compiling, this setup suits me well.

    The new project structure and source code can be found here https://github.com/peer23peer/VisionSoilAnalyzer

Viewing 3 posts - 1 through 3 (of 3 total)