unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Pronaip <pronaip@protonmail.com>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Mixing build systems
Date: Fri, 03 May 2019 07:26:21 +0200	[thread overview]
Message-ID: <87muk4glcl.fsf@elephly.net> (raw)
In-Reply-To: <sR133aesLa99N9oYxc6XLzpWsD3-CXgCBTpfXFrAqCZxTJKHfllMO5XfkWoOjHxk10nQnM53Fa1cpo1JhITai9uSl05GknrxMhkfsYtt_JE=@protonmail.com>


Pronaip <pronaip@protonmail.com> writes:

> Hi, I'm (still) trying to build Mininet and it uses both a Makefile
> for building an C executable and setup.py to install its Python
> modules. I looked at the soundconverter package to get some hints for
> mixing build systems but couldn't get very far, I get all sorts of
> (mostly cryptic) error messages, usually about missing modules.

For future messages please always include the error messages.

Looking at the soundconverter package we see this:

    (arguments
     `(#:imported-modules ((guix build python-build-system)
                           (guix build glib-or-gtk-build-system)
                           ,@%gnu-build-system-modules)

       #:modules ((guix build glib-or-gtk-build-system)
                  (guix build utils)
                  ((guix build gnu-build-system) #:prefix gnu:)
                  ((guix build python-build-system) #:prefix python:))

       #:phases …
       ))

What you have is:

      #:imported-modules
      ((guix build python-build-system)
       (guix build gnu-build-system)

       ^— add ,@%gnu-build-system-modules here
       )

      #:modules
      ((guix build utils)
       (guix build python-build-system) #:prefix python:

       ^— wrap this in parentheses

       (guix build gnu-build-system))


Note that the license field is also incorrect.  There is no license by
the name “bsd-style”.

-- 
Ricardo

      reply	other threads:[~2019-05-03  5:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-01 19:53 Mixing build systems Pronaip
2019-05-03  5:26 ` Ricardo Wurmus [this message]

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=87muk4glcl.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=pronaip@protonmail.com \
    /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).