[BDB 11gR2 Beta] [#18415] Compilation errors and warnings
Alex Gorrod
alexander.gorrod at oracle.com
Wed Mar 17 19:53:26 PDT 2010
Hi Raj,
On 18/03/2010 4:30 AM, Raj Laad wrote:
> I tried wce_sql.exe and I can insert key/value pairs in the database.
That's great news.
> I wish you had C# API! I see that your examples (e.g. examples_cxx) use
> direct database API. I am interested in sticking to SQL interface. Where can
> I find SQLLite examples and projects?
Unfortunately we don't have a plan to directly support a C# API in the
upcoming release. We have not tried it out internally, but it's possible
that the ADO.Net interface (http://sqlite.phxsoftware.com/) for SQLite
will worth with Berkeley DB SQL on Windows Mobile.
I have not tried that out though.
As for sample applications.. The examples you refer to are for the base
C++ API. There is some SQL example code in the distribution as well.
Most relevant for you is probably the Windows Mobile sample application
you built and ran. That code is in the release tree at:
db-5.0.XX/sql/examples/wce_sql
The source code that actually uses the Berkeley DB SQL C API is in the
file excxx_wce_sqlDlg.cpp in the function
Cexcxx_wce_sqlDlg::OnButtonClicked2.
There are other non Windows Mobile specific sample applications in the
release package as well. They might be helpful for you as well. You can
find them in:
db-5.0.XX/sql/examples/c
I hope this helps, and thanks for trying out our product!
- Alex
>
> Regards,
> - Raj
> Raj Laad
> Cell: 617-538-9593
>
> -----Original Message-----
> From: Alex Gorrod [mailto:alexander.gorrod at oracle.com]
> Sent: Sunday, March 14, 2010 6:31 PM
> To: Raj Laad
> Cc: bdb-beta-feedback at oss.oracle.com; support at sleepycat.com;
> karl.fu at oracle.com
> Subject: Re: [BDB 11gR2 Beta] [#18415] Compilation errors and warnings
>
> Hi Raj,
>
> Thanks for trying out my suggestion.
>
> The documentation you are quoting is for the Windows desktop build, it
> is quite different to the Windows Mobile build. We obviously need to
> differentiate better - I'll ask our documentation people to do that.
>
> The Windows Mobile build does not create dll files, it builds a static
> library, which is linked directly into an executable.
>
> The warnings you report should not be important, though I don't
> understand why you are seeing them. Do you see an output file called:
>
> db-5.0.11/build_wince/Debug_PocketPC2003_ARMV4/wce_sql.exe
> ?
>
> You should be able to copy that onto a Windows Mobile device, or the
> emulator, and run it standalone.
>
> We have not yet built the binary package for Windows, and we have not
> historically included the Windows Mobile binaries with that package. I
> doubt that will change in this release, since there are so many
> different combinations of platforms and CPUs it's not practical for us
> to include them all.
>
> Also, one more clarification. The C# API is not currently supported on
> Windows Mobile. You should be able to use the C API as an unmanaged
> library, the Berkeley DB team does not have much expertise in that
> configuration.
>
> - Alex
>
> On 13/03/2010 7:11 AM, Raj Laad wrote:
>> Hi Alex,
>>
>> I was able to compile and link successfully, without any errors. Same
>> warning is given 107 times; it may not be important.
>> --------------
>> Warning 1 warning LNK4099: PDB 'vc80.pdb' was not found with
>> '.\Debug_PocketPC2003_ARMV4\wce_tpcb\TpcbUI.obj' or at
>>
> 'c:\Projects\Oracle\db-5.0.11\build_wince\Debug_PocketPC2003_ARMV4\vc80.pdb'
>> ; linking object as if no debug info TpcbUI.obj
>> --------------
>>
>> We are using VS 2005 and C#, and we need to integrate with SQL API. Under
>> Building the SQL API section, I found:
>> -------------
>> SQL support is built automatically on Windows. The SQL library is built as
>> libdb_sql50.dll in the Release mode or libdb_sql50d.dll in the Debug mode.
>> An SQL command line interpreter called db_sql_shell.exe is also built.
>> -------------
>>
>> I did not find any DLL under db-5.0.11. I need help to proceed further.
>>
>> I remember reading that there are binaries available for Windows, but
> can't
>> find it now. We can use existing binaries and API kit.
>>
>> Please advise.
>>
>> Regards,
>> - Raj
>> Raj Laad
>> Cell: 617-538-9593
>>
>>
>> -----Original Message-----
>> From: Alex Gorrod [mailto:alexander.gorrod at oracle.com]
>> Sent: Thursday, March 11, 2010 10:49 PM
>> To: Raj Laad
>> Cc: bdb-beta-feedback at oss.oracle.com; support at sleepycat.com;
>> karl.fu at oracle.com
>> Subject: Re: [BDB 11gR2 Beta] [#18415] Compilation errors and warnings
>>
>> Hi,
>>
>> I realized that I did not answer all of your questions:
>>
>> On 12/03/2010 12:52 PM, Raj Laad wrote:
>>> . Is it OK to use "Visual Studio 2005"? Seems to compile fine.
>>
>> Yes, you can compile using Visual Studio 2005.
>>
>>> . Where is libdb_sql50sd.lib?
>>
>> Once the errors are fixed the file will be output to:
>>
>> build_wince/Debug_PocketPC2003_ARMV4/ if you built in debug mode for the
>> PocketPC2003 target platform. Or a correspondingly named folder for
>> other configurations.
>>
>> - Alex
>>
>>>
>>> -----------------------------------
>>>
>>> Error 210 error C2065: 'db_errno' : undeclared identifier
>>> c:\Projects\Oracle\db-5.0.11\sql\adapter\btree.c 3005
>>>
>>> Error 211 error C2106: '=' : left operand must be l-value
>>> c:\Projects\Oracle\db-5.0.11\sql\adapter\btree.c 3005
>>>
>>> Error 212 fatal error LNK1181: cannot open input file
>>> 'libdb_sql50sd.lib' wce_sql
>>>
>>> Warning 1 warning LNK4099: PDB 'vc80.pdb' was not found with
>>> '.\debug_pocketpc2003_armv4\wce_tpcb\TpcbUI.obj' or at
>>>
>>
> 'c:\Projects\Oracle\db-5.0.11\build_wince\Debug_PocketPC2003_ARMV4\vc80.pdb'
>> ;
>>> linking object as if no debug info TpcbUI.obj
>>>
>>> Warning 2 warning LNK4099: PDB 'vc80.pdb' was not found with
>>> '.\debug_pocketpc2003_armv4\wce_tpcb\TpcbExample.obj' or at
>>>
>>
> 'c:\Projects\Oracle\db-5.0.11\build_wince\Debug_PocketPC2003_ARMV4\vc80.pdb'
>> ;
>>> linking object as if no debug info TpcbExample.obj
>>>
>>> Warning 3 warning LNK4099: PDB 'vc80.pdb' was not found with
>>> 'Debug_PocketPC2003_ARMV4\libdb50sd.lib' or at
>>>
>>
> 'c:\Projects\Oracle\db-5.0.11\build_wince\Debug_PocketPC2003_ARMV4\vc80.pdb'
>> ;
>>> linking object as if no debug info libdb50sd.lib
>>>
>>> Warning 4 warning LNK4099: PDB 'vc80.pdb' was not found with
>>> 'Debug_PocketPC2003_ARMV4\libdb50sd.lib' or at
>>>
>>
> 'c:\Projects\Oracle\db-5.0.11\build_wince\Debug_PocketPC2003_ARMV4\vc80.pdb'
>> ;
>>> linking object as if no debug info libdb50sd.lib
>>>
>>> Warning 5 warning LNK4099: PDB 'vc80.pdb' was not found with
>>> 'Debug_PocketPC2003_ARMV4\libdb50sd.lib' or at
>>>
>>
> 'c:\Projects\Oracle\db-5.0.11\build_wince\Debug_PocketPC2003_ARMV4\vc80.pdb'
>> ;
>>> linking object as if no debug info libdb50sd.lib
>>>
>>> Warning 6 warning LNK4099: PDB 'vc80.pdb' was not found with
>>> 'Debug_PocketPC2003_ARMV4\libdb50sd.lib' or at
>>>
>>
> 'c:\Projects\Oracle\db-5.0.11\build_wince\Debug_PocketPC2003_ARMV4\vc80.pdb'
>> ;
>>> linking object as if no debug info libdb50sd.lib
>>>
>>> Warning 7 warning LNK4099: PDB 'vc80.pdb' was not found with
>>> 'Debug_PocketPC2003_ARMV4\libdb50sd.lib' or at
>>>
>>
> 'c:\Projects\Oracle\db-5.0.11\build_wince\Debug_PocketPC2003_ARMV4\vc80.pdb'
>> ;
>>> linking object as if no debug info libdb50sd.lib
>>>
>>> Warning 8 warning LNK4099: PDB 'vc80.pdb' was not found with
>>> 'Debug_PocketPC2003_ARMV4\libdb50sd.lib' or at
>>>
>>
> 'c:\Projects\Oracle\db-5.0.11\build_wince\Debug_PocketPC2003_ARMV4\vc80.pdb'
>> ;
>>> linking object as if no debug info libdb50sd.lib
>>>
>>> Regards,
>>>
>>> - Raj
>>>
>>> Raj Laad
>>>
>>> CTO, Pristine Infotech, Inc.
>>>
>>> Cell: 617-538-9593
>>>
>>> www.pristineinfotech.com<http://www.pristineinfotech.com/>
>>>
>>> This email communication including its attachments is intended only for
>>> the use of the individuals to whom it has been addressed. It may contain
>>> information that is privileged and confidential to Pristine Infotech,
>>> Inc. If the reader of this message is not the intended recipient, you
>>> are hereby notified that any dissemination, distribution or copying of
>>> this communication is strictly prohibited. If you have read this
>>> communication in error, please notify us immediately by return e-mail.
>>>
>>>
>>>
>>> _______________________________________________
>>> BDB-BETA-FEEDBACK mailing list
>>> BDB-BETA-FEEDBACK at oss.oracle.com
>>> http://oss.oracle.com/mailman/listinfo/bdb-beta-feedback
>>
>
More information about the BDB-BETA-FEEDBACK
mailing list