Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
G
glslang
  • Project
    • Overview
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Chen Yisong
  • glslang
  • Repository

Switch branch/tag
  • glslang
  • External
  • CMakeLists.txt
Find file
BlameHistoryPermalink
  • Karl Schultz's avatar
    build: Don't ship GTEST headers in install target · 1d1fd885
    Karl Schultz authored Apr 02, 2019
    A project that uses googletest(GTEST) shouldn't include googletest
    headers with its artifacts in its install target.  These headers
    simply are not needed by the consumers of the install target and
    can cause conflicts with other projects that use googletest
    themselves and this project's install target.  And they are just not
    part of the expected glslang build artifacts.
    
    It is likely that the addition of the googletest headers to the install
    target was a simple oversight that happens as a result of adding
    googletest as a CMake subdirectory.
    
    For more information on how this causes conflicts with other projects,
    please see: https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/821.
    1d1fd885
CMakeLists.txt 1.54 KB
EditWeb IDE
×

Replace CMakeLists.txt

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.