[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MXE files list generation

From: John Donoghue
Subject: Re: MXE files list generation
Date: Sun, 10 Nov 2013 19:38:17 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0

On 11/07/2013 03:28 AM, address@hidden wrote:
essage: 2
Date: Wed, 6 Nov 2013 23:46:09 -0500
From: Michael Goffioul<address@hidden>
To: "John W. Eaton"<address@hidden>,    Octave Maintainers List
Subject: MXE files list generation
Content-Type: text/plain; charset="iso-8859-1"


I'd like to add a system to MXE that generates a files list for the
compiled packages. Eventually, I intend to use that information to build a
smarter installer and/or separate installers. The footprint on the current
compilation process should be minimal.

I've attached a prototype. The patch generate-file-list implements the
functionality in the core Makefile: it passes additional arguments to
$(PKG)_BUILD macro to be used as prefix and DESTDIR, then it generates a
files list and copy over the installed files into the real installation

I've also provided an example of changes required on the cURL module.

Do you agree with the concept?



I see few things that have broken in mxe build where files from the host build were copied to the build folders (config scripts etc) I have changed a few of these back to install to the BUILD_TOOLS_PREFIX (not the temp build dir)

My question on these and all the build_xxx tools - do these need be treated in the new way for the install, or since they are not part of what will be distributed, should/need be out of the install ?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]