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


On Mon, Feb 06, 2012 at 03:41:36PM +0100, Regina Henschel wrote:
Norbert Thiebaud schrieb:

I have pushed a series of commit that completely remove
set_soenv.in and the creation of Env.Host.sh/Env.Build.sh

The following wiki page give some explanations:
http://wiki.documentfoundation.org/Development/Build_in_3.6

Up to now I have to put
ATL_LIB="C:/WinDDK/7600.16385.1/lib/ATL/i386"
ATL_INCLUDE="C:/WinDDK/7600.16385.1/inc/atl71"
MFC_LIB="C:/WinDDK/7600.16385.1/lib/Mfc/i386"
MFC_INCLUDE="C:/WinDDK/7600.16385.1/inc/mfc42"
manually into Env.Host.sh

How do I now tell, where to find the files, which are needed for
ATL?

You can put these same lines, but without the double quotes, in
config_host.mk.

However, I don't like the fact that you have to muck with this file
manually. Indeed, your paths seem to be different than what our build
system expects. Maybe we should add options to ./configure to set
these variables directly, or use a more intelligent setup like:

#set arch in some way
if test "$CL_X64" = "YES" ; then
  arch=amd64
else
  arch=i386
fi
for d in $COMPATH/atlmfc/lib $WINDOWS_SDK_HOME/lib/ATL/${arch} $WINDOWS_SDK_HOME/lib; do
  if test -d "${d}"; then
    ATL_LIB="${d}"
    break
  fi
done


I don't understand why in your current setup the path we look in
depends on the value of "$DISABLE_ACTIVEX"... I'd guess it should
rather depend on the version of the compiler / platform sdk /
... being used?

-- 
Lionel

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.