On Fri, Apr 05, 2019 at 07:56:25PM -0700, Marc Herbert wrote:
>Instead of removing, have you tried appending the -Wno-fubar flag that
>turns back off these
>specific warnings for these specific files?
Ah, yes, it will actually work... Not the answer that I was expecting
but clearly a s
On Thu, Apr 04, 2019 at 06:00:43PM +0200, Mateusz Loskot wrote:
> The list should rather be, in preference/priority order
>
> 1. https://cmake.org/cmake/help/latest/command/target_compile_options.html
> 2. add_compile_options
Yes, it's what I understood from documentation.
> Are you certain you'
Hi Nils,
> From a command line environment where your compiler is properly set up and
> ninja is in PATH configure the root of the project with the Ninja generator
> (currently hardcoded in the tests); use an out of source build directory and
> set the REFERENCE_CMAKE_BIN_DIR cache variable to the
Hi All,
I have a component similar to this setup ...
project(foo LANGUAGES CXX CUDA)
add_library(foo INTERFACE)
target_include_directories(foo INTERFACE )
add_library(bar OBJECT bar.cu)
target_link_libraries(bar PUBLIC foo)
When building *bar*, there is no "-I " in the command line f
Regarding the previous email, below
The method of library construction is to first create an
object library with
add_library(${libname}obj OBJECT ${${LIBNAME}_SOURCES}
${${LIBNAME}_CUDASRCS})
then to create the actual library with
add_library(${libname} $)
and I have tried setting:
se
On Mon, Apr 8, 2019 at 2:07 AM Cook, Steven (G&I)
wrote:
> Hi Nils,
>
>
>
> > Been a while since I looked at this but it still seems to work for me
> in 3.14.0.
>
> > Corresponding elements are generated in files.wxs:
>
>
>
> Can you please tell me the commands you used to run cpack? I did the
>
