Re: New package: mysql_xdevapi

Hello, On 2016-12-07 11:12, Anatol Belski wrote:

Hi,

-----Original Message----- From: Darek Slusarczyk [mailto:dariusz.slusarczyk@oracle.com] Sent: Tuesday, December 6, 2016 1:08 AM To: Johannes Schlüter <johannes.schlueter@oracle.com>; Anatol Belski <anatol.php@belski.net> Cc: 'pecl-dev' <pecl-dev@lists.php.net>; 'Filip Janiszewski' <filip.janiszewski@oracle.com>; 'Andrey Hristov' <php@hristov.com> Subject: Re: [PECL-DEV] New package: mysql_xdevapi [...]

I had some problems with one of protobuf 3.x.y on Linux, but don't remember the exact version number :-} On Win 2.6 should work, the same for 3.0.2. Recently I was also using 3.1.0 for x86 builds.

Ok, so I keep protobuf 3.0.2 and boost 1.62.0 for now. Please let me know, if something changed in between. FYI protobuf 3.1.0 has an issue with x64 build, could be hot patched, though.

OK, I keep eye on win version on daily basis, so will feedback at once in case of any change.

Regarding 001 - the message in pattern matches Unix, but is different on Win 011 - it doesn't pass neither on Win, nor on Unixes (AFAIR it never did)

So 001 can be just forked, or modified to ignore the exact warning text. With 011 seems more investigation needed, if it's supposed to pass. Otherwise, probably a test bug as well.

001 will be fixed soon 011 can be ignored for the moment, some fixes in code of phpcon needed yet

Generally I build binaries according to https://wiki.php.net/internals/windows/stepbystepbuild then copy boost headers (e.g. boost_1_62_0\boost\*) and protobuf install files into deps (for boost into deps/include) in my case it is W:\mysql.php\phpdev\vc14\x86\deps\

Normally, one doesn't need to pollute the deps directory. There are several methods, AFM I use --with-extra-libs and --with-extra-includes to give separate dependency dirs.

OK, thnx for hint. marines