Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


Rather than hard-coding a path, I presume our build system has a
variable for "the path to the Windows SDK". Also, rather than me (not
having a Microsoft Windows development environment) trying "blindly"
and relying on tinderboxes to test the build, I was hoping someone
having a Microsoft Windows development environment "ready to build"
LibreOffice would take care of it.

I doubt the reference to the "Microsoft SQL Server" directories are
necessary or useful in our case. Also, this seems to be an example for
the older "Microsoft Data Access SDK" which is from... 2004
(http://www.microsoft.com/en-us/download/details.aspx?id=21995).

http://msdn.microsoft.com/en-us/library/windows/desktop/ms692882%28v=vs.85%29.aspx
says it is now "Included with Windows" and "not available separately",
which makes me think it is in the Platform SDK.

On Tue, Sep 16, 2014 at 08:20:49PM +0200, Robert Antoni Buj i Gelonch wrote:
OK, try it again setting the following environment variables:

LIB=c:\Program Files\Microsoft Data Access SDK
2.8\Libs\x86\lib;C:\Program Files\Microsoft SQL
Server\100\Tools\SDK\Lib;
INCLUDE=c:\Program Files\Microsoft Data Access SDK 2.8\inc;C:\Program
Files\Microsoft SQL Server\100\Tools\SDK\Include;


REF: http://msdn.microsoft.com/en-us/library/ms131310.aspx

Regards,
Robert

On Tue, Sep 16, 2014 at 7:24 PM, Lionel Elie Mamane <lionel@mamane.lu>
wrote:

No driver is not used at build time. The driver used at runtime is
whichever driver the user asks for, usually via a DSN (that is, the
driver that the DSN is for). The MySQL driver to connect to MySQL, one
of the multiple PostgreSQL drivers to connect to PostgreSQL, the DB/2
driver to connect to DB/2, etc, etc.

I refer to the headers provided by the OSDBC "meta-system" (the driver
manager if you want), which is a "system part" of Microsoft Windows,
under the umbrella of MDAC (Microsoft Data Access Components).

On Tue, Sep 16, 2014 at 07:11:14PM +0200, Robert Antoni Buj i Gelonch
wrote:
What odbc driver are you using for Windows?

http://en.wikipedia.org/wiki/Open_Database_Connectivity#Drivers

On Tue, Sep 16, 2014 at 5:59 PM, Lionel Elie Mamane <lionel@mamane.lu>
wrote:

I've discovered (via the tinderboxes...) that --with-system-odbc
doesn't work on Microsoft Windows. Microsoft Windows is the "reference
platform" of ODBC (the platform that *defines* ODBC), I had *much*
*much* rather we use (on the reference platform) the headers provided
by the platform, rather than some headers meant for ANOTHER platform
(namely, Unix) which *try* to be compatible (and maybe are in a
bug-free way, but why take the risk).

So, if some LibreOffice developer with Microsoft Windows experience
could debug why "--with-system-odbc" doesn't find the ODBC headers on
Windows, I'd be very grateful. I expect they are in the platform SDK,
maybe in some optional part of it, ...

Thanks in advance.

On Tue, Sep 16, 2014 at 02:59:31PM +0200, Jan Holesovsky wrote:
Hi Lionel,

kendy@suse.cz píše v Út 16. 09. 2014 v 12:03 +0000:

checking for sqlext.h... no
configure: error: odbc not found. install odbc
Error running configure at /home/tinderbox/master/autogen.sh line
258.

I've reverted the 'Use system ODBC on MS Windows unless specifically
overriden' for now, it breaks the Windows tinderboxes...

All the best,
Kendy



_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice









Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.