From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: guix-devel@gnu.org
Subject: Re: Stuck on KiCad dependency wxPython
Date: Tue, 12 Jul 2016 11:24:57 +0200 [thread overview]
Message-ID: <87oa63jjiu.fsf@gnu.org> (raw)
In-Reply-To: <idjshvktp01.fsf@bimsb-sys02.mdc-berlin.net> (Ricardo Wurmus's message of "Fri, 8 Jul 2016 12:15:10 +0200")
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:
> Leo Famulari <leo@famulari.name> writes:
>
>> On Thu, Jul 07, 2016 at 09:31:20AM +0300, Efraim Flashner wrote:
>>> /gnu/store/h38zwyj2a64dpai99gavv3anhk303xyp-wxwidgets-3.0.2/include/wx-3.0/wx/wx.h
>>>
>>> looks like you'll need (string-append "-I" (assoc-ref %build-inputs
>>> "wxwidgets") "/include/wx-3.0") as a configure flag
>>
>> Unfortunately, it has no effect as #:make-flag.
>
> Do you mean “#:configure-flags”?
>
>> ./configure exits with an error, as it doesn't recognize the option.
>
> In these cases I normally augment the CPATH environment variable.
Or you can do:
./configure CPPFLAGS=-I/foo/bar
Perhaps that’s what Efraim meant.
Ludo’.
next prev parent reply other threads:[~2016-07-12 9:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 7:40 [PATCH] gnu: add kicad Danny Milosavljevic
2016-02-15 11:35 ` Ben Woodcroft
2016-05-23 4:13 ` Leo Famulari
2016-07-07 0:22 ` Stuck on KiCad dependency wxPython Leo Famulari
2016-07-07 6:31 ` Efraim Flashner
2016-07-08 0:51 ` Leo Famulari
2016-07-08 10:15 ` Ricardo Wurmus
2016-07-12 9:24 ` Ludovic Courtès [this message]
2016-09-22 8:27 ` Danny Milosavljevic
2016-09-22 8:45 ` Danny Milosavljevic
2016-09-22 9:26 ` python-build-system: Allow build flags Danny Milosavljevic
2016-09-22 10:43 ` [PATCH] guix: python-build-system: Honor configure-flags also when building Danny Milosavljevic
2016-09-22 9:10 ` Stuck on KiCad dependency wxPython Danny Milosavljevic
2016-09-30 0:51 ` Theodoros Foradis
2016-09-30 7:09 ` Danny Milosavljevic
2016-08-03 23:54 ` [PATCH] gnu: add kicad Danny Milosavljevic
2016-08-04 8:31 ` Andreas Enge
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=87oa63jjiu.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).