This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Compiler: Setting flag TREAT_WARNINGS_AS_ERRORS inside VisionSDK(ver 2.11)

Tool/software: TI C/C++ Compiler

Hello Everyone,

Iam working on VisionSDK(ver 2.11) .When I set the TREAT_WARNINGS_AS_ERRORS  flag to 'no' ,I fail to achieve error for undefined functions  and it successfully compiles.Why does it suppress the undefined functions and throw no error.However if flag is set 'yes' ,it gives error.

Regards,

poonam

  • Hi, Poonam,

    VSDK experts have been notified. They will reply directly here.

    Regards,
    Mariya
  • Hi Poonam,

    Can you please provide more details on successful compilation scenario.
    If you have undefined functions that you are calling in the application, linker will give an error.

    Regards,
    Rishabh
  • Hi Poonam,

    usually the undefined functions are shown just as warnings in the compilation process (from source code to object code)
    and then, as Rishabh said, can cause errors during linking (from object code to executable). If the flag treat warning as errors
    is set, then there will be an error instead of warning and the build process will be stopped on compile stage.

    Do you see warning about undefined function on successful case? Do you get executable binary in that case?

    Regards,
    Yordan
  • Hi Yordan,

    I am working with poonam on this issue..
    First thing the problem is when treat warning as error flag is reset(0)..
    Consider scenario : if i have declared abc function in abc.h file and if i call the same function in abc.c file it gets successfully compiled even if there is no definition of abc available in application..

    @Rishabh : If you have undefined functions that you are calling in the application, linker will give an error.

    We are also expecting the same but there is no error thrown from linker.. can you please once check is it a problem with flag/build system because we haven't faced such issue with VSDK2.10.

  • Hi Kapil,

    Can you tell me what is the compiler with which you are facing this issue?

    Regards,
    Rishabh
  • We are compiling algorithm plugins in which we are facing this issue and it's for DSP1 and DSP2 . i am not sure is this what you are asking ?...
    I corrected my last reply we didn't face this issue with VSDK2.10..
  • Hi Kapil,

    Let me check this and I will get back to you.

    Regards,
    Rishabh
  • Hi Rishabh,
    Did you get any updates on this ?
  • Hi Kapil,

    I was unable to reproduce the exact issue as mentioned above.
    However I think there is an issue with warnings/errors generation by DSP build in case of missing API definition.
    This might be a bug in SDK and needs a proper debug.
    We will fix it in next release.
    I will post a reply on this thread when we fix this.

    Regards,
    Rishabh
  • Ok rishabh . thanks for your response..

    one doubt i have is to add algo plugin in VSDK 2.11 i have done following changes :

    1) Adding my algo in ALG_LIST variable in cfg.mk file inside vision_sdk/configs folder..

    but after doing this change i am not able to see my algo in result of make showconfig command.

    so to add my algo in VSDK 2.11 i have modified makefile available at vision_sdk/examples/tda2xx/src/alg_plugin , i am not sure is this a required step or not as it is not mentioned anywhere in documentation of VSDK 2.11 ..

    2) By going through doc i got a query regarding is it compulsory to create a user defined config like tda3xx_evm_bios_all if i am adding new algo plugins in VSDK 2.11?


    Thanks,
    Kapil Mehta
  • Hi Kapil,

    Can you please refer to the chapter "Adding new use-cases, algplugins to build" of the user guide VisionSDK_UserGuide_BuildSystem.pdf.

    Regards,
    Rishabh
  • Yes i have referred it. it says to add my algo name in ALG_LIST variable inside vision_sdk/configs/cfg.mk and after this you should be able to see name in make showconfig command .. but still after adding it i am not able to see my algo in output of command.. 

    And when we build there is one file auto generated called system_cfg_tda3xx_evm_bios_all.h , inside this also i am not getting my algo name..

    can you please check on this ?

  • Hi Kapil,

    Have you done the below step:
    6. Enable algplug in a required use-case cfg.mk file (see section 6.1 Adding new use-cases to build (BIOS ONLY mode))

    Please note that the use case where alg plugin is used should be enabled in build.

    Regards,
    Rishabh
  • hi rishabh,

    currently i haven't added any use case for my alg plugin as i am trying to add only alg plugin..

    I think it should not be compulsory to add any use case for all alg plugins.. right ?

  • Hi Kapil,

    Alg plugin will be used in a use case right.
    You need to specify what is the use case for which the alg plugin is enabled.
    Regards,
    Rishabh
  • Hi Kapil,

    For example to enable object detect algorithm in UC_fast_boot_iss_capture_isp_simcop_pd_display, ALG_objectdetection=yes is set in vision_sdk\examples\tda2xx\src\usecases\fast_boot_iss_capture_isp_simcop_pd_display\cfg.mk.

    Regards,
    Rishabh
  • Yes that's also what i understood..

    but with previous VSDK versions it was not compulsory to add use-case for all algo plugins,  you can only add and compile algo plugins ..

    Initially we just add algorithms and after adding all modules as plugins we create usecase..

    Isn't it possible with 2.11 version?

  • Hi Kapil,

    Build system changed with VSDK 2.11 release and now you need to enable Alg Plugin for a use case.
    You can add a dummy usecase and enable your algorithm for it.
    Later on when you are done with algorithm development you can create real use case.

    Regards,
    Rishabh
  • Hi,

    there has been no activity on this thread for several weeks, so I will close it.

    Regards,
    Yordan