Skip to Content.
Sympa Menu

freetds - Re: [freetds] MinGW + Windows

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: Harry Sfougaris <hsfougaris AT gmail.com>
  • To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
  • Subject: Re: [freetds] MinGW + Windows
  • Date: Fri, 7 May 2010 18:47:33 +0300

Are you using db-library, or the ODBC thing?
I am trying to use db-library, and I don't have odbc*.lib and FreeTDS.lib
linked.

Thanks,
Harry

On 07 Μαϊ 2010, at 6:40 μ.μ., Paul Thurston wrote:

> Harry:
>
> In VC9, here are the list of additional libraries I needed to link into to
> my "hello SQL" app to drive FreeTDS:
>
> ws2_32.lib
> odbc32.lib
> odbccp32.lib
> FreeTDS.lib
> dblib.lib
> libTDS.lib
>
> Best,
>
> Paul
>
>
> From: freetds-bounces AT lists.ibiblio.org
> [mailto:freetds-bounces AT lists.ibiblio.org] On Behalf Of Harry Sfougaris
> Sent: Friday, May 07, 2010 11:38 AM
> To: FreeTDS Development Group
> Subject: Re: [freetds] MinGW + Windows
>
>
>
>
> On 07 Μαϊ 2010, at 4:46 μ.μ.,
> jklowden AT schemamania.org<mailto:jklowden AT schemamania.org> wrote:
>
>
>
>> On Fri, May 07, 2010 at 07:26:06AM +0300, Harry Sfougaris wrote:
>
>>> I'm not interested in doing it from the command line (as opposed to from
>>> within Visual Studio), but rather to compile it with a different compiler.
>
>>
>
>> Perhaps if you post the link command and the first 10 so errors, we'll be
>> able to help. Also, how was Qt compiled?
>
>>
>
> Well I don't even know how to get started...
>
> The only thing I found was to download msys, so I can run configure and
> make.
>
> This creates libsybdb.a, libsybdb.dll.a mad libsybdb.la files.
>
> Is this what I should be doing to start with?
>
> I really have no idea how Qt was compiled; it is the download LGPL version
> 4.6.2 from their website.
>
> What exactly should I look for?
>
>
>
>> FreeTDS is a C library. On a Windows platform it will take the form of a
>> COFF binary, no matter what compiler is used. As I'm sure you know, the
>> *compiler* per se just converts C to object code. But it can be told to
>> make certain assumptions with every header file about the libraries its
>> output will be linked to. For everything to work properly, all components
>> in the final executable need to share a single definition of each global
>> name e.g. strcpy(3). If some of your code is linked to glibc and other to
>> Microsofts's C runtime library, I'd expect problems.
>
>>
>
> That's the issue I think when compiling with Visual Studio, and trying to
> use the .lib with Qt.
>
>
>
>> HTH.
>
>>
>
>> --jkl
>
>> _______________________________________________
>
>> FreeTDS mailing list
>
>> FreeTDS AT lists.ibiblio.org<mailto:FreeTDS AT lists.ibiblio.org>
>
>> http://lists.ibiblio.org/mailman/listinfo/freetds
>
>
>
> Harry Sfougaris
>
>
>
>
>
>
>
>
>
> _______________________________________________
>
> FreeTDS mailing list
>
> FreeTDS AT lists.ibiblio.org<mailto:FreeTDS AT lists.ibiblio.org>
>
> http://lists.ibiblio.org/mailman/listinfo/freetds
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds

Harry Sfougaris








Archive powered by MHonArc 2.6.24.

Top of Page