On 22/02/2010 23:17, Vincent van Ravesteijn wrote:
Compiling with: "/Zc:wchar_t-" solves it for me.
In MSVC this is called "Treat wchar_t as Built-in Type : No". This is
by default set to Yes.
Can this be changed in the Scons and CMake scripts ?
I did that in cmake.
Abdel.
On Tue, Feb 23, 2010 at 01:28:44AM +0100, Vincent van Ravesteijn wrote:
> Enrico Forestieri schreef:
>> On Tue, Feb 23, 2010 at 12:59:41AM +0100, Vincent van Ravesteijn wrote:
>>
>>> Enrico Forestieri schreef:
>>>
On Mon, Feb 22, 2010 at 11:17:02PM +0100, Vincent van Ravesteijn wrote:
Enrico Forestieri schreef:
On Tue, Feb 23, 2010 at 12:59:41AM +0100, Vincent van Ravesteijn wrote:
Enrico Forestieri schreef:
On Mon, Feb 22, 2010 at 11:17:02PM +0100, Vincent van Ravesteijn wrote:
Compiling with: "/Zc:wchar_t-" solves it for me.
In MSVC this is called "Trea
On Tue, Feb 23, 2010 at 12:59:41AM +0100, Vincent van Ravesteijn wrote:
> Enrico Forestieri schreef:
>> On Mon, Feb 22, 2010 at 11:17:02PM +0100, Vincent van Ravesteijn wrote:
>>
>>> Compiling with: "/Zc:wchar_t-" solves it for me.
>>>
>>> In MSVC this is called "Treat wchar_t as Built-in Type :
Enrico Forestieri schreef:
On Mon, Feb 22, 2010 at 11:17:02PM +0100, Vincent van Ravesteijn wrote:
Compiling with: "/Zc:wchar_t-" solves it for me.
In MSVC this is called "Treat wchar_t as Built-in Type : No". This is by
default set to Yes.
D'oh! And does it work without that option
On Mon, Feb 22, 2010 at 11:17:02PM +0100, Vincent van Ravesteijn wrote:
> Compiling with: "/Zc:wchar_t-" solves it for me.
>
> In MSVC this is called "Treat wchar_t as Built-in Type : No". This is by
> default set to Yes.
D'oh! And does it work without that option if you replace "wchar_t *"
with
No, Qt uses the wchar_t of the platform for the to/fromWChar functions
to communicate with wchar_t based functions of the host system. On
Windows that's a 16 bit type, on *nix traditionally 32 bit.
QString is internally UTF-16 on all platforms.
So what do you propose? LyX is currently uncompil
Am 22.02.2010 20:55, schrieb Andre Poenitz:
"class QString QString::fromWCharArray(unsigned short const *,int)"
So, qt defines/typedefs wchar_t as unsigned short ??
No, that's not Qt, but Windows, in msvcrt.h if memory serves right.
But Qt has only a short one defined ?
No, Qt uses the wc
Compiling with: "/Zc:wchar_t-" solves it for me.
In MSVC this is called "Treat wchar_t as Built-in Type : No". This is by
default set to Yes.
Can this be changed in the Scons and CMake scripts ?
Vincent
On Mon, Feb 22, 2010 at 08:07:56PM +0100, Vincent van Ravesteijn - TNW wrote:
> Depends.exe says:
>
> "class QString QString::fromWCharArray(unsigned short const *,int)"
>
> So, qt defines/typedefs wchar_t as unsigned short ??
No, that's not Qt, but Windows, in msvcrt.h if memory serves right.
> >class Q_CORE_EXPORT QString
> >{
> >...
> >static QString fromWCharArray(const wchar_t *, int size = -1);
> >...
> >}
> >
>The function is new in 4.2, so one possibility is that you compile
against
>4.2 headers but link against 4.1 libraries.
No, that's not the problem.
>Export mig
On Mon, Feb 22, 2010 at 01:50:09PM +0100, Vincent van Ravesteijn - TNW wrote:
>
> >> No.
> >> The above error message states that
> >> QString::fromWCharArray(wchar_t const *,int) is the problem.
> >> I don't understand the error message but it seems that fromWCharArray
>
> >> needs to be linked
On Mon, Feb 22, 2010 at 04:35:00PM +0100, Uwe Stöhr wrote:
> Vincent van Ravesteijn - TNW schrieb:
>
>>> Vincent, Enrico, what Qt version are you using?
>>> (I can try to switch to Qt 4.6.2 and try again.)
>>
>> 4.7.
>
> The development version of Qt? OK, then upgrading to 4.6.2 wouldn't fix
> th
Vincent van Ravesteijn - TNW schrieb:
Vincent, Enrico, what Qt version are you using?
(I can try to switch to Qt 4.6.2 and try again.)
4.7.
The development version of Qt? OK, then upgrading to 4.6.2 wouldn't fix
this issue.
Perhaps the problem is a bug in the Qt sources - André, can you p
On Mon, Feb 22, 2010 at 03:58:26PM +0100, Vincent van Ravesteijn - TNW wrote:
>
> >> >class Q_CORE_EXPORT QString
> >> >{
> >> >...
> >> >static QString fromWCharArray(const wchar_t *, int size = -1);
> >> >...
> >> >}
> >> >
> >> >so, I really don't understand why you get the error. A
>> >class Q_CORE_EXPORT QString
>> >{
>> >...
>> >static QString fromWCharArray(const wchar_t *, int size = -1);
>> >...
>> >}
>> >
>> >so, I really don't understand why you get the error. Are you sure
you
>> are
>> >linking the QtCore library?
>> >
>>
>> I see the same, and I don't k
On Mon, Feb 22, 2010 at 01:50:09PM +0100, Vincent van Ravesteijn - TNW wrote:
>
> >> No.
> >> The above error message states that
> >> QString::fromWCharArray(wchar_t const *,int) is the problem.
> >> I don't understand the error message but it seems that fromWCharArray
>
> >> needs to be linked
>> I see the same, and I don't know what the problem is either. The >
QString header can be found, Qstring can be used, just not this static
> function. Maybe it is not exported or something..
>Glad to hear that I'm not the only one having this problem. I'm using
Qt 4.5.3. Vincent, Enrico, what Q
> I see the same, and I don't know what the problem is either. The
> QString header can be found, Qstring can be used, just not this static
> function. Maybe it is not exported or something..
Glad to hear that I'm not the only one having this problem. I'm using Qt
4.5.3. Vincent, Enrico, what Qt
>> No.
>> The above error message states that
>> QString::fromWCharArray(wchar_t const *,int) is the problem.
>> I don't understand the error message but it seems that fromWCharArray
>> needs to be linked via a header file.
>
>That header file is , which is already included. There, you
can
>find
On Mon, Feb 22, 2010 at 02:33:34AM +0100, Uwe Stöhr wrote:
> Am 21.02.2010 19:41, schrieb Enrico Forestieri:
>
This breaks the compilation. I now get this error:
Creating library release\lyx.lib and object release\lyx.exp
support.lib(os.obj) : error LNK2019: unresolved external
Am 21.02.2010 19:41, schrieb Enrico Forestieri:
This breaks the compilation. I now get this error:
Creating library release\lyx.lib and object release\lyx.exp
support.lib(os.obj) : error LNK2019: unresolved external symbol
"__declspec(dllimport) public: static class QString __cdecl
QString::fro
On Sun, Feb 21, 2010 at 03:07:57PM +0100, Enrico Forestieri wrote:
> On Sun, Feb 21, 2010 at 02:27:49PM +0100, Uwe Stöhr wrote:
>
> > Am 21.02.2010 05:59, schrieb LyX Ticket Tracker:
> >
> > >#5238: LyX 1.6 fails with non-ascii chars in path (on Windows)
> >
On Sun, Feb 21, 2010 at 02:27:49PM +0100, Uwe Stöhr wrote:
> Am 21.02.2010 05:59, schrieb LyX Ticket Tracker:
>
> >#5238: LyX 1.6 fails with non-ascii chars in path (on Windows)
> >
> > Fixed in trunk at r33524.
>
> This breaks the compilation. I now get thi
Am 21.02.2010 05:59, schrieb LyX Ticket Tracker:
#5238: LyX 1.6 fails with non-ascii chars in path (on Windows)
Fixed in trunk at r33524.
This breaks the compilation. I now get this error:
Creating library release\lyx.lib and object release\lyx.exp support.lib(os.obj) : error LNK2019
25 matches
Mail list logo
