all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: ng0 <ng0@infotropique.org>
Cc: guix-devel@gnu.org
Subject: Re: yamlcpp policy?
Date: Sat, 22 Jul 2017 12:15:24 +0200	[thread overview]
Message-ID: <87fudoaibn.fsf@elephly.net> (raw)
In-Reply-To: <20170721163537.3bykjvogb6wf7f3g@abyayala>


ng0 <ng0@infotropique.org> writes:

> I picked up my supercollider package again.
> At the very beginning of the cmake build (configure) I can see this:
>
> -- Found YAMLCPP: /gnu/store/d54zy49pbzsyfviqhjlwdsavgg6mx3w7-yaml-cpp-0.5.3/include  
> CMake Warning (dev) at external_libraries/hidapi/CMakeLists.txt:3 (project):
>   Policy CMP0048 is not set: project() command manages VERSION variables.
>   Run "cmake --help-policy CMP0048" for policy details.  Use the cmake_policy
>   command to set the policy and suppress this warning.
>
>   The following variable(s) would be set to empty:
>
>     PROJECT_VERSION
>     PROJECT_VERSION_MAJOR
>     PROJECT_VERSION_MINOR
>     PROJECT_VERSION_PATCH
> This warning is for project developers.  Use -Wno-dev to suppress it.
>
>
> Is this our intention for yamlcpp, or do we just have no other way to
> specify it other than setting the variables ourselves in packages?

Is this a fatal warning or can we ignore it?

Without the context I don’t know what it’s trying to do.  Make sure it
isn’t trying to build the package from source again.  It seems to me
that it shouldn’t need this information when it’s just using the
existing package.

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

  reply	other threads:[~2017-07-22 10:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-21 16:35 yamlcpp policy? ng0
2017-07-22 10:15 ` Ricardo Wurmus [this message]
2017-07-22 11:42   ` ng0

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fudoaibn.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=ng0@infotropique.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.