openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthias Seidel <matthias.sei...@hamburg.de>
Subject Re: [openoffice] branch trunk updated: Upgrade bundled expat to 2.2.9.
Date Wed, 02 Oct 2019 22:17:41 GMT
Am 03.10.19 um 00:06 schrieb Don Lewis:
> On  2 Oct, Matthias Seidel wrote:
>> Windows build (42X) breaks:
>>
>> =============
>> Building module expat
>> =============
>>
>> Entering /cygdrive/c/Source/openoffice/main/expat
>>
>> mkdir: cannot create directory
>> './wntmsci12.pro/misc/build/expat-2.2.9/lib': File exists
>> Making: ../../../../../wntmsci12.pro/slo/x64/xmltok.obj
>> mkdir: cannot create directory '../../../../../wntmsci12.pro/slo/x64/':
>> File exists
>> xmltok.c
>> dmake:  Error: -- `../../../../../wntmsci12.pro/slo/x64/loadlibrary.obj'
>> not found, and can't be made
>> dmake:  Error code 255, while making
>> './wntmsci12.pro/misc/build/so_built_so_expat'
> This code is getting executed:
>
> +.IF "$(BUILD_X64)"!=""
> +# ---------------- X64 stuff special ---------------------
> +#  use UNICODE only because shell/shlxthandler
> +#  doesn't link against ascii_expat_xmlparse
> +#---------------------------------------------------------
> +.IF "$(OS)"=="WNT"
> + LOADLIBOBJFILE_X64=$(SLO_X64)/loadlibrary.obj
> +.ELSE
> + LOADLIBOBJFILE_X64=
> +.ENDIF
> +SLOFILES_X64=$(SLO_X64)$/xmlparse.obj \
> +             $(SLO_X64)$/xmlrole.obj \
> +             $(SLO_X64)$/xmltok.obj \
> +             $(LOADLIBOBJFILE_X64)
> +CDEFS_X64+=-DXML_UNICODE -DWIN32
> +CFLAGS_X64+=-I..
> +LIB1TARGET_X64=$(SLB_X64)$/$(TARGET)_xmlparse.lib
> +LIB1OBJFILES_X64=$(SLO_X64)$/xmlparse.obj  $(LOADLIBOBJFILE_X64)
> +LIB2TARGET_X64=$(SLB_X64)$/$(TARGET)_xmltok.lib
> +LIB2OBJFILES_X64=$(SLO_X64)$/xmlrole.obj $(SLO_X64)$/xmltok.obj
> +.ENDIF # "$(BUILD_X64)"!=""
>
> loadlibrary is no longer a part of expat, which is causing the failure.
> I disabled that in the 32-bit build.  The question is why is BUILD_X64
> getting set by configure if you are doing a 32-bit build?  Looks like
> it is controlled by the enable_win_x64_shellext configure flag.  What is
> that supposed to do?

From configure.ac:

--enable-win-x64-shellext
Enable the build/usage of Windows 64bit shell extensions.
These extensions are used for the system integration on
Windows 64bit systems. For example supporting the search
in ODF files with the standard Windows search feature.

Matthias

>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>


Mime
View raw message