Windows build: manual mucking with variables

Lionel Elie Mamane lionel at
Mon Feb 6 22:23:11 PST 2012

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
>> and the creation of

>> The following wiki page give some explanations:

> 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

> 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

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
for d in $COMPATH/atlmfc/lib $WINDOWS_SDK_HOME/lib/ATL/${arch} $WINDOWS_SDK_HOME/lib; do
  if test -d "${d}"; then

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?


More information about the LibreOffice mailing list