For 32 bits it should be a long, for 64 bites, a 64 bit integer type. For example __int64 in Windows.
sqlite3_intptr_t has to be large enough to hold the larger of an integer or a pointer on each platform. We had to fix this too... Gopala Surya wrote: > Hi All > We have been using sqlite version 3.5.7 for our development in a 32 > bit environment. We are moving to 64 bit and I am trying to build > sqlite3.c. > I see that sqlite3.c ver 3.5.7 has a typedef as follows: > > typedef int sqlite3_intptr_t; > > This causes the compiler to complain about incompatibilities in > pointer and int sizes in 64-bit > Now am I safe in changing int to long as in > > typedef long sqlite3_intptr_t; > > After this change I see that my 64 bit build goes through, but I am > not sure as to what other assumptions the code makes regarding these > data types. > Any help shall be greatly appreciated. > Thanks > -Gopala > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
