Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


On 11/11/13 10:57, Christian Lohmaier wrote:
Hi *,

Am 11.11.2013 10:44 schrieb "soliman Eldebaky" <soliman.mourad@gmail.com
<mailto:soliman.mourad@gmail.com>>:

but i didn't receive any warning   message

the reason for that is that the warning message exists only on master
and not on the libreoffice-4-1 release branch.

 and i installed  vs2012 update 3 and still as it is

Yes, as visual studio itself doesn't contain the file. You need to
download the windows SDK separately. You'll find a link on the wiki page.

Just coping the file into the existing SDK might work or not.. Never
tried. I suggest to use the separate SDK. That is what the release
builds do, and also what configure picks up by default (at least when
using the defaults in the vs/SDK installers).

So so download and install the windows SDK and run autogen.sh again. It
should find the vbs file (look in config_host.mk <http://config_host..mk>).

configure only looks for the VBS file on master, not on the
libreoffice-4-1 branch.

reading the relevant parts of configure.ac on master i get the idea that
the problem could probably be avoided with Visual Studio 2012 by using
the configure option --with-windows-sdk=7.1A  (which is needed anyway if
the builds should run on Win XP).

the commits that introduce the WiLangId configure checks on master are:

08337321e655a3b4991c895de98d96858e60d863
265cc578b0a27c44fda115407d841aa821384b71
3bfe3bfca27dcc4cb00a85c2b30a5a50f5bad689
f351c1399313aab9533bd9b0451a1e7fd76e2204


Context


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.