unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Pre-compiled .exe-files for other target-plaforms
Date: Sun, 2 Oct 2016 14:47:18 -0400	[thread overview]
Message-ID: <20161002184718.GA32233@jasmine> (raw)
In-Reply-To: <57F0CBD9.4060903@crazy-compilers.com>

On Sun, Oct 02, 2016 at 10:56:57AM +0200, Hartmut Goebel wrote:
> Hi,
> 
> I discovered that Python setuptools includes pre-compiled .exe files.
> First I thought, these can be savely removed from the source. But when I
> researched on this, I found [1] saying: " These installers can even be
> created on Unix platforms or Mac OS X."
> 
> This means, these .exe files have to be included in our distribution,
> too. (One may still need to ask the Python developers, resp. the
> setuptools developers whether this is true and how this is supposed to
> work.)
> 
> Normally we remove all pre-compliled stuff, don't we? So how should we
> handle this case? We would need to cross-build these .exe files., which
> are available for x86, amd64 and arm.

It doesn't look like these binary files get installed in our setuptools
package; they are present in the source code. Do they get compiled into
the setuptools that we build? If not it seems safe to remove them in an
origin snippet.

      reply	other threads:[~2016-10-02 18:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-02  8:56 Pre-compiled .exe-files for other target-plaforms Hartmut Goebel
2016-10-02 18:47 ` Leo Famulari [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=20161002184718.GA32233@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=h.goebel@crazy-compilers.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).