
davidbuzz at gmail
May 15, 2008, 5:15 AM
Post #7 of 20
(1864 views)
Permalink
|
I've just had a quick glance through your patch, and it looks like you have a few really good things in there, and a couple of things I'm uncertain about.... 0) what are you patches against? it seems like you have use an older version of the script, and then diffed against HEAD? these are a lot of changes in the .diff file that I don't think are yours, are they? 1) As you've started installing to /usr/local instead of /usr ... it appears to be so that you can just copy the entire contents of 'local' into 'build' later and delete it! ? That's far from perfect, especially if msys/ming users have other stuff that they have chosen to install into /usr/local/ Perhaps checking if it already exists at the start, and failing would be a reasonable compromise.... "build aborted /usr/local must be empty initially" or some other BS. A better solution (in my view anyway) is to pick-n-choose the precise files needed in the 'build' folder, and copy them into the 'build' folder on-demand. that way, the files aren't re-installed to /usr/local, relocated, and then deleted every time the script is run. the result being that repeat runs are quicker then?. 2) the patches to QT4 (qt4_install_helpers.patch) are definitely something that we want (assuming no-one has any better ideas that avoid patching QT) , so we should get these checked-in to the build script ASAP. 3) ticket 5331/5332 should be reviewed by a dev with commit access (Nigel, or anyone else feeling helpful!) . 4) these tweaks to settings.pro (and plugins settings.pro too) seem a good idea to me too, so I think they should just get committed to the .pro files directly= ! win32:QMAKE_INSTALL_DIR = sh ./cpsvndir win32:DEPENDS += ./ win32:QMAKE_MKDIR = mkdir -p No further comments except to say good work! It's nice to have other people involved, now we just need more ! :-) Buzz. On Thu, May 15, 2008 at 7:41 PM, Arnon Meshoulam (arnonm) <arnonm[at]gmail.com> wrote: > Buzz, > > Just did a complete rebuild, started with PERL only on the machine (no > ming,msys, qt or mythtv) and same result. SEGFault without any output. Given > that QT examples work, I am pretty sure it is out library linking that is > not working - perhaps need to examine the workarounds done for library > names. > > Attached is my latest win32-packager. It builds QT4 distribution end to end. > A few changes I made: > - minor bug fix for qmake QT4 to fix extra installs (aka inc.files=) > - minor fixes to pro files to install properly - ticket 5332 - currently > applied as a patch until it is in head > - installs mythtv first to /usr/local/ and then to build. This resolves the > depedencies for mythplugins and also gives a stable install > > No code changes to myth- all are related to qmake installation routines > > Arnon > > On 5/15/08, Arnon Meshoulam (arnonm) <arnonm[at]gmail.com> wrote: >> >> Arnonm, >> >> You are not alone, I got these exact same symptoms yesterday when I got my >> Win32 build built. I assumed I'd screwed up, and was going to try again >> from scratch tonite, but now I feel better about my situation. :-) >> >> All Applications crash IMMEDIATELY, with nothing but a SIGSEV. no GUI, no >> output, nothing. same symptoms on all .exe's: backend, frontend, >> welcome, etc. >> >> Buzz. > _______________________________________________ mythtv-dev mailing list mythtv-dev[at]mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
|