summaryrefslogtreecommitdiffstats
path: root/llvm/lib
diff options
context:
space:
mode:
authorChris Bieneman <chris.bieneman@me.com>2018-10-15 21:14:19 +0000
committerChris Bieneman <chris.bieneman@me.com>2018-10-15 21:14:19 +0000
commit09fcbbd85c96ae11f15be34277e41db75345bf70 (patch)
tree15e25f48aa8797496fe69deb577a03c0cd179a35 /llvm/lib
parent94dfcc2eb2668fcd1129f33cb7df68b20a95b14e (diff)
downloadbcm5719-llvm-09fcbbd85c96ae11f15be34277e41db75345bf70.tar.gz
bcm5719-llvm-09fcbbd85c96ae11f15be34277e41db75345bf70.zip
[CMake] Change the default value of LLVM_ENABLE_IDE
There really aren't any generator behaviors that we need to take `CMAKE_EXTRA_GENERATOR` into account for. Where we need to take different behaviors for IDEs is mostly in enabling or disabling certain build system features that are optional but trip up the IDE UIs. Like the generation of lots of utility targets. By changing the LLVM_ENABLE_IDE default to only being on for multi-configuration generators, we allow gating where it will impact the UI presentation, while also supporting optionally disabling the generation if your tooling workflow encounters problems. Presently being able to manually disable extra target generation is useful for Visual Studio 2017's CMake integration where the IDE has trouble displaying and working with the large number of optional targets. llvm-svn: 344553
Diffstat (limited to 'llvm/lib')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud