Thanks, that worked for printing a message during our “check” target. Makes
sense for “if (TARGET…)” to truthfully enter if that target name exists. What
threw me off, I think, was having "TARGET test” not actually pass and
misunderstanding the docs that this would embed logic in the generato
>From working on a Homebrew formula <
https://github.com/Homebrew/homebrew/pull/46547> for OpenCoarrays <
https://github.com/sourceryinstitute/opencoarrays> I'm under the impression
that common practice is to use FindMPI over passing mpicc and mpif90 to
cmake directly. Is this correct, and the way
Hello,
I'm trying to build the source package for cmocka 1.0.1 (
https://cmocka.org/files/1.0/cmocka-1.0.0.tar.xz) on MSYS2 and Windows 10,
but when running cmake I get:
C:\cmocka\cmocka-1.0.1\build>cmake .. -DCMAKE_INSTALL_PREFIX=/usr
-DCMAKE_BUILD_TYPE=Release
System is unknown to cmake, create
On 12/04/2015 02:14 PM, Johnson, Hans J wrote:
> PERFORM_CMAKE_TEST(vxl_platform_tests.cxx VCL_STATIC_CONST_INIT_FLOAT)
> NOTE: THIS FAILS WHEN IT SHOULD PASS!
[snip]
> Should I simply add -DCMAKE_CXX_STANDARD:STRING=${CMAKE_CXX_STANDARD}
> to the TRY_COMPILE? The seems too simplistic.
I think th
Any suggestions on how to organise that? Presumably there are
lots of examples in (for example) KDE, but I'm not familiar enough
with that codebase to be able to find them easily.
Currently our GNU Make build builds static libraries in the subdirectories,
then those are put into a big static libra
* Dmitry Marakasov (amdmi3@hades.panopticon) wrote:
> Anyway for now, I did some research and solved the problem of inplace
> vs. systemwide compilation in a way that I find acceptable.
>
> I check for CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT to basically
> know whether a user has explicitly s
