Re: [sqlite] SQLite does not support ARM platform?

2017-03-20 Thread Jens Alfke

> On Mar 20, 2017, at 3:38 PM, Jaime Stuardo  wrote:
> 
> That is why I suspect about SQLite3 to be really multiplatform. Why can my 
> own C++ program, that is not small, be successfully compiled and then run in 
> the machine? Why cannot SQLite source code?

You’re using a nine-year-old compiler, and targeting an OS that’s been obsolete 
for years. There’s nothing intrinsically wrong with that (retro computing is 
cool!), but if something goes wrong you really shouldn’t blame the (up-to-date) 
software you’re trying to compile.

I’m sure if I tried to compile SQLite for a Macintosh SE using a version of 
Lightspeed C from 1990, I’d have worse problems ;-)

—Jens
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] No public bug tracker?

2017-03-20 Thread Simon Slavin

On 21 Mar 2017, at 2:25am, Yuri  wrote:

> Does this mean that this issue will be fixed:

Not necessarily.  It does mean that the development team will know about it.  
They may decide it’s not a bug, or that it’ll take a long time to fix, or have 
to decide whether to change the documentation or the program.  Or have 
something better to do.

Whichever it is, there’s no need to report the issue again.

Simon.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] No public bug tracker?

2017-03-20 Thread Yuri

On 03/20/2017 17:11, Simon Slavin wrote:

You can report bugs by posting here.  The development team will see them.

It sometimes takes a little time to get a reaction while they discuss things 
between themselves to figure out what to do.


Does this mean that this issue will be fixed:

> A few days ago I reported the problem with configure script and 
thread safety options. configure option --enable-threadsafe only 
supports two values for SQLITE_THREADSAFE, 0 and 1, while documentation 
says that the allowed values are 0,1,2. There was no answer, while this 
appears to be a valid problem.



?


Yuri

___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] No public bug tracker?

2017-03-20 Thread Yuri

On 03/20/2017 17:20, Joshua J. Kugler wrote:

If you go here:

https://www.sqlite.org/src/login

You can see you can log in (if you have an account), or:

"Visitors may enter anonymous as the user-ID with the 8-character hexadecimal
password shown below."



sqlite.org/src/login  shows that I am logged in, but the bug site says I am not 
logged in. I am not sure if this is intentional. I assumed it was.

Yuri

___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] No public bug tracker?

2017-03-20 Thread Joshua J. Kugler
On Monday, March 20, 2017 5:00:21 PM AKDT Yuri wrote:
> Your bug tracker http://www.sqlite.org/src/rptview?rn=1 doesn't accept
> public submissions.
> A few weeks ago I reported (in this ML) the bug with blob handle being
> invalidated by the writes into unrelated tables.
> fossil timeline doesn't  show this bug as fixed, and the above bug site
> doesn't show it too.
> 
> Is there anything to assure that this bug isn't forgotten?
> 
> A few days ago I reported the problem with configure script and thread
> safety options. configure option --enable-threadsafe only supports two
> values for SQLITE_THREADSAFE, 0 and 1, while documentation says that the
> allowed values are 0,1,2. There was no answer, while this appears to be
> a valid problem.
> 
> Isn't it better to have a separate bug report for every issue?

If you go here:

https://www.sqlite.org/src/login

You can see you can log in (if you have an account), or:

"Visitors may enter anonymous as the user-ID with the 8-character hexadecimal 
password shown below."

j

-- 
Joshua J. Kugler - Fairbanks, Alaska
Azariah Enterprises - Programming and Website Design
jos...@azariah.com - Jabber: pedah...@gmail.com
PGP Key: http://pgp.mit.edu/  ID 0x73B13B6A
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


[sqlite] configure --enable-shared doesn't build shared libraries

2017-03-20 Thread Yuri

Configure file says:

>   --enable-shared[=PKGS]  build shared libraries [default=yes]

However, shared library isn't built by default. This command:

$ ./configure --enable-shared && gmake

doesn't build it either.


Yuri


___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] No public bug tracker?

2017-03-20 Thread Simon Slavin

On 21 Mar 2017, at 12:00am, Yuri  wrote:

> Isn't it better to have a separate bug report for every issue?

You can report bugs by posting here.  The development team will see them.

It sometimes takes a little time to get a reaction while they discuss things 
between themselves to figure out what to do.

Simon.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


[sqlite] No public bug tracker?

2017-03-20 Thread Yuri
Your bug tracker http://www.sqlite.org/src/rptview?rn=1 doesn't accept 
public submissions.
A few weeks ago I reported (in this ML) the bug with blob handle being 
invalidated by the writes into unrelated tables.
fossil timeline doesn't  show this bug as fixed, and the above bug site 
doesn't show it too.


Is there anything to assure that this bug isn't forgotten?

A few days ago I reported the problem with configure script and thread 
safety options. configure option --enable-threadsafe only supports two 
values for SQLITE_THREADSAFE, 0 and 1, while documentation says that the 
allowed values are 0,1,2. There was no answer, while this appears to be 
a valid problem.


Isn't it better to have a separate bug report for every issue?

Yuri

___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] SQLite does not support ARM platform?

2017-03-20 Thread Jaime Stuardo
Thanks a lot...

I have finally got it to compile (DLL was generated), but a lot of warnings 
appeared. Warnings of all of this kind:

"warning C4244: 'function' : conversion from 'i64' to 'int', possible loss of 
data  c:\WorkingFolder\Proyectos\Lean\RFID\SQLite3\btree.c "
" warning C4244: 'function' : conversion from 'i64' to 'u32', possible loss of 
data c:\WorkingFolder\Proyectos\Lean\RFID\SQLite3\btree.c "
"warning C4018: '>' : signed/unsigned mismatch  
c:\WorkingFolder\Proyectos\Lean\RFID\SQLite3\btree.c"

And a lot of similar warnings. 82 in total.


Can I safely ignore them?

Regards
Jaime

-Original Message-
From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On 
Behalf Of Jim Borden
Sent: lunes, 20 de marzo de 2017 19:54
To: SQLite mailing list 
Subject: Re: [sqlite] SQLite does not support ARM platform?

Oh, you are talking about WinCE?  I don’t think you should be thinking in terms 
of “ARM vs non-ARM” but rather “X platform vs Y platform.”  As others have 
noted, sqlite obviously runs on ARM and the issue is not with sqlite but with 
the way you are trying to compile it or the platform you are trying to compile 
it for.  It totally slipped my mind that WinCE would probably be ARM as well 
(and honestly I didn’t even realize it was still around!).  

I think WinCE has its own build for sqlite:  
http://sqlite-wince.sourceforge.net/ probably due to rather extreme limitations.

On 2017/03/21 7:41, "sqlite-users on behalf of Jaime Stuardo" 
 wrote:

I use to develop mobile applications for years using VS 2008, and in fact, 
I have just developed a MFC C++ application that runs in the ARM machine 
without problem. I need to use SQLite3 for my application. That is why I need 
to compile it.




> On 20 Mar 2017, at 23:17, Jaime Stuardo  wrote:
> 
> Thanks all who answered.
> 
> Yes... it seems a MSVC limitation, however, it is very strange. I am 
using Visual Studio 2008 which does support ARM compilation.  I did that, 
adding some compiler switches for target WIN32_CE but I got million of 
warnings, of this type:
> 
> sqlite3.c(166) : warning C4005: 'OS_VXWORKS' : macro redefinition
>sqlite3.c(158) : see previous definition of 'OS_VXWORKS'
> sqlite3.c(216) : warning C4005: 'GCC_VERSION' : macro redefinition
>sqlite3.c(214) : see previous definition of 'GCC_VERSION'
> sqlite3.c(222) : warning C4005: 'CLANG_VERSION' : macro redefinition
>sqlite3.c(220) : see previous definition of 'CLANG_VERSION'
> sqlite3.c(227) : warning C4005: 'MSVC_VERSION' : macro redefinition
>sqlite3.c(225) : see previous definition of 'MSVC_VERSION'
> sqlite3.c(10924) : warning C4005: 'SQLITE_DEFAULT_PAGE_SIZE' : macro 
redefinition
>sqlite3.c(10920) : see previous definition of 
'SQLITE_DEFAULT_PAGE_SIZE'
> sqlite3.c(10939) : warning C4005: 'SQLITE_MAX_DEFAULT_PAGE_SIZE' : macro 
redefinition
>sqlite3.c(10935) : see previous definition of 
'SQLITE_MAX_DEFAULT_PAGE_SIZE'
> sqlite3.c(11015) : warning C4005: 'SQLITE_INT_TO_PTR' : macro redefinition
>sqlite3.c(11012) : see previous definition of 'SQLITE_INT_TO_PTR'
> sqlite3.c(11016) : warning C4005: 'SQLITE_PTR_TO_INT' : macro redefinition
>sqlite3.c(11013) : see previous definition of 'SQLITE_PTR_TO_INT'
> sqlite3.c(11018) : warning C4005: 'SQLITE_INT_TO_PTR' : macro redefinition
>sqlite3.c(11015) : see previous definition of 'SQLITE_INT_TO_PTR'
> sqlite3.c(11019) : warning C4005: 'SQLITE_PTR_TO_INT' : macro redefinition
>sqlite3.c(11016) : see previous definition of 'SQLITE_PTR_TO_INT'
> sqlite3.c(11021) : warning C4005: 'SQLITE_INT_TO_PTR' : macro redefinition
> 
> I need to compile this for Windows Mobile ARM device. Is there another 
way to do it by mean of other compiler that works in Windows? I need to use 
Windows since the output file should be a DLL.
> 

Given that Windows for ARM was released around 2013 (if I remember 
correctly), I doubt that MSVC2008 will do. Sadly, GCC doesn’t support ARM for 
Windows as a target, and clang is on the way, but wasn’t ready yet last time I 
checked.
That being said, Windows for ARM/Windows RT doesn’t support “Desktop 
applications”. Is there any reason why need to have a DLL, and not the prebuilt 
package? I’d understand the need for native code, but then I’m not sure you can 
do that with anything earlier than Visual Studio 2013

> By opening sqlite3.c I found directives such as this:
> 
> if defined(_MSC_VER) && _MSC_VER>=1400
> 
> 
> That suggests me that the code is prepared for MSVC also, but it is not 
actually.
> 
> 
> Does somebody have experience compiling this in MSVC?
> 
   

Re: [sqlite] SQLite does not support ARM platform?

2017-03-20 Thread Deon Brewis
Ahh, ok, you're not actually trying to target Windows RT - you're trying to 
target Windows CE. That makes (a LOT) more sense.

The technical problem you have is that you're running into a Windows RT error 
there. You'll get the same behavior simply if you do this:

C:\test>copy con test.c
#include 
^Z
1 file(s) copied.

C:\test>cl test.c
test.c
C:\Program Files (x86)\Windows 
Kits\10\include\10.0.10240.0\ucrt\corecrt.h(205): fatal error C1189: #error:  
Compiling Desktop applications for the ARM platform is not supported.


The way to get around that for WinRT is to specify:
/DWINAPI_FAMILY=WINAPI_FAMILY_APP

So e.g.
cl test.c /DWINAPI_FAMILY=WINAPI_FAMILY_APP



However, this is probably not what you want... you want the SQLITE build for 
Windows CE - it's up on the site.

- Deon

-Original Message-
From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On 
Behalf Of Jaime Stuardo
Sent: Monday, March 20, 2017 3:39 PM
To: 'SQLite mailing list' 
Subject: Re: [sqlite] SQLite does not support ARM platform?

When I build my own program using Visual Studio 2008  IDE  to be run in the 
device, it compiles perfectly and also it runs perfectly in the machine. So 
there is nothing wrong with that.

I tried to compile sqlite3.c using the same command line parameters I saw in 
project properties in VS2008 but without success. Last try was this command 
line:

"cl sqlite3.c /O2 /Os /D "NDEBUG" /D "WIN32_PLATFORM_PSPC" /D "WINCE" /D "ARM" 
/D "_ARM_" /D "POCKETPC2003_UI_MODEL" /D "_UNICODE" /D "UNICODE" /FD /EHsc /MT 
/fp:fast /GR- /link /dll /machine:THUMB"

But the error is: "sqlite3.obj : fatal error LNK1112: module machine type 'X86' 
conflicts with target machine type 'THUMB'"

I use THUMB as the machine, because my own C++ project uses THUMB as the 
machine type and that works.

That is why I suspect about SQLite3 to be really multiplatform. Why can my own 
C++ program, that is not small, be successfully compiled and then run in the 
machine? Why cannot SQLite source code? I only need to generate the LIB file to 
add it to my project and the DLL file to copy to the machine. What command line 
do you use for your target machine?

Regards
Jaime

-Original Message-
From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On 
Behalf Of Deon Brewis
Sent: lunes, 20 de marzo de 2017 19:25
To: SQLite mailing list 
Subject: Re: [sqlite] SQLite does not support ARM platform?

"That suggests me that the code is prepared for MSVC also, but it is not 
actually."

The SQLITE code works just fine on an MSVC build. Have been using it for many 
years.

What platform are you targeting? The MSVC ARM compiler is only meant for 
Windows RT devices - is that really what you're trying to build for?

- Deon

-Original Message-
From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On 
Behalf Of Jaime Stuardo
Sent: Monday, March 20, 2017 3:17 PM
To: 'SQLite mailing list' 
Subject: Re: [sqlite] SQLite does not support ARM platform?

Thanks all who answered.

Yes... it seems a MSVC limitation, however, it is very strange. I am using 
Visual Studio 2008 which does support ARM compilation.  I did that, adding some 
compiler switches for target WIN32_CE but I got million of warnings, of this 
type:

sqlite3.c(166) : warning C4005: 'OS_VXWORKS' : macro redefinition
sqlite3.c(158) : see previous definition of 'OS_VXWORKS'
sqlite3.c(216) : warning C4005: 'GCC_VERSION' : macro redefinition
sqlite3.c(214) : see previous definition of 'GCC_VERSION'
sqlite3.c(222) : warning C4005: 'CLANG_VERSION' : macro redefinition
sqlite3.c(220) : see previous definition of 'CLANG_VERSION'
sqlite3.c(227) : warning C4005: 'MSVC_VERSION' : macro redefinition
sqlite3.c(225) : see previous definition of 'MSVC_VERSION'
sqlite3.c(10924) : warning C4005: 'SQLITE_DEFAULT_PAGE_SIZE' : macro 
redefinition
sqlite3.c(10920) : see previous definition of 'SQLITE_DEFAULT_PAGE_SIZE'
sqlite3.c(10939) : warning C4005: 'SQLITE_MAX_DEFAULT_PAGE_SIZE' : macro 
redefinition
sqlite3.c(10935) : see previous definition of 
'SQLITE_MAX_DEFAULT_PAGE_SIZE'
sqlite3.c(11015) : warning C4005: 'SQLITE_INT_TO_PTR' : macro redefinition
sqlite3.c(11012) : see previous definition of 'SQLITE_INT_TO_PTR'
sqlite3.c(11016) : warning C4005: 'SQLITE_PTR_TO_INT' : macro redefinition
sqlite3.c(11013) : see previous definition of 'SQLITE_PTR_TO_INT'
sqlite3.c(11018) : warning C4005: 'SQLITE_INT_TO_PTR' : macro redefinition
sqlite3.c(11015) : see previous definition of 'SQLITE_INT_TO_PTR'
sqlite3.c(11019) : warning C4005: 'SQLITE_PTR_TO_INT' : macro redefinition
sqlite3.c(11016) : see previous definition of 'SQLITE_PTR_TO_INT'
sqlite3.c(11021) : warning C4005: 'SQLITE_INT_TO_PTR' : macro redefinition

I need to compile this for 

Re: [sqlite] SQLite does not support ARM platform?

2017-03-20 Thread Jim Borden
Oh, you are talking about WinCE?  I don’t think you should be thinking in terms 
of “ARM vs non-ARM” but rather “X platform vs Y platform.”  As others have 
noted, sqlite obviously runs on ARM and the issue is not with sqlite but with 
the way you are trying to compile it or the platform you are trying to compile 
it for.  It totally slipped my mind that WinCE would probably be ARM as well 
(and honestly I didn’t even realize it was still around!).  

I think WinCE has its own build for sqlite:  
http://sqlite-wince.sourceforge.net/ probably due to rather extreme limitations.

On 2017/03/21 7:41, "sqlite-users on behalf of Jaime Stuardo" 
 wrote:

I use to develop mobile applications for years using VS 2008, and in fact, 
I have just developed a MFC C++ application that runs in the ARM machine 
without problem. I need to use SQLite3 for my application. That is why I need 
to compile it.




> On 20 Mar 2017, at 23:17, Jaime Stuardo  wrote:
> 
> Thanks all who answered.
> 
> Yes... it seems a MSVC limitation, however, it is very strange. I am 
using Visual Studio 2008 which does support ARM compilation.  I did that, 
adding some compiler switches for target WIN32_CE but I got million of 
warnings, of this type:
> 
> sqlite3.c(166) : warning C4005: 'OS_VXWORKS' : macro redefinition
>sqlite3.c(158) : see previous definition of 'OS_VXWORKS'
> sqlite3.c(216) : warning C4005: 'GCC_VERSION' : macro redefinition
>sqlite3.c(214) : see previous definition of 'GCC_VERSION'
> sqlite3.c(222) : warning C4005: 'CLANG_VERSION' : macro redefinition
>sqlite3.c(220) : see previous definition of 'CLANG_VERSION'
> sqlite3.c(227) : warning C4005: 'MSVC_VERSION' : macro redefinition
>sqlite3.c(225) : see previous definition of 'MSVC_VERSION'
> sqlite3.c(10924) : warning C4005: 'SQLITE_DEFAULT_PAGE_SIZE' : macro 
redefinition
>sqlite3.c(10920) : see previous definition of 
'SQLITE_DEFAULT_PAGE_SIZE'
> sqlite3.c(10939) : warning C4005: 'SQLITE_MAX_DEFAULT_PAGE_SIZE' : macro 
redefinition
>sqlite3.c(10935) : see previous definition of 
'SQLITE_MAX_DEFAULT_PAGE_SIZE'
> sqlite3.c(11015) : warning C4005: 'SQLITE_INT_TO_PTR' : macro redefinition
>sqlite3.c(11012) : see previous definition of 'SQLITE_INT_TO_PTR'
> sqlite3.c(11016) : warning C4005: 'SQLITE_PTR_TO_INT' : macro redefinition
>sqlite3.c(11013) : see previous definition of 'SQLITE_PTR_TO_INT'
> sqlite3.c(11018) : warning C4005: 'SQLITE_INT_TO_PTR' : macro redefinition
>sqlite3.c(11015) : see previous definition of 'SQLITE_INT_TO_PTR'
> sqlite3.c(11019) : warning C4005: 'SQLITE_PTR_TO_INT' : macro redefinition
>sqlite3.c(11016) : see previous definition of 'SQLITE_PTR_TO_INT'
> sqlite3.c(11021) : warning C4005: 'SQLITE_INT_TO_PTR' : macro redefinition
> 
> I need to compile this for Windows Mobile ARM device. Is there another 
way to do it by mean of other compiler that works in Windows? I need to use 
Windows since the output file should be a DLL.
> 

Given that Windows for ARM was released around 2013 (if I remember 
correctly), I doubt that MSVC2008 will do. Sadly, GCC doesn’t support ARM for 
Windows as a target, and clang is on the way, but wasn’t ready yet last time I 
checked.
That being said, Windows for ARM/Windows RT doesn’t support “Desktop 
applications”. Is there any reason why need to have a DLL, and not the prebuilt 
package? I’d understand the need for native code, but then I’m not sure you can 
do that with anything earlier than Visual Studio 2013

> By opening sqlite3.c I found directives such as this:
> 
> if defined(_MSC_VER) && _MSC_VER>=1400
> 
> 
> That suggests me that the code is prepared for MSVC also, but it is not 
actually.
> 
> 
> Does somebody have experience compiling this in MSVC?
> 
> Regards
> Jaime


___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] SQLite does not support ARM platform?

2017-03-20 Thread Jaime Stuardo
I use to develop mobile applications for years using VS 2008, and in fact, I 
have just developed a MFC C++ application that runs in the ARM machine without 
problem. I need to use SQLite3 for my application. That is why I need to 
compile it.




> On 20 Mar 2017, at 23:17, Jaime Stuardo  wrote:
> 
> Thanks all who answered.
> 
> Yes... it seems a MSVC limitation, however, it is very strange. I am using 
> Visual Studio 2008 which does support ARM compilation.  I did that, adding 
> some compiler switches for target WIN32_CE but I got million of warnings, of 
> this type:
> 
> sqlite3.c(166) : warning C4005: 'OS_VXWORKS' : macro redefinition
>sqlite3.c(158) : see previous definition of 'OS_VXWORKS'
> sqlite3.c(216) : warning C4005: 'GCC_VERSION' : macro redefinition
>sqlite3.c(214) : see previous definition of 'GCC_VERSION'
> sqlite3.c(222) : warning C4005: 'CLANG_VERSION' : macro redefinition
>sqlite3.c(220) : see previous definition of 'CLANG_VERSION'
> sqlite3.c(227) : warning C4005: 'MSVC_VERSION' : macro redefinition
>sqlite3.c(225) : see previous definition of 'MSVC_VERSION'
> sqlite3.c(10924) : warning C4005: 'SQLITE_DEFAULT_PAGE_SIZE' : macro 
> redefinition
>sqlite3.c(10920) : see previous definition of 
> 'SQLITE_DEFAULT_PAGE_SIZE'
> sqlite3.c(10939) : warning C4005: 'SQLITE_MAX_DEFAULT_PAGE_SIZE' : macro 
> redefinition
>sqlite3.c(10935) : see previous definition of 
> 'SQLITE_MAX_DEFAULT_PAGE_SIZE'
> sqlite3.c(11015) : warning C4005: 'SQLITE_INT_TO_PTR' : macro redefinition
>sqlite3.c(11012) : see previous definition of 'SQLITE_INT_TO_PTR'
> sqlite3.c(11016) : warning C4005: 'SQLITE_PTR_TO_INT' : macro redefinition
>sqlite3.c(11013) : see previous definition of 'SQLITE_PTR_TO_INT'
> sqlite3.c(11018) : warning C4005: 'SQLITE_INT_TO_PTR' : macro redefinition
>sqlite3.c(11015) : see previous definition of 'SQLITE_INT_TO_PTR'
> sqlite3.c(11019) : warning C4005: 'SQLITE_PTR_TO_INT' : macro redefinition
>sqlite3.c(11016) : see previous definition of 'SQLITE_PTR_TO_INT'
> sqlite3.c(11021) : warning C4005: 'SQLITE_INT_TO_PTR' : macro redefinition
> 
> I need to compile this for Windows Mobile ARM device. Is there another way to 
> do it by mean of other compiler that works in Windows? I need to use Windows 
> since the output file should be a DLL.
> 

Given that Windows for ARM was released around 2013 (if I remember correctly), 
I doubt that MSVC2008 will do. Sadly, GCC doesn’t support ARM for Windows as a 
target, and clang is on the way, but wasn’t ready yet last time I checked.
That being said, Windows for ARM/Windows RT doesn’t support “Desktop 
applications”. Is there any reason why need to have a DLL, and not the prebuilt 
package? I’d understand the need for native code, but then I’m not sure you can 
do that with anything earlier than Visual Studio 2013

> By opening sqlite3.c I found directives such as this:
> 
> if defined(_MSC_VER) && _MSC_VER>=1400
> 
> 
> That suggests me that the code is prepared for MSVC also, but it is not 
> actually.
> 
> 
> Does somebody have experience compiling this in MSVC?
> 
> Regards
> Jaime


___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] SQLite does not support ARM platform?

2017-03-20 Thread Jaime Stuardo
When I build my own program using Visual Studio 2008  IDE  to be run in the 
device, it compiles perfectly and also it runs perfectly in the machine. So 
there is nothing wrong with that.

I tried to compile sqlite3.c using the same command line parameters I saw in 
project properties in VS2008 but without success. Last try was this command 
line:

"cl sqlite3.c /O2 /Os /D "NDEBUG" /D "WIN32_PLATFORM_PSPC" /D "WINCE" /D "ARM" 
/D "_ARM_" /D "POCKETPC2003_UI_MODEL" /D "_UNICODE" /D "UNICODE" /FD /EHsc /MT 
/fp:fast /GR- /link /dll /machine:THUMB"

But the error is: "sqlite3.obj : fatal error LNK1112: module machine type 'X86' 
conflicts with target machine type 'THUMB'"

I use THUMB as the machine, because my own C++ project uses THUMB as the 
machine type and that works.

That is why I suspect about SQLite3 to be really multiplatform. Why can my own 
C++ program, that is not small, be successfully compiled and then run in the 
machine? Why cannot SQLite source code? I only need to generate the LIB file to 
add it to my project and the DLL file to copy to the machine. What command line 
do you use for your target machine?

Regards
Jaime

-Original Message-
From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On 
Behalf Of Deon Brewis
Sent: lunes, 20 de marzo de 2017 19:25
To: SQLite mailing list 
Subject: Re: [sqlite] SQLite does not support ARM platform?

"That suggests me that the code is prepared for MSVC also, but it is not 
actually."

The SQLITE code works just fine on an MSVC build. Have been using it for many 
years.

What platform are you targeting? The MSVC ARM compiler is only meant for 
Windows RT devices - is that really what you're trying to build for?

- Deon

-Original Message-
From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On 
Behalf Of Jaime Stuardo
Sent: Monday, March 20, 2017 3:17 PM
To: 'SQLite mailing list' 
Subject: Re: [sqlite] SQLite does not support ARM platform?

Thanks all who answered.

Yes... it seems a MSVC limitation, however, it is very strange. I am using 
Visual Studio 2008 which does support ARM compilation.  I did that, adding some 
compiler switches for target WIN32_CE but I got million of warnings, of this 
type:

sqlite3.c(166) : warning C4005: 'OS_VXWORKS' : macro redefinition
sqlite3.c(158) : see previous definition of 'OS_VXWORKS'
sqlite3.c(216) : warning C4005: 'GCC_VERSION' : macro redefinition
sqlite3.c(214) : see previous definition of 'GCC_VERSION'
sqlite3.c(222) : warning C4005: 'CLANG_VERSION' : macro redefinition
sqlite3.c(220) : see previous definition of 'CLANG_VERSION'
sqlite3.c(227) : warning C4005: 'MSVC_VERSION' : macro redefinition
sqlite3.c(225) : see previous definition of 'MSVC_VERSION'
sqlite3.c(10924) : warning C4005: 'SQLITE_DEFAULT_PAGE_SIZE' : macro 
redefinition
sqlite3.c(10920) : see previous definition of 'SQLITE_DEFAULT_PAGE_SIZE'
sqlite3.c(10939) : warning C4005: 'SQLITE_MAX_DEFAULT_PAGE_SIZE' : macro 
redefinition
sqlite3.c(10935) : see previous definition of 
'SQLITE_MAX_DEFAULT_PAGE_SIZE'
sqlite3.c(11015) : warning C4005: 'SQLITE_INT_TO_PTR' : macro redefinition
sqlite3.c(11012) : see previous definition of 'SQLITE_INT_TO_PTR'
sqlite3.c(11016) : warning C4005: 'SQLITE_PTR_TO_INT' : macro redefinition
sqlite3.c(11013) : see previous definition of 'SQLITE_PTR_TO_INT'
sqlite3.c(11018) : warning C4005: 'SQLITE_INT_TO_PTR' : macro redefinition
sqlite3.c(11015) : see previous definition of 'SQLITE_INT_TO_PTR'
sqlite3.c(11019) : warning C4005: 'SQLITE_PTR_TO_INT' : macro redefinition
sqlite3.c(11016) : see previous definition of 'SQLITE_PTR_TO_INT'
sqlite3.c(11021) : warning C4005: 'SQLITE_INT_TO_PTR' : macro redefinition

I need to compile this for Windows Mobile ARM device. Is there another way to 
do it by mean of other compiler that works in Windows? I need to use Windows 
since the output file should be a DLL.

By opening sqlite3.c I found directives such as this:

if defined(_MSC_VER) && _MSC_VER>=1400


That suggests me that the code is prepared for MSVC also, but it is not 
actually.


Does somebody have experience compiling this in MSVC?

Regards
Jaime

-Original Message-
From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On 
Behalf Of Joseph Stockman
Sent: lunes, 20 de marzo de 2017 18:34
To: SQLite mailing list 
Subject: Re: [sqlite] SQLite does not support ARM platform?

This is a Visual Studio/Microsoft issue. We have been building SQLite on ARM 7 
and 9 for almost ten years across a wide variety of (non-Microsoft) operating 
systems.

V.


From: sqlite-users [sqlite-users-boun...@mailinglists.sqlite.org] on behalf of 
Jaime Stuardo [jstua...@desytec.com]
Sent: Monday, March 20, 2017 4:24 PM
To: 'SQLite 

Re: [sqlite] SQLite does not support ARM platform?

2017-03-20 Thread Hugo Beauzée-Luyssen


> On 20 Mar 2017, at 23:17, Jaime Stuardo  wrote:
> 
> Thanks all who answered.
> 
> Yes... it seems a MSVC limitation, however, it is very strange. I am using 
> Visual Studio 2008 which does support ARM compilation.  I did that, adding 
> some compiler switches for target WIN32_CE but I got million of warnings, of 
> this type:
> 
> sqlite3.c(166) : warning C4005: 'OS_VXWORKS' : macro redefinition
>sqlite3.c(158) : see previous definition of 'OS_VXWORKS'
> sqlite3.c(216) : warning C4005: 'GCC_VERSION' : macro redefinition
>sqlite3.c(214) : see previous definition of 'GCC_VERSION'
> sqlite3.c(222) : warning C4005: 'CLANG_VERSION' : macro redefinition
>sqlite3.c(220) : see previous definition of 'CLANG_VERSION'
> sqlite3.c(227) : warning C4005: 'MSVC_VERSION' : macro redefinition
>sqlite3.c(225) : see previous definition of 'MSVC_VERSION'
> sqlite3.c(10924) : warning C4005: 'SQLITE_DEFAULT_PAGE_SIZE' : macro 
> redefinition
>sqlite3.c(10920) : see previous definition of 
> 'SQLITE_DEFAULT_PAGE_SIZE'
> sqlite3.c(10939) : warning C4005: 'SQLITE_MAX_DEFAULT_PAGE_SIZE' : macro 
> redefinition
>sqlite3.c(10935) : see previous definition of 
> 'SQLITE_MAX_DEFAULT_PAGE_SIZE'
> sqlite3.c(11015) : warning C4005: 'SQLITE_INT_TO_PTR' : macro redefinition
>sqlite3.c(11012) : see previous definition of 'SQLITE_INT_TO_PTR'
> sqlite3.c(11016) : warning C4005: 'SQLITE_PTR_TO_INT' : macro redefinition
>sqlite3.c(11013) : see previous definition of 'SQLITE_PTR_TO_INT'
> sqlite3.c(11018) : warning C4005: 'SQLITE_INT_TO_PTR' : macro redefinition
>sqlite3.c(11015) : see previous definition of 'SQLITE_INT_TO_PTR'
> sqlite3.c(11019) : warning C4005: 'SQLITE_PTR_TO_INT' : macro redefinition
>sqlite3.c(11016) : see previous definition of 'SQLITE_PTR_TO_INT'
> sqlite3.c(11021) : warning C4005: 'SQLITE_INT_TO_PTR' : macro redefinition
> 
> I need to compile this for Windows Mobile ARM device. Is there another way to 
> do it by mean of other compiler that works in Windows? I need to use Windows 
> since the output file should be a DLL.
> 

Given that Windows for ARM was released around 2013 (if I remember correctly), 
I doubt that MSVC2008 will do. Sadly, GCC doesn’t support ARM for Windows as a 
target, and clang is on the way, but wasn’t ready yet last time I checked.
That being said, Windows for ARM/Windows RT doesn’t support “Desktop 
applications”. Is there any reason why need to have a DLL, and not the prebuilt 
package? I’d understand the need for native code, but then I’m not sure you can 
do that with anything earlier than Visual Studio 2013

> By opening sqlite3.c I found directives such as this:
> 
> if defined(_MSC_VER) && _MSC_VER>=1400
> 
> 
> That suggests me that the code is prepared for MSVC also, but it is not 
> actually.
> 
> 
> Does somebody have experience compiling this in MSVC?
> 
> Regards
> Jaime


___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] SQLite does not support ARM platform?

2017-03-20 Thread Deon Brewis
"That suggests me that the code is prepared for MSVC also, but it is not 
actually."

The SQLITE code works just fine on an MSVC build. Have been using it for many 
years.

What platform are you targeting? The MSVC ARM compiler is only meant for 
Windows RT devices - is that really what you're trying to build for?

- Deon

-Original Message-
From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On 
Behalf Of Jaime Stuardo
Sent: Monday, March 20, 2017 3:17 PM
To: 'SQLite mailing list' 
Subject: Re: [sqlite] SQLite does not support ARM platform?

Thanks all who answered.

Yes... it seems a MSVC limitation, however, it is very strange. I am using 
Visual Studio 2008 which does support ARM compilation.  I did that, adding some 
compiler switches for target WIN32_CE but I got million of warnings, of this 
type:

sqlite3.c(166) : warning C4005: 'OS_VXWORKS' : macro redefinition
sqlite3.c(158) : see previous definition of 'OS_VXWORKS'
sqlite3.c(216) : warning C4005: 'GCC_VERSION' : macro redefinition
sqlite3.c(214) : see previous definition of 'GCC_VERSION'
sqlite3.c(222) : warning C4005: 'CLANG_VERSION' : macro redefinition
sqlite3.c(220) : see previous definition of 'CLANG_VERSION'
sqlite3.c(227) : warning C4005: 'MSVC_VERSION' : macro redefinition
sqlite3.c(225) : see previous definition of 'MSVC_VERSION'
sqlite3.c(10924) : warning C4005: 'SQLITE_DEFAULT_PAGE_SIZE' : macro 
redefinition
sqlite3.c(10920) : see previous definition of 'SQLITE_DEFAULT_PAGE_SIZE'
sqlite3.c(10939) : warning C4005: 'SQLITE_MAX_DEFAULT_PAGE_SIZE' : macro 
redefinition
sqlite3.c(10935) : see previous definition of 
'SQLITE_MAX_DEFAULT_PAGE_SIZE'
sqlite3.c(11015) : warning C4005: 'SQLITE_INT_TO_PTR' : macro redefinition
sqlite3.c(11012) : see previous definition of 'SQLITE_INT_TO_PTR'
sqlite3.c(11016) : warning C4005: 'SQLITE_PTR_TO_INT' : macro redefinition
sqlite3.c(11013) : see previous definition of 'SQLITE_PTR_TO_INT'
sqlite3.c(11018) : warning C4005: 'SQLITE_INT_TO_PTR' : macro redefinition
sqlite3.c(11015) : see previous definition of 'SQLITE_INT_TO_PTR'
sqlite3.c(11019) : warning C4005: 'SQLITE_PTR_TO_INT' : macro redefinition
sqlite3.c(11016) : see previous definition of 'SQLITE_PTR_TO_INT'
sqlite3.c(11021) : warning C4005: 'SQLITE_INT_TO_PTR' : macro redefinition

I need to compile this for Windows Mobile ARM device. Is there another way to 
do it by mean of other compiler that works in Windows? I need to use Windows 
since the output file should be a DLL.

By opening sqlite3.c I found directives such as this:

if defined(_MSC_VER) && _MSC_VER>=1400


That suggests me that the code is prepared for MSVC also, but it is not 
actually.


Does somebody have experience compiling this in MSVC?

Regards
Jaime

-Original Message-
From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On 
Behalf Of Joseph Stockman
Sent: lunes, 20 de marzo de 2017 18:34
To: SQLite mailing list 
Subject: Re: [sqlite] SQLite does not support ARM platform?

This is a Visual Studio/Microsoft issue. We have been building SQLite on ARM 7 
and 9 for almost ten years across a wide variety of (non-Microsoft) operating 
systems.

V.


From: sqlite-users [sqlite-users-boun...@mailinglists.sqlite.org] on behalf of 
Jaime Stuardo [jstua...@desytec.com]
Sent: Monday, March 20, 2017 4:24 PM
To: 'SQLite mailing list'
Subject: [sqlite] SQLite does not support ARM platform?

Hello,

I have finally given up. After almost all day trying to compile SQLite 
amalgamated source code files for ARM platform I got the conclusion that SQLite 
is not for ARM platform, even when documentation says the contrary. I have VS 
2008 and I tried to compile some C++ wrappers out there that contains 
amalgamated files but with no success

I tried several command line parameters, but nothing.

Last try was, by using only amalgamated files (shell.c, sqlite3.c, sqlite3.h, 
sqlite3ext.h). There is no science with this. I open a VS2008 command prompt 
and VS2012 ARM Command prompt and compile with:

"cl sqlite3.c -link -dll -out:sqlite3.dll -machine:ARM"

In both cases, I got this error:

"crtdefs.h(338) : fatal error C1189: #error :  Compiling Desktop applications 
for the ARM platform is not supported."

That took  me to the conclusion about SQLite is only for Desktop applications, 
which is very bad. Is there another alternative or trick to make it compile for 
ARM platform?

Thanks
Jaime

___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

 This message is for the addressee's use only. It may contain confidential 
information. If you receive this message in error, please delete it and 

Re: [sqlite] SQLite does not support ARM platform?

2017-03-20 Thread Jaime Stuardo
Thanks all who answered.

Yes... it seems a MSVC limitation, however, it is very strange. I am using 
Visual Studio 2008 which does support ARM compilation.  I did that, adding some 
compiler switches for target WIN32_CE but I got million of warnings, of this 
type:

sqlite3.c(166) : warning C4005: 'OS_VXWORKS' : macro redefinition
sqlite3.c(158) : see previous definition of 'OS_VXWORKS'
sqlite3.c(216) : warning C4005: 'GCC_VERSION' : macro redefinition
sqlite3.c(214) : see previous definition of 'GCC_VERSION'
sqlite3.c(222) : warning C4005: 'CLANG_VERSION' : macro redefinition
sqlite3.c(220) : see previous definition of 'CLANG_VERSION'
sqlite3.c(227) : warning C4005: 'MSVC_VERSION' : macro redefinition
sqlite3.c(225) : see previous definition of 'MSVC_VERSION'
sqlite3.c(10924) : warning C4005: 'SQLITE_DEFAULT_PAGE_SIZE' : macro 
redefinition
sqlite3.c(10920) : see previous definition of 'SQLITE_DEFAULT_PAGE_SIZE'
sqlite3.c(10939) : warning C4005: 'SQLITE_MAX_DEFAULT_PAGE_SIZE' : macro 
redefinition
sqlite3.c(10935) : see previous definition of 
'SQLITE_MAX_DEFAULT_PAGE_SIZE'
sqlite3.c(11015) : warning C4005: 'SQLITE_INT_TO_PTR' : macro redefinition
sqlite3.c(11012) : see previous definition of 'SQLITE_INT_TO_PTR'
sqlite3.c(11016) : warning C4005: 'SQLITE_PTR_TO_INT' : macro redefinition
sqlite3.c(11013) : see previous definition of 'SQLITE_PTR_TO_INT'
sqlite3.c(11018) : warning C4005: 'SQLITE_INT_TO_PTR' : macro redefinition
sqlite3.c(11015) : see previous definition of 'SQLITE_INT_TO_PTR'
sqlite3.c(11019) : warning C4005: 'SQLITE_PTR_TO_INT' : macro redefinition
sqlite3.c(11016) : see previous definition of 'SQLITE_PTR_TO_INT'
sqlite3.c(11021) : warning C4005: 'SQLITE_INT_TO_PTR' : macro redefinition

I need to compile this for Windows Mobile ARM device. Is there another way to 
do it by mean of other compiler that works in Windows? I need to use Windows 
since the output file should be a DLL.

By opening sqlite3.c I found directives such as this:

if defined(_MSC_VER) && _MSC_VER>=1400


That suggests me that the code is prepared for MSVC also, but it is not 
actually.


Does somebody have experience compiling this in MSVC?

Regards
Jaime

-Original Message-
From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On 
Behalf Of Joseph Stockman
Sent: lunes, 20 de marzo de 2017 18:34
To: SQLite mailing list 
Subject: Re: [sqlite] SQLite does not support ARM platform?

This is a Visual Studio/Microsoft issue. We have been building SQLite on ARM 7 
and 9 for almost ten years across a wide variety of (non-Microsoft) operating 
systems.

V.


From: sqlite-users [sqlite-users-boun...@mailinglists.sqlite.org] on behalf of 
Jaime Stuardo [jstua...@desytec.com]
Sent: Monday, March 20, 2017 4:24 PM
To: 'SQLite mailing list'
Subject: [sqlite] SQLite does not support ARM platform?

Hello,

I have finally given up. After almost all day trying to compile SQLite 
amalgamated source code files for ARM platform I got the conclusion that SQLite 
is not for ARM platform, even when documentation says the contrary. I have VS 
2008 and I tried to compile some C++ wrappers out there that contains 
amalgamated files but with no success

I tried several command line parameters, but nothing.

Last try was, by using only amalgamated files (shell.c, sqlite3.c, sqlite3.h, 
sqlite3ext.h). There is no science with this. I open a VS2008 command prompt 
and VS2012 ARM Command prompt and compile with:

"cl sqlite3.c -link -dll -out:sqlite3.dll -machine:ARM"

In both cases, I got this error:

"crtdefs.h(338) : fatal error C1189: #error :  Compiling Desktop applications 
for the ARM platform is not supported."

That took  me to the conclusion about SQLite is only for Desktop applications, 
which is very bad. Is there another alternative or trick to make it compile for 
ARM platform?

Thanks
Jaime

___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

 This message is for the addressee's use only. It may contain confidential 
information. If you receive this message in error, please delete it and notify 
the sender. Tripp Lite disclaims all warranties and liabilities, and assumes no 
responsibility for viruses which may infect an email sent to you from Tripp 
Lite and which damage your electronic systems or information. It is your 
responsibility to maintain virus detection systems to prevent damage to your 
electronic systems and information.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

___
sqlite-users mailing list

Re: [sqlite] RIGHT JOIN! still not supported?

2017-03-20 Thread Chris Locke
Sqlite is public domain, so feel free to add the necessary code, and once
approved, it'll get added to the main code.


Thanks,
Chris

On 20 Mar 2017 8:09 p.m., "PICCORO McKAY Lenz" 
wrote:

> i got this
>
> Query Error: RIGHT and FULL OUTER JOINs are not currently supported
> Unable to execute statement
>
> still today in 21 ts century?
>
> Lenz McKAY Gerardo (PICCORO)
> http://qgqlochekone.blogspot.com
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] SQLite does not support ARM platform?

2017-03-20 Thread Joseph Stockman
This is a Visual Studio/Microsoft issue. We have been building SQLite on ARM 7 
and 9 for almost ten years across a wide variety of (non-Microsoft) operating 
systems.

V.


From: sqlite-users [sqlite-users-boun...@mailinglists.sqlite.org] on behalf of 
Jaime Stuardo [jstua...@desytec.com]
Sent: Monday, March 20, 2017 4:24 PM
To: 'SQLite mailing list'
Subject: [sqlite] SQLite does not support ARM platform?

Hello,

I have finally given up. After almost all day trying to compile SQLite 
amalgamated source code files for ARM platform I got the conclusion that SQLite 
is not for ARM platform, even when documentation says the contrary. I have VS 
2008 and I tried to compile some C++ wrappers out there that contains 
amalgamated files but with no success

I tried several command line parameters, but nothing.

Last try was, by using only amalgamated files (shell.c, sqlite3.c, sqlite3.h, 
sqlite3ext.h). There is no science with this. I open a VS2008 command prompt 
and VS2012 ARM Command prompt and compile with:

"cl sqlite3.c -link -dll -out:sqlite3.dll -machine:ARM"

In both cases, I got this error:

"crtdefs.h(338) : fatal error C1189: #error :  Compiling Desktop applications 
for the ARM platform is not supported."

That took  me to the conclusion about SQLite is only for Desktop applications, 
which is very bad. Is there another alternative or trick to make it compile for 
ARM platform?

Thanks
Jaime

___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

 This message is for the addressee's use only. It may contain confidential 
information. If you receive this message in error, please delete it and notify 
the sender. Tripp Lite disclaims all warranties and liabilities, and assumes no 
responsibility for viruses which may infect an email sent to you from Tripp 
Lite and which damage your electronic systems or information. It is your 
responsibility to maintain virus detection systems to prevent damage to your 
electronic systems and information.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] SQLite does not support ARM platform?

2017-03-20 Thread Hugo Beauzée-Luyssen
Hi,

> On 20 Mar 2017, at 22:24, Jaime Stuardo  wrote:
> 
> Hello,
> 
> I have finally given up. After almost all day trying to compile SQLite 
> amalgamated source code files for ARM platform I got the conclusion that 
> SQLite is not for ARM platform, even when documentation says the contrary. I 
> have VS 2008 and I tried to compile some C++ wrappers out there that contains 
> amalgamated files but with no success
> 

sqlite totally supports ARM, we use it & build it ourselves for VLC on android, 
and even the android SDK provides a way to use sqlite IIRC.

> I tried several command line parameters, but nothing.
> 
> Last try was, by using only amalgamated files (shell.c, sqlite3.c, sqlite3.h, 
> sqlite3ext.h). There is no science with this. I open a VS2008 command prompt 
> and VS2012 ARM Command prompt and compile with:
> 
> "cl sqlite3.c -link -dll -out:sqlite3.dll -machine:ARM"
> 
> In both cases, I got this error:
> 
> "crtdefs.h(338) : fatal error C1189: #error :  Compiling Desktop applications 
> for the ARM platform is not supported.”
> 

Seems that you’re trying to compile sqlite for an ARM application without 
settings the proper flags to point MSVC at a store application.
Either you’re building for a store app, and you should be able to use some 
prebuild version (https://www.sqlite.org/2017/sqlite-uwp-317.vsix) or 
you’re building for a desktop app, and there is no desktop apps on 
WindowsRT/Windows for ARM.

> That took  me to the conclusion about SQLite is only for Desktop 
> applications, which is very bad. Is there another alternative or trick to 
> make it compile for ARM platform?
> 

Don’t know about windows, but using the algamated version and autotools, it 
should be as easy as ./configure —host= && make

> Thanks
> Jaime
> 
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] SQLite does not support ARM platform?

2017-03-20 Thread Eric Sink
You are encountering a limitation of the compiler you are using, not a
limitation of SQLite (which compiles for ARM just fine).

The error message is telling you that Microsoft does not support desktop
applications compiled for ARM.

What environment are you trying to compile for?

--
E


On Mon, Mar 20, 2017 at 4:24 PM, Jaime Stuardo  wrote:

> Hello,
>
> I have finally given up. After almost all day trying to compile SQLite
> amalgamated source code files for ARM platform I got the conclusion that
> SQLite is not for ARM platform, even when documentation says the contrary.
> I have VS 2008 and I tried to compile some C++ wrappers out there that
> contains amalgamated files but with no success
>
> I tried several command line parameters, but nothing.
>
> Last try was, by using only amalgamated files (shell.c, sqlite3.c,
> sqlite3.h, sqlite3ext.h). There is no science with this. I open a VS2008
> command prompt and VS2012 ARM Command prompt and compile with:
>
> "cl sqlite3.c -link -dll -out:sqlite3.dll -machine:ARM"
>
> In both cases, I got this error:
>
> "crtdefs.h(338) : fatal error C1189: #error :  Compiling Desktop
> applications for the ARM platform is not supported."
>
> That took  me to the conclusion about SQLite is only for Desktop
> applications, which is very bad. Is there another alternative or trick to
> make it compile for ARM platform?
>
> Thanks
> Jaime
>
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] SQLite does not support ARM platform?

2017-03-20 Thread Jim Borden
That error has nothing to do with SQLite, really.  SQLite is deployed on ARM 
platforms and ships as a system library on iOS.  It sounds like you are running 
into this -> 
https://stackoverflow.com/questions/11151474/can-arm-desktop-programs-be-built-using-visual-studio-2012

Keep in mind that Visual Studio ARM development is fairly new.  There was 
absolutely no support for it as far as I know before 2012 and the introduction 
of Windows ARM tablets, and even then the things you could do with it were 
extremely limited.  

On 2017/03/21 6:24, "sqlite-users on behalf of Jaime Stuardo" 
 wrote:

Hello,

I have finally given up. After almost all day trying to compile SQLite 
amalgamated source code files for ARM platform I got the conclusion that SQLite 
is not for ARM platform, even when documentation says the contrary. I have VS 
2008 and I tried to compile some C++ wrappers out there that contains 
amalgamated files but with no success

I tried several command line parameters, but nothing.

Last try was, by using only amalgamated files (shell.c, sqlite3.c, 
sqlite3.h, sqlite3ext.h). There is no science with this. I open a VS2008 
command prompt and VS2012 ARM Command prompt and compile with:

"cl sqlite3.c -link -dll -out:sqlite3.dll -machine:ARM"

In both cases, I got this error:

"crtdefs.h(338) : fatal error C1189: #error :  Compiling Desktop 
applications for the ARM platform is not supported."

That took  me to the conclusion about SQLite is only for Desktop 
applications, which is very bad. Is there another alternative or trick to make 
it compile for ARM platform?

Thanks
Jaime

___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] SQLite does not support ARM platform?

2017-03-20 Thread Christian Schmitz

> Am 20.03.2017 um 22:24 schrieb Jaime Stuardo :
> 
> Hello,
> 
> I have finally given up. After almost all day trying to compile SQLite 
> amalgamated source code files for ARM platform I got the conclusion that 
> SQLite is not for ARM platform,…

Really?
I do that now for over 1.5 years.
With GCC on Linux for Raspberry Pi.

> In both cases, I got this error:
> 
> "crtdefs.h(338) : fatal error C1189: #error :  Compiling Desktop applications 
> for the ARM platform is not supported."
> 

Is that a Visual Studio thing?

Maybe you check those .h files for what they are about.
Is that maybe a Visual Studio header and you do something Microsoft doesn’t 
support?

Sincerely
Christian

-- 
Read our blog about news on our plugins:

http://www.mbsplugins.de/


___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


[sqlite] SQLite does not support ARM platform?

2017-03-20 Thread Jaime Stuardo
Hello,

I have finally given up. After almost all day trying to compile SQLite 
amalgamated source code files for ARM platform I got the conclusion that SQLite 
is not for ARM platform, even when documentation says the contrary. I have VS 
2008 and I tried to compile some C++ wrappers out there that contains 
amalgamated files but with no success

I tried several command line parameters, but nothing.

Last try was, by using only amalgamated files (shell.c, sqlite3.c, sqlite3.h, 
sqlite3ext.h). There is no science with this. I open a VS2008 command prompt 
and VS2012 ARM Command prompt and compile with:

"cl sqlite3.c -link -dll -out:sqlite3.dll -machine:ARM"

In both cases, I got this error:

"crtdefs.h(338) : fatal error C1189: #error :  Compiling Desktop applications 
for the ARM platform is not supported."

That took  me to the conclusion about SQLite is only for Desktop applications, 
which is very bad. Is there another alternative or trick to make it compile for 
ARM platform?

Thanks
Jaime

___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


[sqlite] RIGHT JOIN! still not supported?

2017-03-20 Thread PICCORO McKAY Lenz
i got this

Query Error: RIGHT and FULL OUTER JOINs are not currently supported
Unable to execute statement

still today in 21 ts century?

Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] Yet Another Why Doesn't Sqlite Use My Index question ...

2017-03-20 Thread Rob Willett

Just to close this thread down completely.

We've implemented the changes on our production server and the actual 
performance increase is even better than we predicted.


Our production server is a containerised Ubuntu Server. Its hardware 
configuration is significantly different to our Macs on which we 
develop. Our Macs have more RAM and SSD disks. The production server has 
other advantages though :)


The query took 90 mins on our production server, this is mainly due to 
slower disks than we have locally, so this was not unexpected.


After doing the performance changes (removing unneeded fields and adding 
in a covering index), we went down to 38 secs.


This has meant we are no longer looking at a second database just for 
analytics, we just needed to learn to use the database we already had :)


Rob

On 18 Mar 2017, at 5:48, Rob Willett wrote:

We've just implemented a covering index for the last step (is it 
really?) in our quest to get the query execution time down.


To summarise we have gone from 32 mins to 16 mins by updating an index 
so it doesn't use collate, we took another six minutes off by removing 
extra fields in the select we didn't need.


We have just created a new index which 'covers' all the fields we use 
in the select, this means (and I paraphrase) that we use the index to 
get all the data and there is no need to read from the database.


Well that was a bit of a surprise, the index creation took 45 mins, we 
ran the program again and thought, rats, we've cocked it up, it only 
took 54 secs, we got something wrong. So we checked it and checked 
again and we hasn't got anything wrong. Our query has moved from 32 
mins to 54 secs.


We're quite happy with that performance increase. In fact we're 
delighted, so thanks for all the help in getting us to this stage.


We have kept copies of the query planner bytecode output if anybody is 
interested. Gunter has had copies, but if anybody else would like 
them, please ask.


Many thanks again for all the help,

Rob

On 17 Mar 2017, at 22:12, Rob Willett wrote:


Dear all,

We progress steadily forward.

1. We immediately halved our execution time by moving to an updated 
index that doesn't use COLLATE. Thats 32mins to 16mins.


2. We then shaved a further six minutes off the execution time by 
removing extraneous fields in the select statement, so instead of 
"select * ...", we identified which fields we used and directly 
selected those. So we are now down to 10 mins or 1/3 of when we 
started for, to be honest, virtually no extra work, merely being 
smarter, or rather you being smarter.


3. We have looked through all our indexes and can see that every 
index has a COLLATE against it, even if the column is an integer. We 
have raised a support call with Navicat.


4. The next step is to create a "covering index" to try and get the 
whole of the query into the index. However its 22:11 in London and I 
need to get home.


Thanks very much for the help so far. Tomorrow is more tricky but 
I'll read up on covering indexes to see how to use them,.


Rob

On 17 Mar 2017, at 18:39, Simon Slavin wrote:

On 17 Mar 2017, at 6:22pm, Rob Willett 
 wrote:


4. Work through returning just the columns we actually need from 
our queries. We have a recollection that if we can build an index 
with all the information necessary in it, we can do all the work in 
joins rather than paging out to disk. Is this what you are 
referring to?


It works only where all the columns you need to read are in the same 
table.  The ideal form of a covering index is to have the columns 
listed in this order:


1) columns needed for the WHERE clause
2) columns needed for the ORDER BY clause which aren’t in (1)
3) columns needed to be read which aren’t in (2) or (1)

SQLite detects that all the information it needs for the SELECT is 
available from the index, so it doesn’t bother to read the table 
at all.  This can lead to something like a doubling of speed.  Of 
course, you sacrifice filespace, and making changes to the table 
takes a little longer.


5. Sleep (not exactly sure when) and watch three international 
rugby games tomorrow.


Sleep while waiting for indexes to be created and ANALYZE to work.  
May you see skilled players, creative moves and dramatic play.


Simon.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] Yet Another Why Doesn't Sqlite Use My Index question ...

2017-03-20 Thread Rob Willett

David,

We're English and masters of the understatement ;)

Rob

On 20 Mar 2017, at 15:04, David Raymond wrote:


"... Our query has moved from 32 mins to 54 secs.

We're quite happy with that performance increase."

I have to admit that the hearty chuckle which that statement produced 
from me hurt my sore throat. Totally worth it though.

___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] Yet Another Why Doesn't Sqlite Use My Index question ...

2017-03-20 Thread David Raymond
"... Our query has moved from 32 mins to 54 secs.

We're quite happy with that performance increase."

I have to admit that the hearty chuckle which that statement produced from me 
hurt my sore throat. Totally worth it though.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] First beta for SQLite 3.18.0.

2017-03-20 Thread Simon Slavin

On 20 Mar 2017, at 2:45pm, Simon Slavin  wrote:

> On 20 Mar 2017, at 2:42pm, Richard Hipp  wrote:
> 
>> More changes.  Please Reload one more time.
> 
> The changes are good but it’s still showing up as "alway" for me.  I even 
> tried a different browser.

Ignore that.  Now showing up correctly as "always".

Simon.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] First beta for SQLite 3.18.0.

2017-03-20 Thread Richard Hipp
On 3/20/17, Simon Slavin  wrote:
>
> On 20 Mar 2017, at 2:13pm, Richard Hipp  wrote:
>
>> All other corrections implemented.
>
> Check "alway" on the current mask sentence again.  No correction shown when
> I retrieve the page.

More changes.  Please Reload one more time.

-- 
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] First beta for SQLite 3.18.0.

2017-03-20 Thread Simon Slavin

On 20 Mar 2017, at 2:42pm, Richard Hipp  wrote:

> More changes.  Please Reload one more time.

The changes are good but it’s still showing up as "alway" for me.  I even tried 
a different browser.

Simon.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] First beta for SQLite 3.18.0.

2017-03-20 Thread Simon Slavin

On 20 Mar 2017, at 2:13pm, Richard Hipp  wrote:

> All other corrections implemented.

Check "alway" on the current mask sentence again.  No correction shown when I 
retrieve the page.

Simon.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] First beta for SQLite 3.18.0.

2017-03-20 Thread Richard Hipp
On 3/20/17, Simon Slavin  wrote:
>
> " • (Not yet implemented) Create indexes that might have been helpful to
> recent queries."
>
> —> If I recall a previous conversation correctly, it might clarify things to
> make this sentence end "queries executed by this connection.".  On the other
> hand you may have changed your idea about how this should work and that may
> no longer be accurate.
>

The decision might also be predicated on queries from prior
connections using information saved by the 0x0004 bit.  Or this
feature may never be implemented :-)

All other corrections implemented.
-- 
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] First beta for SQLite 3.18.0.

2017-03-20 Thread Simon Slavin

On 20 Mar 2017, at 1:06pm, Richard Hipp  wrote:

> https://www.sqlite.org/draft/index.html

In 

"   • (Not yet implemented) Create indexes that might have been helpful to 
recent queries."

—> If I recall a previous conversation correctly, it might clarify things to 
make this sentence end "queries executed by this connection.".  On the other 
hand you may have changed your idea about how this should work and that may no 
longer be accurate.

"The default MASK is and alway shall be 0xfffe. "

—> "always"

If it’s possible to specify masks using BLOB-type hex values, could you provide 
an example which shows how ?  Simply saying that "PRAGMA optimize(0x2);" works 
would be good enough.

"In the current implementation, a table is analyzed if only if"

—> "analyzed only if"

"   • Debugging mode. Do not actually perform any optimizations but instead 
return one line of text for each optimization that would have been done."

—> The section describes what is returned in debugging mode, but not what is 
returned in normal mode.  Presumably it returns that same text.

———

I see two patterns of use for this.  Some programmers will just use normal 
mode.  Others will use debugging mode first, and count the number of lines 
returned.  If the count is non-zero they will put up a dialog telling the user 
of a possible delay, allowing them to pick whether the optimizations are done 
or not.

Simon.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


[sqlite] First beta for SQLite 3.18.0.

2017-03-20 Thread Richard Hipp
The SQLite 3.18.0 release is forecast to occur within about two weeks.
A snapshot of the latest amalgamation source code is available at

https://www.sqlite.org/download.html

Please review the changes and try out the latest code.  Report any
issues or concerns on this mailing list, or directly to me at the
email shown below.  Your feedback is important.

Draft documentation is available at

 https://www.sqlite.org/draft/index.html
 https://www.sqlite.org/draft/releaselog/current.html

The release checklist is on-line at

 https://www.sqlite.org/checklists/318/index

The 3.18.0 release will occur when the above checklist goes all green.
We expect start marking off checklist items later this week or early
next week.  (Test procedure review - item 1 - might be checked off a
little sooner.)

If you access SQLite source code using a local Fossil client, please
note that Fossil version 2.0 or later is necessary to see SQLite
changes since 2017-03-12.  Precompiled binaries and easy-to-compile
source code for Fossil are available at
https://www.fossil-scm.org/fossil/uv/download.html if you need to
upgrade.

Thank you for taking the time to review this beta.
-- 
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users