On Wed, Dec 5, 2012 at 12:25 AM, Tor Lillqvist <tml@iki.fi> wrote:
Anyway, about killing the --directx-home option, even if that is done,
that does not mean having and building against the DirectX SDK (June
2010, or some earlier version) would be mandatory. It would just mean
that if the standard DXSDK_DIR environment variable does not exist,
then DirectX use is not built, i.e. like --disable-directx.
Probably the explicit --disable/enable-directx option can be removed
too; if $DXSDK_DIR exists and is valid, build against it, otherwise
not (and give a warning that the resulting build lacks functionality
and should probably not be distributed in a serious way). Why would
this need to be a configure option?
to be able to reproduce a scenario: build using the same config than
the one that broke ?
Norbert
Context
- Re: Reworking the MSVC-related build options (continued)
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.