RE: AW: [sqlite] sqlite and borland c++ builder

2007-04-29 Thread Jonathan Kahn
The attachment someone sent me seemed to do the trick in terms of fixing
compilation errors, some of these other errors I am getting are kind of
unexplainable I think but unrelated to sqlite I think.  Maybe things are
conflicting, I'm not sure though but in terms of any sqlite compilation
issues the files I was sent seemed to clear that up. Now I think it is
strictly c++ builder giving me aggravation for whatever reason.

Thanks
- Jon 

-Original Message-
From: John Stanton [mailto:[EMAIL PROTECTED] 
Sent: Sunday, April 29, 2007 12:50 PM
To: sqlite-users@sqlite.org
Subject: Re: AW: [sqlite] sqlite and borland c++ builder

If that is his only problem all he has to do is some basic definitions 
for his compiler specifyng the Sqlite3 API components he is using.

Michael Ruck wrote:
> If I understand him correctly, he's having issues including the original
> sqlite3.h in his own sources too... He tried to build sqlite again to
solve
> that problem, but it remains there too.
> 
> I would recommed patching up sqlite3.h to conform to BC++ requirements -
> changing those structs to something the compiler understands.
> 
> Mike 
> 
> -Ursprüngliche Nachricht-
> Von: John Stanton [mailto:[EMAIL PROTECTED] 
> Gesendet: Sonntag, 29. April 2007 18:31
> An: sqlite-users@sqlite.org
> Betreff: Re: [sqlite] sqlite and borland c++ builder
> 
> Why not use gcc to compile your library, or use a precompiled DLL?
> 
> Jonathan Kahn wrote:
> 
>>Hi Ulrik,
>>  Thank you for responding.  I'll try anything!  The frustration that all
>>this has brought me I am determined to solve it.  
>>
>>  If I built SQLite with a C compiler what would be the result?  What
> 
> would
> 
>>I be able to work with from within c++?  Won't compiling leave me with an
>>executable?  I am fairly new to dealing with different compilers and
> 
> things,
> 
>>so please forgive my ignorance. 
>>
>>Thanks a lot,
>>- Jon
>>
>>
>>-Original Message-
>>From: Ulrik Petersen [mailto:[EMAIL PROTECTED] 
>>Sent: Sunday, April 29, 2007 2:29 AM
>>To: sqlite-users@sqlite.org
>>Subject: Re: [sqlite] sqlite and borland c++ builder
>>
>>Hi Jon,
>>
>>is it not an option to build SQLite with a C compiler, then call it from 
>>within C++?
>>
>>
>>Regards,
>>
>>Ulrik Petersen
>>
>>
>>Jonathan Kahn wrote:
>>
>>
>>>Even when I try to build a new dll I get errors with attach.c and it says
>>>cannot convert 'void *' to 'Db *', no matter what route I take I always
>>
>>hit
>>
>>
>>>a bump.  I'm just trying anything at this point
>>>
>>>- Jon
>>>
>>>-Original Message-
>>>From: Joe Wilson [mailto:[EMAIL PROTECTED] 
>>>Sent: Sunday, April 29, 2007 1:59 AM
>>>To: sqlite-users@sqlite.org
>>>Subject: Re: [sqlite] sqlite and borland c++ builder 
>>>
>>>I wrote too quickly - sqlite3.h correctly uses __cplusplus for extern
"C".
>>>
>>>But the almalgomated sqlite3.c cannot be compiled from a C++ compiler
>>>for the reasons described below.
>>>
>>>--- Joe Wilson <[EMAIL PROTECTED]> wrote:
>>> 
>>>
>>>
>>>>> When I try to use the header I get errors
>>>>>
>>>>>[C++ Error] sqlite3.h(1778): E2232 Constant member
>>>>>'sqlite3_index_info::nConstraint' in class without constructors
>>>>> 
>>>>
>>>>It appears it is trying to compile the sqlite header file as if it were
>>>>   
>>>
>>>C++.
>>> 
>>>
>>>
>>>>Lemme guess - you're using the almalgomated sqlite3.c from 3.3.17,
right?
>>>>
>>>
>>>>from the generated sqlite3.c:
>>>
>>>>/*
>>>>** Make sure we can call this stuff from C++.
>>>>*/
>>>>#if 0
>>>>extern "C" {
>>>>#endif
>>>>
>>>>See the #if 0? That's the problem. It should be:
>>>>
>>>>#if __cplusplus
>>>>
>>>>SQLite 3.3.17 has a bug in sqlite3.c generation.
>>>>To work around this issue, do this:
>>>>
>>>>extern "C" {
>>>>#include "sqlite3.h"
>>>>}
>>>>
>>>>
>>>>

Re: AW: [sqlite] sqlite and borland c++ builder

2007-04-29 Thread John Stanton
If that is his only problem all he has to do is some basic definitions 
for his compiler specifyng the Sqlite3 API components he is using.


Michael Ruck wrote:

If I understand him correctly, he's having issues including the original
sqlite3.h in his own sources too... He tried to build sqlite again to solve
that problem, but it remains there too.

I would recommed patching up sqlite3.h to conform to BC++ requirements -
changing those structs to something the compiler understands.

Mike 


-Ursprüngliche Nachricht-
Von: John Stanton [mailto:[EMAIL PROTECTED] 
Gesendet: Sonntag, 29. April 2007 18:31

An: sqlite-users@sqlite.org
Betreff: Re: [sqlite] sqlite and borland c++ builder

Why not use gcc to compile your library, or use a precompiled DLL?

Jonathan Kahn wrote:


Hi Ulrik,
 Thank you for responding.  I'll try anything!  The frustration that all
this has brought me I am determined to solve it.  


 If I built SQLite with a C compiler what would be the result?  What


would


I be able to work with from within c++?  Won't compiling leave me with an
executable?  I am fairly new to dealing with different compilers and


things,

so please forgive my ignorance. 


Thanks a lot,
- Jon


-Original Message-
From: Ulrik Petersen [mailto:[EMAIL PROTECTED] 
Sent: Sunday, April 29, 2007 2:29 AM

To: sqlite-users@sqlite.org
Subject: Re: [sqlite] sqlite and borland c++ builder

Hi Jon,

is it not an option to build SQLite with a C compiler, then call it from 
within C++?



Regards,

Ulrik Petersen


Jonathan Kahn wrote:



Even when I try to build a new dll I get errors with attach.c and it says
cannot convert 'void *' to 'Db *', no matter what route I take I always


hit



a bump.  I'm just trying anything at this point

- Jon

-Original Message-
From: Joe Wilson [mailto:[EMAIL PROTECTED] 
Sent: Sunday, April 29, 2007 1:59 AM

To: sqlite-users@sqlite.org
Subject: Re: [sqlite] sqlite and borland c++ builder 


I wrote too quickly - sqlite3.h correctly uses __cplusplus for extern "C".

But the almalgomated sqlite3.c cannot be compiled from a C++ compiler
for the reasons described below.

--- Joe Wilson <[EMAIL PROTECTED]> wrote:




When I try to use the header I get errors

[C++ Error] sqlite3.h(1778): E2232 Constant member
'sqlite3_index_info::nConstraint' in class without constructors



It appears it is trying to compile the sqlite header file as if it were
  


C++.




Lemme guess - you're using the almalgomated sqlite3.c from 3.3.17, right?




from the generated sqlite3.c:



/*
** Make sure we can call this stuff from C++.
*/
#if 0
extern "C" {
#endif

See the #if 0? That's the problem. It should be:

#if __cplusplus

SQLite 3.3.17 has a bug in sqlite3.c generation.
To work around this issue, do this:

extern "C" {
#include "sqlite3.h"
}


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 



  






-




To unsubscribe, send email to [EMAIL PROTECTED]

  






-



  



__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 










-
To unsubscribe, send email to [EMAIL PROTECTED]








-










-



To unsubscribe, send email to [EMAIL PROTECTED]








-













-
To unsubscribe, send email to [EMAIL PROTECTED]






-






-


To unsubscribe, send email to [EMAIL PROTECTED]




-




-
To unsubscribe, send email to [EMAIL PROTECTED]

-



-
To unsubscribe, send email to [EMAIL PROTECTED]
-




-
To unsubscribe, send email to [EMAIL PROTECTED]
-



AW: [sqlite] sqlite and borland c++ builder

2007-04-29 Thread Michael Ruck
If I understand him correctly, he's having issues including the original
sqlite3.h in his own sources too... He tried to build sqlite again to solve
that problem, but it remains there too.

I would recommed patching up sqlite3.h to conform to BC++ requirements -
changing those structs to something the compiler understands.

Mike 

-Ursprüngliche Nachricht-
Von: John Stanton [mailto:[EMAIL PROTECTED] 
Gesendet: Sonntag, 29. April 2007 18:31
An: sqlite-users@sqlite.org
Betreff: Re: [sqlite] sqlite and borland c++ builder

Why not use gcc to compile your library, or use a precompiled DLL?

Jonathan Kahn wrote:
> Hi Ulrik,
>   Thank you for responding.  I'll try anything!  The frustration that all
> this has brought me I am determined to solve it.  
> 
>   If I built SQLite with a C compiler what would be the result?  What
would
> I be able to work with from within c++?  Won't compiling leave me with an
> executable?  I am fairly new to dealing with different compilers and
things,
> so please forgive my ignorance. 
> 
> Thanks a lot,
> - Jon
> 
> 
> -Original Message-
> From: Ulrik Petersen [mailto:[EMAIL PROTECTED] 
> Sent: Sunday, April 29, 2007 2:29 AM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] sqlite and borland c++ builder
> 
> Hi Jon,
> 
> is it not an option to build SQLite with a C compiler, then call it from 
> within C++?
> 
> 
> Regards,
> 
> Ulrik Petersen
> 
> 
> Jonathan Kahn wrote:
> 
>>Even when I try to build a new dll I get errors with attach.c and it says
>>cannot convert 'void *' to 'Db *', no matter what route I take I always
> 
> hit
> 
>>a bump.  I'm just trying anything at this point
>>
>>- Jon
>>
>>-Original Message-
>>From: Joe Wilson [mailto:[EMAIL PROTECTED] 
>>Sent: Sunday, April 29, 2007 1:59 AM
>>To: sqlite-users@sqlite.org
>>Subject: Re: [sqlite] sqlite and borland c++ builder 
>>
>>I wrote too quickly - sqlite3.h correctly uses __cplusplus for extern "C".
>>
>>But the almalgomated sqlite3.c cannot be compiled from a C++ compiler
>>for the reasons described below.
>>
>>--- Joe Wilson <[EMAIL PROTECTED]> wrote:
>>  
>>
  When I try to use the header I get errors

 [C++ Error] sqlite3.h(1778): E2232 Constant member
'sqlite3_index_info::nConstraint' in class without constructors
  
>>>
>>>It appears it is trying to compile the sqlite header file as if it were
>>>
>>
>>C++.
>>  
>>
>>>Lemme guess - you're using the almalgomated sqlite3.c from 3.3.17, right?
>>>
>>>from the generated sqlite3.c:
>>>
>>> /*
>>> ** Make sure we can call this stuff from C++.
>>> */
>>> #if 0
>>> extern "C" {
>>> #endif
>>>
>>>See the #if 0? That's the problem. It should be:
>>>
>>> #if __cplusplus
>>>
>>>SQLite 3.3.17 has a bug in sqlite3.c generation.
>>>To work around this issue, do this:
>>>
>>> extern "C" {
>>> #include "sqlite3.h"
>>> }
>>>
>>>
>>>__
>>>Do You Yahoo!?
>>>Tired of spam?  Yahoo! Mail has the best spam protection around 
>>>http://mail.yahoo.com 
>>>
>>>
>>>
>>
>

> 
>>-
>>  
>>
>>>To unsubscribe, send email to [EMAIL PROTECTED]
>>>
>>>
>>
>

> 
>>-
>>  
>>
>>>
>>
>>
>>__
>>Do You Yahoo!?
>>Tired of spam?  Yahoo! Mail has the best spam protection around 
>>http://mail.yahoo.com 
>>
>>
> 
>

> 
>>-
>>To unsubscribe, send email to [EMAIL PROTECTED]
>>
> 
>

> 
>>-
>>
>>
>>
> 
>

> -
> 
>>To unsubscribe, send email to [EMAIL PROTECTED]
>>
> 
>

> -
> 
>>
>>  
> 
> 
> 
>

> -
> To unsubscribe, send email to [EMAIL PROTECTED]
>

> -
> 
> 
>

-
> To unsubscribe, send email to [EMAIL PROTECTED]
>

-
> 



-
To unsubscribe, send email to [EMAIL PROTECTED]

-



-
To unsubscribe, send email to [EMAIL PROTECTED]
-