언어 설정

Menu
Sites
Language
Tizen project build on Mac OS X: Include paths workspace folders not working.

Hi,

I have projects that are dependent. Project A is shared library which used by project B.

From Project B I am trying to include a file of project A by Project -> Properties ->  C/C++ Build -> Settings -> C++ compiler -> Include Paths (-I ), clicked on Add button -> select workspace -> inc folder where the include file is located. 

Though I have added the inc folder to include paths and it appear in the C++ compiler -> All options -I "...." paths, on building from CLI using `tizen build-native -a arm -c gcc -C Debug` command, compiler is unable to find the header. It does not appear in the arm-linux-gnueabi-g++ -I"pch" -D_DEBUG -I"..." options.

Hence compilation is failing.  However, if I build from IDE it is compiling, the path is included. I have tried cleaning the project, refreshing the project, deleting debug folder etc without any progress. 

In short 'tizen build-native' scanner discovery of include paths is not working on mac os.

On windows both compilation from CLI and from IDE work without any issues.

Is there any issue with adding include paths through workspaces?

Please let me know If I am making any mistake?

Any help is much appreciated.

Edited by: Me Papillon on 19 6월, 2015
목록

Responses

5 댓글
Jean Yang

Hi, 

Do you check the access right of your library in macOS? 

Me Papillon

Hi,

It is to do with the Include files path and not lib file. Permissions of the lib is -rwxr-xr-x .Include files are not found though the path is correctly mentioned.

 

Me Papillon

 'tizen build-native' scanner discovery of include paths is not working on mac os.

Vikram

Hi,

How about you try to build your shared library through Project references?

   Project Explorer --> Project --> Project Property --> Project References

AFAK Project References can be used for multiproject like your case.

 

Me Papillon

Hi Vikram,

I did try Project references, it did not work. When built from IDE there is no issue. Issue is observed only when building from the CLI with 'tizen build-native' command.