unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
* Pre-compiled .exe-files for other target-plaforms
@ 2016-10-02  8:56 Hartmut Goebel
  2016-10-02 18:47 ` Leo Famulari
  0 siblings, 1 reply; 2+ messages in thread
From: Hartmut Goebel @ 2016-10-02  8:56 UTC (permalink / raw)
  To: guix-devel

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.

[1]
https://docs.python.org/2/distutils/builtdist.html#creating-windows-installers

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Pre-compiled .exe-files for other target-plaforms
  2016-10-02  8:56 Pre-compiled .exe-files for other target-plaforms Hartmut Goebel
@ 2016-10-02 18:47 ` Leo Famulari
  0 siblings, 0 replies; 2+ messages in thread
From: Leo Famulari @ 2016-10-02 18:47 UTC (permalink / raw)
  To: Hartmut Goebel; +Cc: guix-devel

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.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2016-10-02 18:47 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-10-02  8:56 Pre-compiled .exe-files for other target-plaforms Hartmut Goebel
2016-10-02 18:47 ` Leo Famulari

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).