On 21/02/2019 14:18, Timothy Wrona wrote:
Perhaps there is a standard location to "install" the documentation when
running the install command for a project?
This collection builds and installs the documentation into a standard
location, as well as reporting undocumented code. Feel free to co
I was just about to write a mail with similar content than this one, so allow
me to add my 5 cents.
Fear of reyling on defaults in case Microsoft decides to change them?
1) Defaults don't change often. BTW, don't we rely on defaults for GCC and
Clang anyway?2) Defaults change to benefit users. I
Hi All!
I am trying to compile CUDA code with controlling both host and device compiler
flags.
Currently my CMakeLists.txt looks like:
```
cmake_minimum_required(VERSION 3.8) # CUDA language support
project(CUDA_test LANGUAGES CXX CUDA)
if (MSVC)
string(REGEX REPLACE "/W[0-9]" "" CMAKE_CXX_FLA
Hi Timothy,
This is not something I'm very familiar with, but maybe I
can still add a little to the discussion by answering both
of your messages together.
On 21/2/2019 10:18 PM, Timothy Wrona wrote:
Perhaps there is a standard location to "install" the
documentation when running the insta
Perhaps there is a standard location to "install" the documentation when
running the install command for a project?
Either way having it as an "index.html" file somewhere on the hard-disk is
not very intuitive. It would make much more sense for it to be on a web
server where you can access it with
Hi all,
following my previous post 'link only with targets feature' I have
found yet another unpleasant consequence of not being able to tell
cmake that it is the target name in the parameters of
target_link_libraries (without the use of :: notation, that is
optional and inconsistent). Whe