> On 17 Jan 2019, at 04:57, Jan Wielemaker wrote:
>
> I got very far using
>
>set(CMAKE_C_FLAGS -m32)
Maybe not going to solve your main issue but worth changing anyway to:
set(CMAKE_C_FLAGS "-m32 ${CMAKE_C_FLAGS}")
With your previous and simpler code, passing any cmake
-D
You can file an enhancement request that the $
generator expression to be relaxed to include STATIC, SHARED, and
MODULE libraries.
My suggestion is that a dummy source file to workaround the Xcode
limitation on targets, is not as hacky
as reverse engineering the object file locations.
On Wed, Fe
On Wed, 2019-02-27 at 08:39 -0500, Robert Maynard wrote:
> CMake only provides an official way to get the location of the object
> files for OBJECT targets ( $ ). For other
> target types the location is an implementation detail.
Yes, but sometimes (as in my case) I need to know it :). I need to
If `interfaceDep` is an actual interface target, consuming libraries
of libA inside the project ( example ) should resolve it as an
interface target and not drop it on the lnik line.
If you have a small self contained example that would help track down
this issue.
On Thu, Feb 21, 2019 at 5:49 AM
You need to guard the flags with `$` the
evaluation on a given compiler id is done for all sources of a target,
and not on each target source file.
So you will need something like:
set(cxx_flags "$<$,$>:-Wall
-Wextra -pedantic>
$<$:/W4")
target_compi
On 2/26/19 10:30 AM, Mathieu Garaud wrote:
> While compiling cmake3.13.4 using pkgsrc I had an error because I'm using a
> new version of clang7.0.1 witth an old version of libstdc++5.4.0.
Thanks. For reference in list archives, Mathieu opened a MR here:
https://gitlab.kitware.com/cmake/cmake/
CMake only provides an official way to get the location of the object
files for OBJECT targets ( $ ). For other
target types the location is an implementation detail.
On Sat, Feb 23, 2019 at 3:24 PM Paul Smith wrote:
>
> Hi all. I'm using CMake 3.13.4 across Linux, MacOS, and Windows, with
> var
Hi,
since the last makeover of CMake for ParaView, I have trouble with MPI
configuration, similar as described in here:
https://gitlab.kitware.com/cmake/cmake/issues/18570
I made an entry onto ParaView's discourse two weeks ago with no response:
https://discourse.paraview.org/t/could-not-fin