[Top][All Lists]

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

[lmi] wx ./configure options

From: Greg Chicares
Subject: [lmi] wx ./configure options
Date: Sat, 27 May 2017 10:44:32 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0

Vadim--It's been a while since we updated the ./configure options in
and I wonder whether there are any we should change. But first of all,
let me ask whether changing these options would make your work more
difficult...because I seem to recall that several years ago you wanted
some adjustments here that would let you reuse the same wx build for
other projects besides lmi, and I don't want to spoil that goal by
making casual changes that create incompatibilities for you without
adding much benefit for anyone else.

One change that I think shouldn't matter to you is to add
However, does that actually have any effect? Specifying it, I see:
  configure ... --disable-webview --enable-no_deps --enable-monolithic
  checking for dependency tracking method... gcc
but there's still a lib/.deps/ directory with 651 files (and I've made
very sure that any such directory created by an earlier build was
removed first).

[BTW, is there any way I can easily see which options were ignored?
On my first attempt, I mistakenly used this:
and I didn't find an error message diagnosing my mistake.]

Is there a way to inhibit PCH? I ask because I believe we determined
that using gcc precompiled headers is actually a pessimization for lmi.
I see a 'wxprec.h.gch' that's 200 MB in case that's relevant.

Should we be using either or both of the following C++11 options?

Isn't the first of these two options:
  --enable-std_iostreams \
  --enable-stl \
implied by the second, so that the first may be removed? (I'm reading
which says
  if test "$wxUSE_STL" = "yes"; then

Currently I'm specifying
which I think is silently ignored. I'm guessing that the defaults for
such 'compat' options are generally appropriate and should not be
overridden without a specific reason.

reply via email to

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