Re: [lmi] [PATCH] Integrate wxPdfDocument into lmi build system

[Vadim Zeitlin]

On Fri, 07 Aug 2015 16:33:45 +0000 Greg Chicares <address@hidden> wrote:

GC> checking target system type... i686-pc-mingw32
GC> checking for the --enable-debug option... will be automatically detected
GC> checking for the --enable-unicode option... will be automatically detected
GC> checking for the --enable-shared option... will be automatically detected
GC> checking for the --with-toolkit option... will be automatically detected
GC> checking for the --with-wxshared option... will be automatically detected
GC> checking for the --with-wxversion option... will be automatically detected
GC> checking for wx-config... /opt/lmi/local/bin/wx-config-portable
GC> checking for wxWidgets version >= 2.8.0... ./configure: line 2594: test: 
too many arguments
GC> ./configure: line 2597: test: too many arguments
GC> no (version Bad argument --host=i686-pc-mingw32 is not new enough)
GC> configure: error:
GC>     The requested wxWidgets build couldn't be found.

 The error message is bogus, of course, but OTOH configure really can't be
expected to be smart enough that we had pulled the real wx-config out from
underneath it and replaced it with a crude emulation...

GC> That file looks better. Let's try again:
GC> 
GC> /lmi/src/lmi[0]$make $coefficiency -f install_wxpdfdoc.make >../log 2>&1
GC> 
GC> Windows - Out of Virtual Memory

 Hmm, just how much RAM do you have in this VM? I used my usual 4GB for the
lmi build VM and definitely didn't have any problems with this and I think
it should be rare to find any machines used for development with less than
4GB of RAM nowadays.

GC> I may as well update wx while I'm doing this. I've been doing:
GC>   git clone https://github.com/wxWidgets/wxWidgets.git
GC>   git log -1 | head -n1
GC>   commit 0b821adf903872b6d8b56630d2191c5b9c3362e5

 BTW "git log -1 --format=%H" would output the SHA-1 directly (and using
other format specifiers you can get any of the metadata associated with the
commit easily).

GC> to get the sha1sum of the latest commit; is there an easier way to do that
GC> now that we're grabbing '.zip' archives from GitHub?
...
GC> I'd really like to know an effortless way to get the sha1sum of wx HEAD
GC> for future maintenance.

 Sorry, I'm not sure what counts as effortless in this context. Does
opening a web browser, going to https://github.com/wxWidgets/wxWidgets and
looking at the "latest commit" field on this page counts as effortless? It
probably can be automated somehow, too. But OTOH if you want to do it fully
automatically, wouldn't it be better to continue doing "git clone" (perhaps
with "--depth 1" to make it run faster or just keep the previous clone
instead of -- presumably? -- removing it every time so that you could do
"git fetch" to get just the new commits instead of re-downloading
everything) and extract its SHA-1 and, then, maybe even use "git archive"
to create wxWidgets-commit.zip file directly in the lmi cache directory to
avoid having to download it from GitHub (although this will most likely run
into trouble with MD5 checks)?

 I.e. I'd like to help but I'm just not sure what is the problem now, i.e.
what step would you like to skip/automate?
VZ