|
From: | Michael Goffioul |
Subject: | Re: MXE files list generation |
Date: | Sun, 10 Nov 2013 19:44:16 -0500 |
On 11/07/2013 03:28 AM, octave-maintainers-request@octave.org wrote:
essage: 2
Date: Wed, 6 Nov 2013 23:46:09 -0500
From: Michael Goffioul<michael.goffioul@gmail.com>
To: "John W. Eaton"<address@hidden>, Octave Maintainers List
<address@hidden>
Subject: MXE files list generation
Message-ID:
<CAB-99LtWNaHVZ28h+KAnAf6cgfZOXVJ6DKO515JyC6+address@hidden>
Content-Type: text/plain; charset="iso-8859-1"
John,
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
directory.
I've also provided an example of changes required on the cURL module.
Do you agree with the concept?
Michael.
Michael,
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 ?
[Prev in Thread] | Current Thread | [Next in Thread] |