On Mon, Jun 9, 2014 at 12:55 AM, Lionel Elie Mamane wrote:
>
> Well, essentially this means that TDF build LibreOffice is built with
> a different ODBC ABI than the MacOS X system ODBC ABI. I think it does
> not really matter, because LibreOffice never uses the "wide
> characters" ODBC API. The co
Le 09/06/2014 10:06, Julien Nabet a écrit :
> I had to comment every Mysql/MariaDB options since brew (a repository
> manager) freezed to install mysql connector (at least for some minutes
> when installing Mysql after having retrieved Boost and other components
> + build Mysql with cmake).
>
to build (just simple 32 bits) on Windows with Cygwin and had
failed. Perhaps I'll give a try another time since I was on Vista and now
I've got Seven :-)
Julien
--
View this message in context:
http://nabble.documentfoundation.org/Build-fail-with-MacOs-in-connectivity-part-tp41118
> I had to comment every Mysql/MariaDB options since brew (a repository
> manager) freezed to install mysql connector
Please avoid all 3rd-party software packages when building LO for OS
X. Using such is not supported and will often lead to build problems.
(Unfortunately, yes, this currently mean
On 09/06/2014 09:55, Lionel Elie Mamane wrote:
Well, essentially this means that TDF build LibreOffice is built with
a different ODBC ABI than the MacOS X system ODBC ABI. I think it does
not really matter, because LibreOffice never uses the "wide
characters" ODBC API. The code is there
On Sun, Jun 08, 2014 at 11:04:04AM -0700, Norbert Thiebaud wrote:
> On Sun, Jun 8, 2014 at 10:55 AM, Julien Nabet wrote:
>> Now is the boost_assertion wrong or is there something else to fix?
>> (and which one?)
> I doubt the assertion is wrong there. internally we use 16 bits for
> character re
> I suppose it's 64 bits since config.log displays this:
> build='x86_64-apple-darwin13.2.0'
> build_cpu='x86_64'
> host_cpu='x86_64'
Nope. That is misleading. For Windows, Mac and iOS, we don't use
autofoo to decide whether to build 32- or 64-bit code. Instead, we
build 32-bit, unless you specifi
rwin13.2.0'
build_cpu='x86_64'
host_cpu='x86_64'
Julien
--
View this message in context:
http://nabble.documentfoundation.org/Build-fail-with-MacOs-in-connectivity-part-tp4111804p4111839.html
Sent from the Dev mailing list archive at Nabble.com.
Sorry Lionel, I had just checked my emails, not the forum. I'll take a look
Julien
--
View this message in context:
http://nabble.documentfoundation.org/Build-fail-with-MacOs-in-connectivity-part-tp4111804p4111817.html
Sent from the Dev mailing list archive at Nabbl
On 08/06/2014 20:04, Norbert Thiebaud wrote:
On Sun, Jun 8, 2014 at 10:55 AM, Julien Nabet wrote:
Now is the boost_assertion wrong or is there something else to fix? (and
which one?)
I doubt the assertion is wrong there. internally we use 16 bits for
character representation (OUString)... 32 b
bit build or 64 bit build? (In case
that makes a difference...)
All the code that fails to compile just blindly assumes that an ODBC
Unicode char is 2 bytes (UCS2 or UTF-16 encoding). If that's not true
on MacOS X, then it needs to be adapted :-|
--
Lionel
--
View this message in contex
On Sun, Jun 8, 2014 at 10:55 AM, Julien Nabet wrote:
> Now is the boost_assertion wrong or is there something else to fix? (and
> which one?)
I doubt the assertion is wrong there. internally we use 16 bits for
character representation (OUString)... 32 bit wchar_t will probably
not play well with t
On 08/06/2014 19:29, Norbert Thiebaud wrote:
On Sun, Jun 8, 2014 at 9:05 AM, julien2412 wrote:
--with-system-odbc
Any idea?
Julien
with-system-odbc pick sqlext.h from the 10.8 SDK
it define SQLWCHAR using
#if defined(WIN32)
typedef unsigned short SQLWCHAR;
#else
# include
# if defined
On Sun, Jun 8, 2014 at 9:05 AM, julien2412 wrote:
> --with-system-odbc
>
> Any idea?
>
> Julien
>
with-system-odbc pick sqlext.h from the 10.8 SDK
it define SQLWCHAR using
#if defined(WIN32)
typedef unsigned short SQLWCHAR;
#else
# include
# if defined(__cplusplus) || \
d
unsigned short has a size of 2 bytes.
So it means that WCHAR is made from wchart_t
but then I'm stuck because I don't know where's defined SQL_WCHART_CONVERT
(and what it is)
--
View this message in context:
http://nabble.documentfoundation.org/Build-fail-with-MacOs-in-co
e-bundle-mariadb
--enable-avahi
--enable-eot
--disable-gstreamer-0.10
--enable-gstreamer
--enable-odk
#--with-lang=en-US it fr de es pt ru cs hu pl da sv el sk is nl
--with-lang=ALL
--with-myspell-dicts
--without-junit
Any idea?
Julien
--
View this message in context:
http://nabble.documen
16 matches
Mail list logo
