[Top][All Lists]

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

RE: MXE files list generation

From: John D
Subject: RE: MXE files list generation
Date: Mon, 11 Nov 2013 12:36:25 -0500



From: Michael Goffioul [mailto:address@hidden
Sent: Sunday, November 10, 2013 8:17 PM
To: John Donoghue
Cc: Octave Maintainers List
Subject: Re: MXE files list generation


On Sun, Nov 10, 2013 at 8:13 PM, John Donoghue <address@hidden> wrote:

On 11/10/2013 07:44 PM, Michael Goffioul wrote:

On Sun, Nov 10, 2013 at 7:38 PM, John Donoghue <address@hidden> wrote:

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)


Could you be more specific about the breakage? Maybe what's just missing is a line like:




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 ?


I wanted the build tools also covered by the file listing, to be able to have the concept of packages on the build host. That's why I generate 2 file lists: one "native" in <module>.files, and one "complete" in <module>.pkg.




For example:
Failed to build package fltk!
make[3]: Leaving directory `/home/jade/mxe-octave/tmp-fltk/fltk-1.3.1/src'
make[2]: Leaving directory `/home/jade/mxe-octave/tmp-fltk/fltk-1.3.1'
if [ no = no ]; then install -m755 '/home/jade/mxe-octave/tmp-fltk-install/home/jade/mxe-octave/usr/i686-pc-mingw32/bin/fltk-config' '/home/jade/mxe-octave/tmp-fltk-install/home/jade/mxe-octave/usr/bin/i686-pc-mingw32-fltk-config'; fi
install: cannot create regular file ‘/home/jade/mxe-octave/tmp-fltk-install/home/jade/mxe-octave/usr/bin/i686-pc-mingw32-fltk-config’: No such file or directory
make[1]: *** [build-only-fltk] Error 1
make[1]: Leaving directory `/home/jade/mxe-octave'



That's exactly what I was saying. The directory does not exist. It just happened to work before, because the directory got created by another module. IMO the proper fix is to add "$(INSTALL) -d ..." calls; that should have been the case anyway. Then there shouldn't be any problem to use the temporary install directory for those build scripts.





I don’t know if its just me, but the Qt is ignoring the install DESTDIR=$(3)  ?

The log shows DESTDIR being set correctly, but then installs to the prefix set name.

reply via email to

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