From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 42791 invoked by alias); 15 Nov 2016 12:10:43 -0000 Mailing-List: contact libffi-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libffi-discuss-owner@sourceware.org Received: (qmail 42742 invoked by uid 89); 15 Nov 2016 12:10:41 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=H*Ad:U*libffi-discuss, yen, $PREFIX, H*r:sk:libffi- X-HELO: mail-qt0-f175.google.com Received: from mail-qt0-f175.google.com (HELO mail-qt0-f175.google.com) (209.85.216.175) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 15 Nov 2016 12:10:31 +0000 Received: by mail-qt0-f175.google.com with SMTP id p16so68442129qta.0 for ; Tue, 15 Nov 2016 04:10:31 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=HFlZubKkUTC2LhzzbzpFPFCkn2yz0GmpB69iRBKWLyY=; b=FJgr0yUCRkyndbkFPrS+WrAeWks2Yo0vZhY22BKr9V5dqu/oEu2akuIxyeOERGou7A krdP+vUJ2aXIy3HA5+hW7S0qGaqsOuVjGfnJW0C1BcotBqI1ycAK0JMRq+P0fwQia33n iQLgfiCBrq4PCQJQHYUT+zpvcxgLWoI9k0mn8jR352timBXWN1ZQg5BRvZbqF4EZVYjM EIs6rCuyk3ISofCfGm7dzr5FgaeEPVrQ46POjwC2mj4LAQTNsfxEewW2gTIhZB/d75Oj 8Ywy4DluCDfV2sTwDZR6/w2nv0j9QzADzOdWA9UmpZNE1S+L4YPLaa3C0asT7b6v4zdm 5Tlw== X-Gm-Message-State: ABUngvcvB+gGfAVBkAFmRcFse7hPL6s4PHLvEqueG34b9YuI4HukZOOrEsVGyQbINuSzYDM+tK2WL1Rk94OeUw== X-Received: by 10.200.55.61 with SMTP id o58mr13832088qtb.6.1479211829715; Tue, 15 Nov 2016 04:10:29 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.138.101 with HTTP; Tue, 15 Nov 2016 04:10:29 -0800 (PST) From: Chi-Hsuan Yen Date: Tue, 15 Nov 2016 12:10:00 -0000 Message-ID: Subject: Install public headers in the standard path? To: libffi-discuss@sourceware.org Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2016/txt/msg00053.txt.bz2 Hello libffi enthusiasts, Currently libffi public headers are installed in $PREFIX/lib/libffi-3.x.y/include. The only reliable approach to get the include path is via pkg-config. There are some disadvantages: 1. pkg-config is tricky in terms of cross-compilation. To cross-build libffi clients, PKG_CONFIG_LIBDIR, PKG_CONFIG_SYSROOT_DIR, PKG_CONFIG_ALLOW_SYSTEM_{CFLAGS,LIBS} may be involved to make it working 2. pkg-config does not come with macOS. Recently CPython is seeking for chances to drop bundled libffi copy. [1] However, CPython core developers are against including additional tools other than XCode/Command Line Tools in CPython build time requirements There are some more discussions here: https://github.com/libffi/libffi/issues/258 As a result, I suggest to move header files to conventional $PREFIX/include, so that libffi clients can have simpler build systems. Here's my implementation: https://github.com/libffi/libffi/pull/288 Any ideas? Best, Yen, Chi-Hsuan [1] http://bugs.python.org/issue28491