Hum.  So Mickeysoft does not supply a lib converter/creator utility?  I even
have a "Make" and "Grep" utility when I get nostalgic for my limited Unix
days.

My generator has an "-a" option to, "Add '_' alias for MS flavor cdecl
functions."

Is that what you mean?

Someday if I can find someone to hold a big enough caliber gun to my head,
I'm going to learn something about the "Visual" development world.  I
installed the C++ "Express" version and was so underwhlmed by the
performance I started look for that person with a giant gun :-(

Fred

-----Original Message-----
From: sqlite-users-boun...@sqlite.org
[mailto:sqlite-users-boun...@sqlite.org]on Behalf Of Mihai Limbasan
Sent: Saturday, July 25, 2009 1:13 PM
To: General Discussion of SQLite Database
Subject: Re: [sqlite] .lib file?


Fred,

Unfortunately, .lib (or, for that matter, .obj) files created by Borland
compilers are not compatible with the Microsoft toolchain, and
vice-versa. Borland uses a variant of the OMF object format, and
Microsoft uses a variant of COFF.

On 07/25/2009 08:09 PM, Fred Williams wrote:
> Paul,
>
> If you wish I can send yoou a SQLite3.lib file I just generated using my
old
> Borland C++ Builder 5 Lib utility.  Can't attach it here so contact me:
>
> fwillia...@gmail.com
>
> And I'll attach it to a reply.
>
> Fred
>
>
> -----Original Message-----
> From: sqlite-users-boun...@sqlite.org
> [mailto:sqlite-users-boun...@sqlite.org]on Behalf Of Doug
> Sent: Saturday, July 25, 2009 11:24 AM
> To: 'General Discussion of SQLite Database'
> Subject: Re: [sqlite] .lib file?
>
>
> Hi Paul --
>
> When I build SQLite (from the amalgamation) into a DLL VS2008 (and earlier
> as I recall) automatically creates an import library in the same directory
> as the .DLL file.  I also _used_ to run the following command separately
to
> create the import lib:
>
> link /lib /def:sqlite3.def
>
> I haven't kept my sqlite3.def file up to date, but it's fairly recent if
you
> want to use it.  Since we can't post files to the newsgroup, I'll append
it
> here.
>
> Doug
>
> <start file>
> EXPORTS
> sqlite3_aggregate_context
> sqlite3_aggregate_count
> sqlite3_auto_extension
> sqlite3_bind_blob
> sqlite3_bind_double
> sqlite3_bind_int
> sqlite3_bind_int64
> sqlite3_bind_null
> sqlite3_bind_parameter_count
> sqlite3_bind_parameter_index
> sqlite3_bind_parameter_name
> sqlite3_bind_text
> sqlite3_bind_text16
> sqlite3_bind_value
> sqlite3_bind_zeroblob
> sqlite3_blob_bytes
> sqlite3_blob_close
> sqlite3_blob_open
> sqlite3_blob_read
> sqlite3_blob_write
> sqlite3_busy_handler
> sqlite3_busy_timeout
> sqlite3_changes
> sqlite3_clear_bindings
> sqlite3_close
> sqlite3_collation_needed
> sqlite3_collation_needed16
> sqlite3_column_blob
> sqlite3_column_bytes
> sqlite3_column_bytes16
> sqlite3_column_count
> sqlite3_column_decltype
> sqlite3_column_decltype16
> sqlite3_column_double
> sqlite3_column_int
> sqlite3_column_int64
> sqlite3_column_name
> sqlite3_column_name16
> sqlite3_column_text
> sqlite3_column_text16
> sqlite3_column_type
> sqlite3_column_value
> sqlite3_commit_hook
> sqlite3_complete
> sqlite3_complete16
> sqlite3_create_collation
> sqlite3_create_collation16
> sqlite3_create_collation_v2
> sqlite3_create_function
> sqlite3_create_function16
> sqlite3_create_module
> sqlite3_create_module_v2
> sqlite3_data_count
> sqlite3_db_handle
> sqlite3_declare_vtab
> sqlite3_enable_load_extension
> sqlite3_enable_shared_cache
> sqlite3_errcode
> sqlite3_errmsg
> sqlite3_errmsg16
> sqlite3_exec
> sqlite3_expired
> sqlite3_extended_result_codes
> sqlite3_file_control
> sqlite3_finalize
> sqlite3_free
> sqlite3_free_table
> sqlite3_get_autocommit
> sqlite3_get_auxdata
> sqlite3_get_table
> sqlite3_global_recover
> sqlite3_interrupt
> sqlite3_last_insert_rowid
> sqlite3_libversion
> sqlite3_libversion_number
> sqlite3_load_extension
> sqlite3_malloc
> sqlite3_memory_alarm
> sqlite3_memory_highwater
> sqlite3_memory_used
> sqlite3_mprintf
> sqlite3_mutex_alloc
> sqlite3_mutex_enter
> sqlite3_mutex_free
> sqlite3_mutex_leave
> sqlite3_mutex_try
> sqlite3_open
> sqlite3_open16
> sqlite3_open_v2
> sqlite3_overload_function
> sqlite3_prepare
> sqlite3_prepare16
> sqlite3_prepare16_v2
> sqlite3_prepare_v2
> sqlite3_profile
> sqlite3_progress_handler
> sqlite3_realloc
> sqlite3_release_memory
> sqlite3_reset
> sqlite3_reset_auto_extension
> sqlite3_result_blob
> sqlite3_result_double
> sqlite3_result_error
> sqlite3_result_error16
> sqlite3_result_error_nomem
> sqlite3_result_error_toobig
> sqlite3_result_int
> sqlite3_result_int64
> sqlite3_result_null
> sqlite3_result_text
> sqlite3_result_text16
> sqlite3_result_text16be
> sqlite3_result_text16le
> sqlite3_result_value
> sqlite3_result_zeroblob
> sqlite3_rollback_hook
> sqlite3_set_authorizer
> sqlite3_set_auxdata
> sqlite3_sleep
> sqlite3_snprintf
> sqlite3_soft_heap_limit
> sqlite3_sql
> sqlite3_step
> sqlite3_thread_cleanup
> sqlite3_threadsafe
> sqlite3_total_changes
> sqlite3_trace
> sqlite3_transfer_bindings
> sqlite3_update_hook
> sqlite3_user_data
> sqlite3_value_blob
> sqlite3_value_bytes
> sqlite3_value_bytes16
> sqlite3_value_double
> sqlite3_value_int
> sqlite3_value_int64
> sqlite3_value_numeric_type
> sqlite3_value_text
> sqlite3_value_text16
> sqlite3_value_text16be
> sqlite3_value_text16le
> sqlite3_value_type
> sqlite3_version
> sqlite3_vfs_find
> sqlite3_vfs_register
> sqlite3_vfs_unregister
> sqlite3_vmprintf
> <end file>
>
>
>
>> -----Original Message-----
>> From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-
>> boun...@sqlite.org] On Behalf Of Paul Claessen
>> Sent: Saturday, July 25, 2009 10:49 AM
>> To: sqlite-users@sqlite.org
>> Subject: Re: [sqlite] .lib file?
>>
>> Thanks Pavel.
>>
>> Two points though:
>>
>> 1. The amalgated sources were, apparently, not written with MS Visual
>> Study in mind, since compiling it results in over 100 errors
>> (mostly invalid pointer conversions)
>> 2. If I have a number of apps, it would really be more efficient to use
>> the DLL.
>>
>> I'm sure I can fix all the pointer casts (shouldn't be necessary if the
>> code used more consistent types!), but that would take me a
>> lot of time, plus, there should be a way to simply use the .dll: since
>> there IS a windows console app, there must be either a .lib
>> file somewhere, or there is an alternative way of using DLL's from a
>> windows console app, that I'm not aware of.
>>
>> Kind regards,
>>
>> ~ Paul Claessen
>>
>>
>>
>>> -----Original Message-----
>>> From: Pavel Ivanov [mailto:paiva...@gmail.com]
>>> Sent: Saturday, July 25, 2009 11:31 AM
>>> To: p...@claessen.com; General Discussion of SQLite Database
>>> Subject: Re: [sqlite] .lib file?
>>>
>>> You can take sqlite3.c from amalgamation package and include it into
>>> your project. This way SQLite will be included into your application
>>> and you won't need any .dll or .lib files.
>>>
>>> Pavel
>>>
>>> On Sat, Jul 25, 2009 at 10:41 AM, Paul Claessen<p...@claessen.com>
>>>
>> wrote:
>>
>>>> Greetings,
>>>>
>>>>
>>>>
>>>> I'm trying to build and use the short sample C code on the quick
>>>>
>> start page
>>
>>> (http://www.sqlite.org/quickstart.html) for windows as a
>>>
>>>> simple win32 console app, using Visual Studio 2008.
>>>>
>>>> In order to provide linkage to the DLL, I need to link with the
>>>>
>> .lib file that is usually created
>>
>>> when creating a DLL. Where can I
>>>
>>>> find that file?
>>>>
>>>> Or are there other ways to actually build the above mentioned app,
>>>>
>> without such a library?
>>
>>>> There is a windows test console app, but I can't find the project
>>>>
>> files for it. Does anyone have
>>
>>> them, and knows how to build a
>>>
>>>> simple console app, using the dell, in Visual Studio?
>>>>
>>>>
>>>>
>>>> Kind regards,
>>>>
>>>>
>>>>
>>>> ~ Paul Claessen
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>
>
>
> _______________________________________________
> 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
>
_______________________________________________
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

Reply via email to