question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Include paths are not set

See original GitHub issue

Step to reproduce:

  1. Download http://www.cocos2d-x.org/filedown/cocos2d-x-3.16.zip
  2. Unzip
  3. open cocos2d-x-3.16\build\cocos2d-win32.sln
  4. project cpp-tests “Clang Power Tools”->Compile Bug: include directories were not extracted from. vcproj.

` Start Clang Compile

VERBOSE: CPU logical core count: 12 VERBOSE: LLVM location: C:\Program Files\LLVM\bin VERBOSE: Source directory: G:\clang_power_tools\cocos2d-x-3.16\tests\cpp-tests\proj.win32 VERBOSE: Scanning for .vcxproj files VERBOSE: Found 1 projects [ INFO ] WILL PROCESS PROJECTS: cpp-tests.vcxproj [ INFO ] 1. PROCESSING PROJECT G:\clang_power_tools\cocos2d-x-3.16\tests\cpp-tests\proj.win32\cpp-tests.vcxproj VERBOSE: Configuration platform: Debug|Win32 VERBOSE: Property sheets: VERBOSE: G:\clang_power_tools\cocos2d-x-3.16\cocos\2d\cocos2dx.props VERBOSE: G:\clang_power_tools\cocos2d-x-3.16\cocos\2d\cocos2d_headers.props VERBOSE: PCH not enabled for this project! VERBOSE: Preprocessor definitions: VERBOSE: -DWIN32 VERBOSE: -D_DEBUG VERBOSE: -D_WINDOWS VERBOSE: -D_USE_MATH_DEFINES VERBOSE: -DGL_GLEXT_PROTOTYPES VERBOSE: -DCC_ENABLE_CHIPMUNK_INTEGRATION=1 VERBOSE: -DCOCOS2D_DEBUG=1 VERBOSE: -D_CRT_SECURE_NO_WARNINGS VERBOSE: -D_SCL_SECURE_NO_WARNINGS VERBOSE: -DCOCOS2DXWIN32_EXPORTS VERBOSE: -D_VARIADIC_MAX=10 VERBOSE: -DUNICODE VERBOSE: -D_UNICODE VERBOSE: -D_USING_V110_SDK71_ VERBOSE: Platform toolset: v120 v120_xp v140 v140_xp v141 v141_xp VERBOSE: Additional includes: VERBOSE: G:\clang_power_tools\cocos2d-x-3.16\tests\cpp-tests\Classes VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE: Visual Studio location: C:\Program Files (x86)\Microsoft Visual Studio\2017\Community VERBOSE: MSCVER: 14.11.25503 VERBOSE: WinSDK version: 7.0 VERBOSE: Include directories: VERBOSE: G:\clang_power_tools\cocos2d-x-3.16\tests\cpp-tests\proj.win32 VERBOSE: C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include VERBOSE: C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\atlmfc\include VERBOSE: C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\VS\include VERBOSE: C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt VERBOSE: C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Include VERBOSE: G:\clang_power_tools\cocos2d-x-3.16\tests\cpp-tests\Classes VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE:
VERBOSE: Force includes: VERBOSE: Processing 133 cpps 133: G:\clang_power_tools\cocos2d-x-3.16\tests\cpp-tests\Classes\AllocatorTest\AllocatorTest.cpp 132: G:\clang_power_tools\cocos2d-x-3.16\tests\cpp-tests\Classes\BaseTest.cpp 131: G:\clang_power_tools\cocos2d-x-3.16\tests\cpp-tests\Classes\BillBoardTest\BillBoardTest.cpp 130: G:\clang_power_tools\cocos2d-x-3.16\tests\cpp-tests\Classes\BugsTest\Bug-12847.cpp 129: G:\clang_power_tools\cocos2d-x-3.16\tests\cpp-tests\Classes\BugsTest\Bug-15594.cpp 128: G:\clang_power_tools\cocos2d-x-3.16\tests\cpp-tests\Classes\BugsTest\Bug-15776.cpp 127: G:\clang_power_tools\cocos2d-x-3.16\tests\cpp-tests\Classes\BugsTest\Bug-14327.cpp 126: G:\clang_power_tools\cocos2d-x-3.16\tests\cpp-tests\Classes\BugsTest\Bug-CCDrawNode.cpp 125: G:\clang_power_tools\cocos2d-x-3.16\tests\cpp-tests\Classes\BugsTest\Bug-Child.cpp 124: G:\clang_power_tools\cocos2d-x-3.16\tests\cpp-tests\Classes\Camera3DTest\Camera3DTest.cpp 123: G:\clang_power_tools\cocos2d-x-3.16\tests\cpp-tests\Classes\ChipmunkTest\ChipmunkTest.cpp 122: G:\clang_power_tools\cocos2d-x-3.16\tests\cpp-tests\Classes\ClippingNodeTest\ClippingNodeTest.cpp In file included from G:\clang_power_tools\cocos2d-x-3.16\tests\cpp-tests\Classes\AllocatorTest\AllocatorTest.cpp:26: In file included from G:\clang_power_tools\cocos2d-x-3.16\tests\cpp-tests\Classes\AllocatorTest/AllocatorTest.h:28: G:\clang_power_tools\cocos2d-x-3.16\tests\cpp-tests\Classes\AllocatorTest/…/BaseTest.h:28:10: fatal error: ‘cocos2d.h’ file not found #include “cocos2d.h” ^~~~~~~~~~~ 1 error generated.

Got errors.

Done Clang Compile

`

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:9 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
mariusz102102commented, Nov 10, 2017

In attachment simplified test case.

It contains: Default console application + PropertySheet.props (18 lines only). PropertySheet has User Macros VAR=c:\temp, macro is used in AdditionalIncludeDirectories.

It seems like Macros (in my test case my $(VAR) ) are not supported for AdditionalIncludeDirectories.

Below PropertySheet.props:

<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <ImportGroup Label="PropertySheets" />
  <PropertyGroup Label="UserMacros">
    <VAR>C:\temp</VAR>
  </PropertyGroup>
  <PropertyGroup />
  <ItemDefinitionGroup>
    <ClCompile>
      <AdditionalIncludeDirectories>$(VAR);G:\</AdditionalIncludeDirectories>
    </ClCompile>
  </ItemDefinitionGroup>
  <ItemGroup>
    <BuildMacro Include="VAR">
      <Value>$(VAR)</Value>
    </BuildMacro>
  </ItemGroup>
</Project>

ConsoleApplication2.zip

0reactions
mariusz102102commented, Nov 28, 2017

Strange… I just reloaded project and it works… Maybe it related to randomness in https://github.com/Caphyon/clang-power-tools/issues/124

Read more comments on GitHub >

github_iconTop Results From Across the Web

c++ - VSCode not recognizing includes from includepath
I have tried adding it both to my include path and windows environment path. it keeps failing for the same reason. I am...
Read more >
Include path doesn't include the custom paths inserted #1190
When I #include with absolute paths aka /home/user/workspacefolder/lib/include/header.hpp it does work. Which is weird as the extension assumes ...
Read more >
mingw - How can I properly configure the g++ include path ...
This is easy to fix by passing -I<include path> as an additional argument to g++ .
Read more >
Include paths not being passed from VSLinux to remote build
I am getting repeated failures to find include files in various VSLinux projects. An example of this : From project / properties /...
Read more >
Configure include paths - PhpStorm
Include paths are used for holding libraries, that is, third-party code that is used for completion and reference resolution in some functions/ ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found