I'd like to update on my current status regarding the subject.
After 3 and a half headaches, I managed to output an obj and link it with
the definitions file.
However:
(using pseudo-paths for the sake of readability)
1) In LCC I'm using the following switches:
/ansic /o "path-for\output.obj" "path-to\main.c"
It produces 0 errors and 27 warnings.. I believe I can move on from
here, despite warnings.
2) In LCCLNK I'm using the following:
/dll "path-to\output.obj" "path-to\sqlite3.def"
I'm getting a ton of "Specified export XX is not defined"
...And later on a "Missing exports. Aborting" message.
Why is this happening?, did I compiled it wrong or the exports file I've got
is not the correct one? (from dll package - sqlite3 website).
Perhaps compiling just main.c is not how it should be done? if so, what
should I do in order to properly compile all the sources? - This time I'm
using the "pre-processed" version of the sources for windows, since I gave
up on the other package...
Thanks again.
----- Original Message -----
From: "Gussimulator" <[EMAIL PROTECTED]>
To: <sqlite-users@sqlite.org>
Sent: Friday, March 09, 2007 12:59 PM
Subject: [sqlite] Compiling the linux package on windows using LCC ?
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.
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
