From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: yamlcpp policy? Date: Sat, 22 Jul 2017 12:15:24 +0200 Message-ID: <87fudoaibn.fsf@elephly.net> References: <20170721163537.3bykjvogb6wf7f3g@abyayala> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45146) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dYrRl-0006aa-Az for guix-devel@gnu.org; Sat, 22 Jul 2017 06:15:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dYrRf-0006Um-Su for guix-devel@gnu.org; Sat, 22 Jul 2017 06:15:41 -0400 Received: from sender-of-o51.zoho.com ([135.84.80.216]:21075) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dYrRf-0006U8-HL for guix-devel@gnu.org; Sat, 22 Jul 2017 06:15:35 -0400 In-reply-to: <20170721163537.3bykjvogb6wf7f3g@abyayala> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: ng0 Cc: guix-devel@gnu.org ng0 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