Thanks for the info.
Im trying with the LCC ide but I get odd errors while trying to compile:
"c:\lcc\bin\make.exe: Commands defined twice for target where.obj near line
87"
I was getting a similar error with another file, I remade the project and
now Im getting the same error on a different file.
What could be causing it?
Thanks.
----- Original Message -----
From: "John Stanton" <[EMAIL PROTECTED]>
To: <sqlite-users@sqlite.org>
Sent: Saturday, March 10, 2007 4:02 PM
Subject: Re: [sqlite] Compiling the linux package on windows using LCC ?
GCC will compile you a library usable with a broad range of C compilers.
If you find the gcc library unusable use the makefile as the basis for
compiling it using lcc. I use lcc and gcc (mingw) interchangably. GCC
has optimization but if you write elegant and efficient C lcc will
generate excellent code and compiles very fast.
If you get the options correct you can compile each module using lcc or
use the lcc IDE to compile them all at once then use ar to build a link
library. The makefile generated by configure and gcc or the one in the
Sqlite Windows zip file will give you a template to follow.
I recollect that compiling Sqlite under lcc was not a big deal, but it was
a long time back for me and I cannot recall the precise details. Now I use
gcc to build the static library and have a compiler which works
identically on all flavors of Windows, Linux, AIX and Solaris.
If you want dynamic linking to a DLL you need to look at the lcc
documentation to see precisely how it is done.
Gussimulator wrote:
GCC?, I need to use the resulting DLL on normal C under windows later on,
without having strange dependencies, etc.
I'd like to know what am I doing wrong when I try to compile the
sources... Do I have to output obj for each source and then somehow link
this into the final library?
----- Original Message ----- From: "John Stanton" <[EMAIL PROTECTED]>
To: <sqlite-users@sqlite.org>
Sent: Friday, March 09, 2007 2:10 PM
Subject: Re: [sqlite] Compiling the linux package on windows using LCC ?
Gussimulator wrote:
Hi, I would like to compile the tar version of the sources using LCC
under Windows.
Since I'm not a *nix guy, I don't know where to start, because my
little linux knowledge played against me. Heres the problem, I tried
using the makefile with make.exe from LCC but that didnt work out (it
said it couldn't open the makefile...) so I tried the config but I dont
know which tool handles this, so I was back to square one...
So I began questioning myself... Would it even be possible to compile
this package under windows with LCC?
I want to perform a static compilation, so I can statically link the
library on my application. However I'd still be happy if I could
compile as a dynamic lib.
Now that I'm at it, I would like to suggest for the windows build, that
the required .exp or .lib be added on the package as well, since this
allows for easier linking on applications - at least under my
environment (I'm sure others would like this as well - However, being
able to compile the source by myself would take care of this issue).
Thanks.
A simple way is to compile it under gcc then use LCC.
After you have compiled with gcc you may discover that to use LCC does
not make a lot of sense since my experience with both compilers is that
lcc is very well implemented but lacks the level of optimization
available with gcc. A static library created with gcc will work with
your lcc programs if you are using lcc for your applications to take
advantage of some of its clever extensions to regular C.
-----------------------------------------------------------------------------
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]
-----------------------------------------------------------------------------
