On Wed, 1 Feb 2006, AshishShrestha wrote:
this is not a major issue. it is just the csc is called with -o sqlite.so so
the output file is called sqlite.so instead of sqlite.dll. As a result the
rest of the installation fails. Just removing the -o argument to csc works
fine.
Hello,
just removing the -o argument in the csc statement will break the
following install-extension statement, which relies on the output being
called .so
I have added a hack that checks (software-version) for the presence of
Windows and calls the output .dll then. The change is committed in SVN and
the patched egg is also on my website at
http://www.chust.org/projects/sqlite3.egg
[...]
On 2/1/06, Thomas Chust <[EMAIL PROTECTED]> wrote:
[...]
I wonder why this is a problem on Windows. At least on Unices CHICKEN
seems to load every piece of compiled code from .so files regardless of
the specific operating system's idea what the file extension for a shared
library should be. For example on MacOS X the dynamic libraries are
normally called .dylib, but CHICKEN uses .so for its compiled code and is
happy with that.
Is it impossible to load code from anything not called .dll on Windows?!?
[...]
Before I make similar changes to my other eggs, though, I would still very
much like to have an answer to these questions. Why does CHICKEN load from
.so files on every system except Windows but requires .dll on Windows? In
my opinion you should either stick to the .so extension on every platform
or use the native extension on every platform, not mix these concepts.
cu,
Thomas
_______________________________________________
Chicken-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/chicken-users
