> Sure, but why do you check for atls.lib file ?
Sorry, can't remember.
> CL_X64 is enough for the purpose, isn't it ?
"CL_X64" being non-empty means we are building a 64-bit LibreOffice.
(Yeah, hard to deduce from its name, feel free to change it. I blame
jcorrius, who first did work on a 64-bi
Hello
Late reply
Le Tue, 10 Apr 2012 15:26:02 +0200, Tor Lillqvist a écrit:
# Prefer native x64 compiler to cross-compiler, in case we are running
# the build on a 64-bit OS.
To clarify: this is related to the build of a 64-bit Explorer
extension while building LibreOffice itself in a norm
> # Prefer native x64 compiler to cross-compiler, in case we are running
> # the build on a 64-bit OS.
To clarify: this is related to the build of a 64-bit Explorer
extension while building LibreOffice itself in a normal 32-bit
fashion. It is not related to building a 64-bit LibreOffice.
--tml
Hi Mat,
On 2012-04-09 at 02:17 +0200, Mat M wrote:
> In configure.in, I saw that around line 2750 :
> # Check for 64-bit (cross-)compiler to use to build the 64-bit
> # version of the Explorer extension (and maybe other small
> [SNIP]
>
> AC_MSG_CHECKING([for a x64 compiler and libraries for 64b
Good evening all,
I am checking for usefulness of adding another option for Win builders in
configure.in .
In configure.in, I saw that around line 2750 :
# Check for 64-bit (cross-)compiler to use to build the 64-bit
# version of the Explorer extension (and maybe other small
[SNIP]
AC_MSG_CHE
