IBPP, a C++ API for Firebird Server

20.07.2010 6:06, John Roberts пишет:
> Using wxWidgets 2.9 or above (unicode VC++ Vista 32&  64) I get many errors
> when attempting to compile.
>
> 1. C:\wxWidgets-2.9\include\wx/translation.h(39) : warning C4005: '_' :
> macro redefinition
>         C:\Cxx\DbProjects\IBPP\ibpp.h(87) : see previous definition of '_'
>
> Appears to be in conflict with the language translation macro in wxWidgets
> _(languagestr)
>
> 2. I get many similar to this:
> _ibpp.cpp(87) : error C2664: 'OutputDebugStringW' : cannot convert parameter
> 1 from 'const char *' to 'LPCWSTR'
>
> Forgive my ignorance but what do I do with this?
> John
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> ibpp-discuss mailing list
> Post to ibpp-discuss@...
> Settings https://lists.sourceforge.net/lists/listinfo/ibpp-discuss
> http://www.ibpp.org
>
>
See FlameRobin
//! converts wxString to std:string
std::string wx2std(const wxString& input, wxMBConv* conv)
{
if (input.empty())
return "";
if (!conv)
conv = wxConvCurrent;
return std::string(input.mb_str(*conv));
}
//-----------------------------------------------------------------------------
//! converts std:string to wxString
wxString std2wx(const std::string& input, wxMBConv* conv)
{
if (input.empty())
return wxEmptyString;
if (!conv)
conv = wxConvCurrent;
return wxString(input.c_str(), *conv);
}

On 20.07.2010 04:06, John Roberts wrote:

> Using wxWidgets 2.9 or above (unicode VC++ Vista 32&  64) I get many errors
> when attempting to compile.
>
> 1. C:\wxWidgets-2.9\include\wx/translation.h(39) : warning C4005: '_' :
> macro redefinition
>         C:\Cxx\DbProjects\IBPP\ibpp.h(87) : see previous definition of '_'
>
> Appears to be in conflict with the language translation macro in wxWidgets
> _(languagestr)
>
> 2. I get many similar to this:
> _ibpp.cpp(87) : error C2664: 'OutputDebugStringW' : cannot convert parameter
> 1 from 'const char *' to 'LPCWSTR'
>
> Forgive my ignorance but what do I do with this?

The first one is not an issue for us with FlameRobin source code, 
because we use precompiled headers and the wxWidgets headers are 
included earlier than the IBPP header.  _() gets defined in wx, and IBPP 
doesn't define it again.
That way you can use gettext translation tools on IBPP messages too. 
(Or at least you should be able to, we haven't tried yet.)

The second one I have never experienced, even though I compile FR 
routinely with different settings on various platforms.

-- 
Michael Hieke

----- Original Message ----- 
From: "Borr" <Boris_741@...>
To: <ibpp-discuss@...>
Sent: Tuesday, July 20, 2010 1:24 PM
Subject: Re: [IBPP-DISCUSS] Compile IBPP in wxWidgets project


>  20.07.2010 6:06, John Roberts пишет:
>> Using wxWidgets 2.9 or above (unicode VC++ Vista 32&  64) I get many 
>> errors
>> when attempting to compile.
>>
>> 1. C:\wxWidgets-2.9\include\wx/translation.h(39) : warning C4005: '_' :
>> macro redefinition
>>         C:\Cxx\DbProjects\IBPP\ibpp.h(87) : see previous definition of 
>> '_'
>>
>> Appears to be in conflict with the language translation macro in 
>> wxWidgets
>> _(languagestr)
>>
>> 2. I get many similar to this:
>> _ibpp.cpp(87) : error C2664: 'OutputDebugStringW' : cannot convert 
>> parameter
>> 1 from 'const char *' to 'LPCWSTR'
>>
>> Forgive my ignorance but what do I do with this?
>> John


> See FlameRobin
> //! converts wxString to std:string
> std::string wx2std(const wxString& input, wxMBConv* conv)
> {
> if (input.empty())
> return "";
> if (!conv)
> conv = wxConvCurrent;
> return std::string(input.mb_str(*conv));
> }
> //-----------------------------------------------------------------------------
> //! converts std:string to wxString
> wxString std2wx(const std::string& input, wxMBConv* conv)
> {
> if (input.empty())
> return wxEmptyString;
> if (!conv)
> conv = wxConvCurrent;
> return wxString(input.c_str(), *conv);
> }

Thanks for your reply Boris. However, I am not dealing with wxString here 
and don't understand how wx2std() or std2wx() will help convert parameter 1 
from 'const char *' to 'LPCWSTR' where it is found in ibpp code.
eg
    path.append("fbclient.dll");
    mHandle = LoadLibrary(path.c_str());
gives compiler error
\ibpp\_ibpp.cpp(142) : error C2664: 'LoadLibraryW' : cannot convert 
parameter 1 from 'const char *' to 'LPCWSTR'

Cheers, John

2010/7/20 John Roberts <johnr@...>:
[snip]
> Thanks for your reply Boris. However, I am not dealing with wxString here
> and don't understand how wx2std() or std2wx() will help convert parameter 1
> from 'const char *' to 'LPCWSTR' where it is found in ibpp code.
> eg
>    path.append("fbclient.dll");
>    mHandle = LoadLibrary(path.c_str());
> gives compiler error
> \ibpp\_ibpp.cpp(142) : error C2664: 'LoadLibraryW' : cannot convert
> parameter 1 from 'const char *' to 'LPCWSTR'
>
> Cheers, John

Hi John,

IBPP can (still) not be compiled with UNICODE set. There are a few
minor changes that have to be made. You can, for example, change to
call to LoadLibrary() to LoadLibraryA().

Greetings,

Daniel Albuschat

-- 
eat(this); // delicious suicide

----- Original Message ----- 
From: "Daniel Albuschat" <d.albuschat@...>
To: <ibpp-discuss@...>
Sent: Tuesday, July 20, 2010 2:59 PM
Subject: Re: [IBPP-DISCUSS] Compile IBPP in wxWidgets project


> 2010/7/20 John Roberts <johnr@...>:
> [snip]
>> Thanks for your reply Boris. However, I am not dealing with wxString here
>> and don't understand how wx2std() or std2wx() will help convert parameter 
>> 1
>> from 'const char *' to 'LPCWSTR' where it is found in ibpp code.
>> eg
>> path.append("fbclient.dll");
>> mHandle = LoadLibrary(path.c_str());
>> gives compiler error
>> \ibpp\_ibpp.cpp(142) : error C2664: 'LoadLibraryW' : cannot convert
>> parameter 1 from 'const char *' to 'LPCWSTR'
>>
>> Cheers, John
>
> Hi John,
>
> IBPP can (still) not be compiled with UNICODE set. There are a few
> minor changes that have to be made. You can, for example, change to
> call to LoadLibrary() to LoadLibraryA().
>
> Greetings,
>
> Daniel Albuschat

Thanks Daniel. I thought that might be the case.
To stay with UNICODE I have used casts through the IBPP code as per examples 
below:

mHandle = LoadLibrary((LPCWSTR)("gds32.dll"));
mHandle = LoadLibrary((LPWSTR)fbdll);

It compiles and runs now with the limited testing I have done so far. If I 
continue to use it I will use svn to maintain my changes if they are 
appropriate.
Cheers, John

----- Original Message ----- 
From: "Michael Hieke" <michael.hieke@...>
To: <ibpp-discuss@...>
Sent: Tuesday, July 20, 2010 2:27 PM
Subject: Re: [IBPP-DISCUSS] Compile IBPP in wxWidgets project


> On 20.07.2010 04:06, John Roberts wrote:
>
>> Using wxWidgets 2.9 or above (unicode VC++ Vista 32&  64) I get many 
>> errors
>> when attempting to compile.
>>
>> 1. C:\wxWidgets-2.9\include\wx/translation.h(39) : warning C4005: '_' :
>> macro redefinition
>>         C:\Cxx\DbProjects\IBPP\ibpp.h(87) : see previous definition of 
>> '_'
>>
>> Appears to be in conflict with the language translation macro in 
>> wxWidgets
>> _(languagestr)
>>
>> 2. I get many similar to this:
>> _ibpp.cpp(87) : error C2664: 'OutputDebugStringW' : cannot convert 
>> parameter
>> 1 from 'const char *' to 'LPCWSTR'
>>
>> Forgive my ignorance but what do I do with this?
>
> The first one is not an issue for us with FlameRobin source code,
> because we use precompiled headers and the wxWidgets headers are
> included earlier than the IBPP header.  _() gets defined in wx, and IBPP
> doesn't define it again.
> That way you can use gettext translation tools on IBPP messages too.
> (Or at least you should be able to, we haven't tried yet.)
>
> The second one I have never experienced, even though I compile FR
> routinely with different settings on various platforms.
>
> -- 
> Michael Hieke

Thanks Michael. Seems ok (fingers crossed) with the first point and now with 
the second using casts as per previous post.
Cheers, John

John,

I had a similar problem with the '_' redefinition with IBPP and GTK on
Linux and I found the following code stopped the warnings:

...
#include <ibpp.h>
...
#undef _ //Stop Gnome moaning
#include <gnome.h>

Something similar for wxWidgets may solve your first problem.

Regards

Tony Whyman
MWA Software



John Roberts wrote:
> Using wxWidgets 2.9 or above (unicode VC++ Vista 32 & 64) I get many errors 
> when attempting to compile.
>
> 1. C:\wxWidgets-2.9\include\wx/translation.h(39) : warning C4005: '_' : 
> macro redefinition
>        C:\Cxx\DbProjects\IBPP\ibpp.h(87) : see previous definition of '_'
>
> Appears to be in conflict with the language translation macro in wxWidgets 
> _(languagestr)
>
> 2. I get many similar to this:
> _ibpp.cpp(87) : error C2664: 'OutputDebugStringW' : cannot convert parameter 
> 1 from 'const char *' to 'LPCWSTR'
>
> Forgive my ignorance but what do I do with this?
> John 
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> ibpp-discuss mailing list
> Post to ibpp-discuss@...
> Settings https://lists.sourceforge.net/lists/listinfo/ibpp-discuss
> http://www.ibpp.org
>

----- Original Message ----- 
From: "John Roberts" <johnr@...>
To: <Boris_741@...>; <ibpp-discuss@...>
Sent: Tuesday, July 20, 2010 2:56 PM
Subject: Re: [IBPP-DISCUSS] Compile IBPP in wxWidgets project


>
> ----- Original Message ----- 
> From: "Borr" <Boris_741@...>
> To: <ibpp-discuss@...>
> Sent: Tuesday, July 20, 2010 1:24 PM
> Subject: Re: [IBPP-DISCUSS] Compile IBPP in wxWidgets project
>
>> See FlameRobin
>> //! converts wxString to std:string
>> std::string wx2std(const wxString& input, wxMBConv* conv)
>> {
>> if (input.empty())
>> return "";
>> if (!conv)
>> conv = wxConvCurrent;
>> return std::string(input.mb_str(*conv));
>> }
>> //-----------------------------------------------------------------------------
>> //! converts std:string to wxString
>> wxString std2wx(const std::string& input, wxMBConv* conv)
>> {
>> if (input.empty())
>> return wxEmptyString;
>> if (!conv)
>> conv = wxConvCurrent;
>> return wxString(input.c_str(), *conv);
>> }
>

Hi Borr
For your interest there are also built in functions in wxWidgets in 2.9 but 
I have not looked at 2.8 or earlier:
wxString::ToStdString()
wxString::ToStdWstring()
and
wxString::wxString (const std::string &str)
wxString::wxString (const std::wstring &str)

Cheers, John

On 2010-07-20 19:48, John Roberts wrote:
> ----- Original Message -----
> From: "Daniel Albuschat"<d.albuschat@...>
> To:<ibpp-discuss@...>
> Sent: Tuesday, July 20, 2010 2:59 PM
> Subject: Re: [IBPP-DISCUSS] Compile IBPP in wxWidgets project
>
>
>    
>> 2010/7/20 John Roberts<johnr@...>:
>> [snip]
>>      
>>> Thanks for your reply Boris. However, I am not dealing with wxString here
>>> and don't understand how wx2std() or std2wx() will help convert parameter
>>> 1
>>> from 'const char *' to 'LPCWSTR' where it is found in ibpp code.
>>> eg
>>> path.append("fbclient.dll");
>>> mHandle = LoadLibrary(path.c_str());
>>> gives compiler error
>>> \ibpp\_ibpp.cpp(142) : error C2664: 'LoadLibraryW' : cannot convert
>>> parameter 1 from 'const char *' to 'LPCWSTR'
>>>
>>> Cheers, John
>>>        
>> Hi John,
>>
>> IBPP can (still) not be compiled with UNICODE set. There are a few
>> minor changes that have to be made. You can, for example, change to
>> call to LoadLibrary() to LoadLibraryA().
>>
>> Greetings,
>>
>> Daniel Albuschat
>>      
> Thanks Daniel. I thought that might be the case.
> To stay with UNICODE I have used casts through the IBPP code as per examples
> below:
>
> mHandle = LoadLibrary((LPCWSTR)("gds32.dll"));
> mHandle = LoadLibrary((LPWSTR)fbdll);
>
> It compiles and runs now with the limited testing I have done so far. If I
> continue to use it I will use svn to maintain my changes if they are
> appropriate.
> Cheers, John
>    
No, you don't want to do this, not only will LoadLibraryW (called when 
UNICODE is defined) not understand what you passed it, but it will no 
longer compile when LoadLibraryA is called when UNICODE is not defined. 
Explicitly calling LoadLibraryA() is the best option here unless you 
want to switch IBPP to using some definition that is either wchar_t or 
char depending on platform so you can use unicode paths.

----- Original Message ----- 
From: "Simon Buchan" <simon@...>
To: <ibpp-discuss@...>
Sent: Monday, August 02, 2010 6:20 AM
Subject: Re: [IBPP-DISCUSS] Compile IBPP in wxWidgets project


> On 2010-07-20 19:48, John Roberts wrote:
>> ----- Original Message -----
>> From: "Daniel Albuschat"<d.albuschat@...>
>> To:<ibpp-discuss@...>
>> Sent: Tuesday, July 20, 2010 2:59 PM
>> Subject: Re: [IBPP-DISCUSS] Compile IBPP in wxWidgets project
>>
>>
>>
>>> 2010/7/20 John Roberts<johnr@...>:
>>> [snip]
>>>
>>>> Thanks for your reply Boris. However, I am not dealing with wxString 
>>>> here
>>>> and don't understand how wx2std() or std2wx() will help convert 
>>>> parameter
>>>> 1
>>>> from 'const char *' to 'LPCWSTR' where it is found in ibpp code.
>>>> eg
>>>> path.append("fbclient.dll");
>>>> mHandle = LoadLibrary(path.c_str());
>>>> gives compiler error
>>>> \ibpp\_ibpp.cpp(142) : error C2664: 'LoadLibraryW' : cannot convert
>>>> parameter 1 from 'const char *' to 'LPCWSTR'
>>>>
>>>> Cheers, John
>>>>
>>> Hi John,
>>>
>>> IBPP can (still) not be compiled with UNICODE set. There are a few
>>> minor changes that have to be made. You can, for example, change to
>>> call to LoadLibrary() to LoadLibraryA().
>>>
>>> Greetings,
>>>
>>> Daniel Albuschat
>>>
>> Thanks Daniel. I thought that might be the case.
>> To stay with UNICODE I have used casts through the IBPP code as per 
>> examples
>> below:
>>
>> mHandle = LoadLibrary((LPCWSTR)("gds32.dll"));
>> mHandle = LoadLibrary((LPWSTR)fbdll);
>>
>> It compiles and runs now with the limited testing I have done so far. If 
>> I
>> continue to use it I will use svn to maintain my changes if they are
>> appropriate.
>> Cheers, John
>>
> No, you don't want to do this, not only will LoadLibraryW (called when
> UNICODE is defined) not understand what you passed it, but it will no
> longer compile when LoadLibraryA is called when UNICODE is not defined.
> Explicitly calling LoadLibraryA() is the best option here unless you
> want to switch IBPP to using some definition that is either wchar_t or
> char depending on platform so you can use unicode paths.

Yes I figured that out and the latter approach is what I ended up doing.
Thanks for your help, John