Developer forums (C::B DEVELOPMENT STRICTLY!) > Contributions to C::B

WIN98/9x/others build : registry settings test

<< < (5/8) > >>

killerbot:
now we need to convince Thomas and Yiannis ;-)

would be nice to have one uild that serves all windows (no no not 3.11)

takeshimiya:
Well, first make an Unicode build linked with unicows, so a few users of Win9x can test it. :)

Be sure to check that your setup.h haves wxUSE_UNICODE_MSLU = 1.

--- Quote ---Hello,

version 0.5 of libunicows, a compiler-independent open source
implementation of MSLU import library, was released and is available
for download from http://libunicows.sourceforge.net. Precompiled
binaries for Visual C++ and Mingw32 are included (help with other
compilers is wanted).

MSLU (The Microsoft Layer for Unicode on Windows 95/98/ME Systems) is
a compatibility layer that makes it possible to run Unicode
applications on Windows 9x systems (previously, Unicode APIs were
only available on Windows NT/2000; see
http://www.microsoft.com/globaldev/Articles/mslu_announce.asp for
details). Necessary runtime DLLs can be downloaded from
http://www.microsoft.com/downloads/release.asp?releaseid=30039

MSLU requires that you use a special statically-linked import library
that is currently only provided for Microsoft Visual C++ and only as
a part of the (rather large) new Platform SDK. Libunicows addresses
both of these problems by being small and available in source code
form.

wxWindows 2.3 contains MSLU support and works with libunicows (VC++
makefile and configure-generated makefile for Mingw32 can both use
it). Libunicows is used in two wxWindows projects: poEdit
(http://poedit.sf.net) and Unicode build of wxPython
(http://wxpython.org).

Best regards,
Vaclav Slavik
--- End quote ---

duncanka:

--- Quote from: Takeshi Miya on January 11, 2006, 07:31:05 pm ---Well, first make an Unicode build linked with unicows, so a few users of Win9x can test it. :)

Be sure to check that your setup.h haves wxUSE_UNICODE_MSLU = 1.

--- End quote ---
I just tried this for myself, building from the latest SVN (1804), and it was kind of a disaster.  I built wxWidgets the usual way, with the exception that I enabled MSLU support, and linked CB against it.  When I ran the program, it did load up properly (though for some reason, I had to specify the program's own directory using the --prefix option for this to work).  But the program I got was very crippled.  For one thing, I cannot see the editor.  It just doesn't appear when I open a file, even though the title bar and the status bar both indicate an open file.  Additionally, dragging a dockable pane invariably results in an immediate crash.  A stack trace always reveals Opencow.dll at the end of the trace, or Unicows.dll if I use the Microsoft implementation, though I have no idea if this means MSLU is at fault.
(I've attached a copy of Dr. Mingw's error report from the wxAUI pane-dragging crash.)
Where did I go wrong??!  :( :?  Help, anyone??

[attachment deleted by admin]

takeshimiya:
On what OS are you testing?

mandrav:

--- Quote ---But the program I got was very crippled.  For one thing, I cannot see the editor.  It just doesn't appear when I open a file, even though the title bar and the status bar both indicate an open file.  Additionally, dragging a dockable pane invariably results in an immediate crash.
--- End quote ---

Whenever you see layout-related errors, try deleting your active layout (or switch to another one if you have).
"View->Layouts->Delete current".

Navigation

[0] Message Index

[#] Next page

[*] Previous page