unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Peter Polidoro <peter@polidoro.io>
To: help-guix@gnu.org
Subject: CMake cannot find Kicad package input
Date: Mon, 03 Jan 2022 15:04:12 -0500	[thread overview]
Message-ID: <86fsq4pkvw.fsf@polidoro.io> (raw)

Hi,

I am trying to upgrade the Guix Kicad package from version 5.1.10 
to 5.1.12.

When I upgrade the version and hash of the package definition and 
try to build it, it fails with a CMake error saying the 
OpenCascade header files are missing.

"opencascade-oce" is listed as a package input, just as it is for 
version 5.1.10, which seems to build just fine. I see that 
opencascade-oce is installed in my /gnu/store and I see the header 
files are in the include/oce/ directory within it.

One of the Kicad build options may have changed, perhaps requiring 
"-DKICAD_USE_OCE=ON", but it still fails even when I add that.

Another option is to switch from "opencascade-oce" to 
"opencascade-occt" and switch the build option to 
"-DKICAD_USE_OCC=ON". Then opencascade-occt gets installed into 
/gnu/store and I see the header files in the include/opencascade/ 
directory within it. CMake still fails saying it cannot find the 
opencascade header files.

Do I need to put more information in the Kicad package definition 
to get CMake to find the opencascade header files? Or perhaps do I 
need to modify the opencascade package definition to make CMake 
work properly to find the header files.

Thanks!


             reply	other threads:[~2022-01-04 16:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03 20:04 Peter Polidoro [this message]
2022-01-05 18:56 ` CMake cannot find Kicad package input Peter Polidoro

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=86fsq4pkvw.fsf@polidoro.io \
    --to=peter@polidoro.io \
    --cc=help-guix@gnu.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).