From: Eric Y. K. <Eri...@lo...> - 2005-08-03 12:30:37
Attachments:
wxhaskell-unicode.patch
|
Hi list, I have been working on getting Unicode support to work in wxhaskell. Progress so far is that the Minimal.hs example runs, but the Control.hs example segfaults. Would anybody be interested in working with me on this? We could conceivably create a darcs repository or something. I attach the patch (-p1) that brings us up to the current state. Note: on Tiger, you have to do gcc_select 3.3 for things to work properly. -- Eric Kow http://www.loria.fr/~kow PGP Key ID: 08AC04F9 Merci de corriger mon français. |
From: Eric Y. K. <Eri...@lo...> - 2005-08-03 16:36:19
Attachments:
wxhaskell-unicode.patch.gz
|
Hi again list, Here is a revised patch for wxhaskell in unicode. Please disregard the previous message. (moderator: if you see this, please kill the first message). I have finally gotten wxhaskell working with Unicode. You can see a screenshot of a sample application here: http://photos1.blogger.com/blogger/5532/1215/1600/unicode_wxhaskell.jpg Please try the following patch (-p1) out. Notes: 1. You'll need to compile wxWidgets with --enable-unicode (or at least, without --disable-unicode?) 2. On MacOS X Tiger, I need to gcc_select 3.3 for it not to give weird errors. Not yet tested on other operating systems. 3. I don't actually know anything about programming in C, using the FFI, or that much about wxWidgets either, so buyer beware -- Eric Kow http://www.loria.fr/~kow PGP Key ID: 08AC04F9 Merci de corriger mon français. |
From: Eric Y. K. <Eri...@lo...> - 2005-09-09 15:37:05
Attachments:
unicode-03.patch
|
Dear list, Attached is the latest version of my wxhaskell Unicode patch. Compared to previous patches, it has fewer memcpy errors. I have tested it against the latest CVS code, and it seems to work. Cheers, -- Eric Kow http://www.loria.fr/~kow PGP Key ID: 08AC04F9 Merci de corriger mon français. |
From: Eric Y. K. <Eri...@lo...> - 2005-09-12 18:14:53
Attachments:
patch-wxhaskell-unicode-04.gz
|
Hi again, Attached is the next version (04) of the patch. It fixes compile issues on Linux. Now the Unicode patch has been tested and seems to work on both Mac and Linux. Could somebody give it a try on Windows? (Note: this patch was motivated by attempts to compile wxhaskell on OS X Tiger, which includes WxWidgets, but with --enable-unicode) -- Eric Kow http://www.loria.fr/~kow PGP Key ID: 08AC04F9 Merci de corriger mon français. |
From: shelarcy <she...@ca...> - 2005-09-24 18:52:36
|
On Tue, 13 Sep 2005 03:05:48 +0900, Eric Y. Kow <Eri...@lo...> wrote= : > Hi again, > > Attached is the next version (04) of the patch. It fixes compile issue= s > on Linux. > > Now the Unicode patch has been tested and seems to work on both > Mac and Linux. Hi, Eric. I tested to build wxfuit's paddle sample on Mac OS X Tiger with GHC-6.4.1= . paddle sample doesn't works well, it notices error messegage and display wrong picture - background color is black and objects are rendered only frame -, slide bar's top and bottom are reversed. Attached is Yampa (afrp-0.4-src.tgz) and wxfruit patch for ghc-6.4.x with wxhaskell-0.9.x, so you can test soonly, I don't test to use make, so I also attach cabal files. * wxFruit http://zoo.cs.yale.edu/classes/cs490/03-04b/bartholomew.robinson/ > Could somebody give it a try on Windows? > > (Note: this patch was motivated by attempts to compile wxhaskell on > OS X Tiger, which includes WxWidgets, but with --enable-unicode) > --=20 shelarcy <shelarcy capella.freemail.ne.jp> http://page.freett.com/shelarcy/ |
From: Eric Y. K. <Eri...@lo...> - 2005-10-04 11:31:04
|
Hi, On Sun, Sep 25, 2005 at 03:51:50 +0900, shelarcy wrote: > I tested to build wxfuit's paddle sample on Mac OS X Tiger with GHC-6.4.1. > paddle sample doesn't works well, it notices error messegage and > display wrong picture - background color is black and objects are > rendered only frame -, slide bar's top and bottom are reversed. I have taken a look at wxFruit with wxhaskell. Without the Unicode patch, I get mostly the same symptoms: http://www.loria.fr/~kow/tmp/paddle-macos-notunicode.png The only thing is that I don't get the dynamic events warning, but=20 this is because I used wxWidgets 2.6.1. In either case, it seems the problem is not related to Unicode stuff, but to something else in wxWidgets. P.S: In case it gets released, please disregard my call for testing wxFruit --=20 Eric Kow http://www.loria.fr/~kow PGP Key ID: 08AC04F9 Merci de corriger mon fran=E7ais. |
From: shelarcy <she...@ca...> - 2005-09-24 17:46:57
Attachments:
wxfruit.diff
afrp.diff-complete
|
On Tue, 13 Sep 2005 03:05:48 +0900, Eric Y. Kow <Eri...@lo...> wrote= : > Hi again, > > Attached is the next version (04) of the patch. It fixes compile issue= s > on Linux. > > Now the Unicode patch has been tested and seems to work on both > Mac and Linux. Hi, Eric. I tested to build wxfuit's paddle sample on Mac OS X Tiger with GHC-6.4.1= . paddle sample doesn't works well, it notices error messegage and display wrong picture - background color is black and objects are rendered only frame -, slide bar's top and bottom are reversed. Attached is Yampa (afrp-0.4-src.tgz) and wxfruit patch for ghc-6.4.x and wxhaskell-0.9.x, so you can test soonly, * wxFruit http://zoo.cs.yale.edu/classes/cs490/03-04b/bartholomew.robinson/ > Could somebody give it a try on Windows? > > (Note: this patch was motivated by attempts to compile wxhaskell on > OS X Tiger, which includes WxWidgets, but with --enable-unicode) > --=20 shelarcy <shelarcy capella.freemail.ne.jp> http://page.freett.com/shelarcy/ |
From: shelarcy <she...@ca...> - 2005-09-26 14:34:54
|
On Mon, 26 Sep 2005 19:24:49 +0900, Eric Y. Kow <Eri...@lo...> wrote= : > One thing I did not mention is that there are some problems with dynami= c > events and the 2.5.3 version of wxWidgets, so this might be related. > > Also, if you are interested, I am working on a DarwinPort for wxhaskell > (http://bugzilla.opendarwin.org/show_bug.cgi?id=3D5006) > > Only the gcc 3.3 version seems to work for now. The 4.0 version, being > linked to wxWidgets 2.6.1, might conceivably work better, but I am > having trouble making it compile. So if you have some free time to pla= y > around with this, i'd be curious to see if you have any luck compiling > wxhaskell with gcc 4.0. I use gcc 3.3 now, because wxHaskell with wxWidgets 2.5.3 can't be built by gcc 4.0. Hmm, wxWidgets 2.6.1, I'm worrying this point - wxhaskell site says: > MacOS X works best with wxWidgets 2.5.4. The latest stable release > (currently wxMAC-2.6.0) does not display menus properly. wxWidgets 2.6.1 or latest wxWidgets 2.6.2 (or enable unicode option) don't exist this problem, or you fixed that? --=20 shelarcy <shelarcy capella.freemail.ne.jp> http://page.freett.com/shelarcy/ |
From: Eric Y. K. <Eri...@lo...> - 2005-09-28 12:44:30
|
On Mon, Sep 26, 2005 at 23:34:27 +0900, shelarcy wrote: > >MacOS X works best with wxWidgets 2.5.4. The latest stable release > >(currently wxMAC-2.6.0) does not display menus properly. >=20 > wxWidgets 2.6.1 or latest wxWidgets 2.6.2 (or enable unicode option) > don't exist this problem, or you fixed that? To be honest, i don't know if the problem is still there, as I myself have not been able to make it work yet. Best, --=20 Eric Kow http://www.loria.fr/~kow PGP Key ID: 08AC04F9 Merci de corriger mon fran=E7ais. |
From: Eric Y. K. <Eri...@lo...> - 2005-10-03 16:01:25
|
Hi list, We need some help testing something out. I would like to know what the following sample application looks like under Linux and Mac OS X without my unicode patch. Could some Mac or Linux users please compile the following sample app and send us a screenshot along with any error messages? I would like to see if the errors are from my Unicode patch or something unrelated. Below are the steps to take and the symptoms we get so you can compare notes. Many thanks! Steps to take ------------- Requirements: GHC 6.4 (else let us know) wxWidgets 2.5 or 2.6.1 (let us know what version) wxhaskell 0.9.4 (vanilla, no unicode patch) Get: Yampa Core: http://www.haskell.org/yampa/afrp-0.4-src.tgz WxFruit: http://zoo.cs.yale.edu/classes/cs490/03-04b/bartholomew.robinson/wxfruit-0.1.tar.gz afrp patch (attached) wxfruit patch (attached) Install AFRP: tar xzf afrp-0.4-src.tgz cd afrp-0.4 patch -p1 < ../afrp-complete.diff runhaskell Setup.hs configure runhaskell Setup.hs build sudo runhaskell Setup.hs install sudo ranlib /usr/local/lib/afrp-0.4/libHSafrp-0.4.a cd .. Compile wxFruit: tar xzf wxfruit-0.1.tgz cd wxfruit-0.1 patch -p1 < ../wxfruit.diff ghc --make -package afrp -farrows paddle.hs # if on mac macosx-app a.out Run it: ./a.out Report errors and send a screen capture Notes: (these are the same patches as shelarcy's) Symptoms Mac (paddle-osx.png attached) ------------ On MacOS X 10.4, I get wxWidgets Debug Alert ../src/common/event.cpp(1327): assert "wxAssertFailure" failed: caller should check that we have dynamic events Do you want to stop the program? You can also choose [Cancel] to suppress further warnings. And after selecting "No", i get the symptoms Shelarchy described (black backgrounds, outline only being displayed), but otherwise things worked. (ghc 6.4.1, wxWidgets 2.5.3 (system), wxhaskell-0.9.4 unicode) Symptoms Linux (paddle-linux.png attached) -------------- On Linux, things seem to work better, but the speed selector seems neither to display correctly, nor work. (ghc 6.4, wxWidgets 2.6.1, wxhaskell-0.9.4 unicode) -- Eric Kow http://www.loria.fr/~kow PGP Key ID: 08AC04F9 Merci de corriger mon français. |
From: Eric Y. K. <Eri...@lo...> - 2005-10-11 12:01:08
|
On Mon, Oct 03, 2005 at 18:01:07 +0200, Eric Y. Kow wrote: > We need some help testing something out. Please feel free to disregard this message. I've managed to test things out on my own. -- Eric Kow http://www.loria.fr/~kow PGP Key ID: 08AC04F9 Merci de corriger mon français. |
From: shelarcy <she...@ca...> - 2005-11-09 18:00:05
Attachments:
wxcu-2.6.2.dsw
wxcu-2.6.2.dsp
|
Previous mail's added file is too big, and I added that by misunderstood problem. So I send this mail instead of previous mail. On Tue, 13 Sep 2005 03:05:48 +0900, Eric Y. Kow <Eri...@lo...> wrote= : > Attached is the next version (04) of the patch. It fixes compile issue= s > on Linux. > > Now the Unicode patch has been tested and seems to work on both > Mac and Linux. > > Could somebody give it a try on Windows? I am Windows and Visual C++ User. But I have only Japanese Edition that report error message in Japanese, so I didn't notice that. Now, Microsoft provied Visual C++ 2005 Express Edition (VC8) freely an month in Web, VC8 can use with Platform SDK, and VC8 has optimised =20 compiler - so I tested and report today for 05 version patch. http://msdn.microsoft.com/vstudio/express/visualc/usingpsdk/ VC reports this error: Linking... wxmswu.lib(string.obj) : error LNK2005: "public: __thiscall wxString::wxString(char const *,class wxMBConv &,unsigned int)" (??0wxString@@QAE@PBDAAVwxMBConv@@I@Z) already defined in apppath.obj Creating library .\..\out\wxc/wxc-msw2.4.2-0.9.4.lib and object .\..\out\wxc/wxc-msw2.4.2-0.9.4.exp and reports also unresolved external symbol. I think these come from wxString::String's error. eljwindow.obj : error LNK2001: unresolved external symbol "char const * const wxEmptyString" (?wxEmptyString@@3PBDB) eljwizard.obj : error LNK2001: unresolved external symbol "char const * const wxEmptyString" (?wxEmptyString@@3PBDB) eljtextctrl.obj : error LNK2001: unresolved external symbol "char const * const wxEmptyString" (?wxEmptyString@@3PBDB) eljtglbtn.obj : error LNK2001: unresolved external symbol "char const * const wxEmptyString" (?wxEmptyString@@3PBDB) ...... eljwizard.obj : error LNK2001: unresolved external symbol "protected: voi= d __thiscall wxStringBase::InitWith(char const *,unsigned int,unsigned int)= " (?InitWith@wxStringBase@@IAEXPBDII@Z) eljtglbtn.obj : error LNK2001: unresolved external symbol "protected: voi= d __thiscall wxStringBase::InitWith(char const *,unsigned int,unsigned int)= " (?InitWith@wxStringBase@@IAEXPBDII@Z) eljtipwnd.obj : error LNK2001: unresolved external symbol "protected: voi= d __thiscall wxStringBase::InitWith(char const *,unsigned int,unsigned int)= " (?InitWith@wxStringBase@@IAEXPBDII@Z) ...... .\out\wxc\wxc-msw2.4.2-0.9.4.dll : fatal error LNK1120: 61 unresolved =20 externals --=20 shelarcy <shelarcy capella.freemail.ne.jp> http://page.freett.com/shelarcy/ |
From: Eric Y. K. <Eri...@lo...> - 2005-11-10 15:16:19
|
Hi there, To be honest, I have no idea how things work on Windows, so bear with me :-) =20 I assume you are following the instructions on this page: http://wxhaskell.sourceforge.net/building-msc.html You seem to be including wxWidgets 2.6.2 headers but linking against 2.4.2 library. Is this the case, or am I misreading things? Anyone else have ideas? Thanks for trying it out! --eric On Thu, Nov 10, 2005 at 02:59:56 +0900, shelarcy wrote: > VC reports this error: >=20 > Linking... > wxmswu.lib(string.obj) : error LNK2005: "public: __thiscall > wxString::wxString(char const *,class wxMBConv &,unsigned int)" > (??0wxString@@QAE@PBDAAVwxMBConv@@I@Z) already defined in apppath.obj > Creating library .\..\out\wxc/wxc-msw2.4.2-0.9.4.lib and object > .\..\out\wxc/wxc-msw2.4.2-0.9.4.exp >=20 > and reports also unresolved external symbol. I think these come > from wxString::String's error. >=20 > eljwindow.obj : error LNK2001: unresolved external symbol "char const * > const wxEmptyString" (?wxEmptyString@@3PBDB) --=20 Eric Kow http://www.loria.fr/~kow PGP Key ID: 08AC04F9 Merci de corriger mon fran=E7ais. |
From: shelarcy <she...@ca...> - 2005-11-10 16:46:54
|
On Thu, 10 Nov 2005 21:49:48 +0900, Eric Y. Kow <Eri...@lo...> wrote= : > I assume you are following the instructions on this page: > http://wxhaskell.sourceforge.net/building-msc.html > > You seem to be including wxWidgets 2.6.2 headers but linking against > 2.4.2 library. Is this the case, or am I misreading things? Building with msc (VC) require wxc-msw2.4.2-0.9.4 library now, so VC generate wxc-msw2.4.2-0.9.4 library by all version. See VC project files - VC project files are plain text. > On Thu, Nov 10, 2005 at 02:59:56 +0900, shelarcy wrote: >> VC reports this error: >> >> Linking... >> wxmswu.lib(string.obj) : error LNK2005: "public: __thiscall >> wxString::wxString(char const *,class wxMBConv &,unsigned int)" >> (??0wxString@@QAE@PBDAAVwxMBConv@@I@Z) already defined in apppath.obj >> Creating library .\..\out\wxc/wxc-msw2.4.2-0.9.4.lib and object >> .\..\out\wxc/wxc-msw2.4.2-0.9.4.exp >> >> and reports also unresolved external symbol. I think these come >> from wxString::String's error. >> >> eljwindow.obj : error LNK2001: unresolved external symbol "char const = * >> const wxEmptyString" (?wxEmptyString@@3PBDB) > --=20 shelarcy <shelarcy capella.freemail.ne.jp> http://page.freett.com/shelarcy/ |
From: Eric Y. K. <Eri...@lo...> - 2005-11-10 18:59:06
|
I see; it's just wxc being named 2.4.2 no matter what wxWidgets it is based on. Also, I hadn't realised that there were .dsw and .dsp files in the wxc directory that you had based this on. Hmm... well, I'll look into it, but without a Windows machine to play around with, i'm pretty lost on this one But just to clarify :=20 1. It compiles fine, but does not link properly? 2. Do you have cygwin? Would you be willing to try the cygwin build and see if it's any easier? On Fri, Nov 11, 2005 at 01:46:41 +0900, shelarcy wrote: > Building with msc (VC) require wxc-msw2.4.2-0.9.4 library now, so > VC generate wxc-msw2.4.2-0.9.4 library by all version. >=20 > See VC project files - VC project files are plain text. >=20 >=20 > >On Thu, Nov 10, 2005 at 02:59:56 +0900, shelarcy wrote: > >>VC reports this error: > >> > >>Linking... > >>wxmswu.lib(string.obj) : error LNK2005: "public: __thiscall > >>wxString::wxString(char const *,class wxMBConv &,unsigned int)" > >>(??0wxString@@QAE@PBDAAVwxMBConv@@I@Z) already defined in apppath.obj > >> Creating library .\..\out\wxc/wxc-msw2.4.2-0.9.4.lib and object > >>.\..\out\wxc/wxc-msw2.4.2-0.9.4.exp --=20 Eric Kow http://www.loria.fr/~kow PGP Key ID: 08AC04F9 Merci de corriger mon fran=E7ais. |
From: shelarcy <she...@ca...> - 2005-11-28 14:36:04
Attachments:
patch-unicode-05-to-windows-support.diff
|
I found where is the problem, On wxMsc, wx/setup.h define wxUSE_UNICODE=3D0 in default - because Windows 98 can't use unicode build - so, I should define wxUSE_UNICODE=3D= 1 in project files. I tried to build with wxUSE_UNICODE=3D1, I found char problem by Visual C= ++ 2005 compiler, so I also change wxChar instead of char and wxT("foo") instead of "", then I can build with Unicode version. I send Windows patch for your Unicode patch. Some problem is exist now... but this is not Unicode versions problem. Because, this problem is also exist on not unicode version. And I have good news. using this patch's project file, ghc-6.4.1 with wxWidgets-2.6.2 version can use ghci, too. (This problem came from, Daan doesn't synch higher wxWidgets-2.5.X's project file.) On Fri, 11 Nov 2005 03:58:55 +0900, Eric Y. Kow <Eri...@lo...> wrote= : > I see; it's just wxc being named 2.4.2 no matter what wxWidgets it is > based on. Also, I hadn't realised that there were .dsw and .dsp files > in the wxc directory that you had based this on. > > Hmm... well, I'll look into it, but without a Windows machine to play > around with, i'm pretty lost on this one > > But just to clarify : > 1. It compiles fine, but does not link properly? > 2. Do you have cygwin? Would you be willing to try the cygwin > build and see if it's any easier? Cygwin version has more problems.... http://sourceforge.net/mailarchive/message.php?msg_id=3D11715526 --=20 shelarcy <shelarcy capella.freemail.ne.jp> http://page.freett.com/shelarcy/ |
From: Eric Y. K. <Eri...@lo...> - 2005-11-30 11:37:23
Attachments:
patch-wxhaskell-unicode-07.gz
|
Hi, That's great news, thanks very much. I have tested your patches under Linux and Mac and (as would be expected) they also seem to work. Attached is the latest version (07) of the unicode patch with shelarchy's changes merged in. For further reference, I have opened a new item on the sf tracker which should help the wxhaskell developers to follow the development of this patch: http://sourceforge.net/tracker/index.php?func=detail&aid=1369929&group_id=73133&atid=536847 On Mon, Nov 28, 2005 at 23:35:56 +0900, shelarcy wrote: > I found where is the problem, > > I send Windows patch for your Unicode patch. -- Eric Kow http://www.loria.fr/~kow PGP Key ID: 08AC04F9 Merci de corriger mon français. |
From: Eric Y. K. <Eri...@lo...> - 2005-11-30 11:49:44
|
(Sorry in advance for double-posting; my first message had hit the size limit [attachment] and is being held by the moderator) That's great news, thanks very much. I have tested your patches under Linux and Mac and (as would be expected) they also seem to work. =20 For further reference, I have opened a new item on the sf tracker which should help the wxhaskell developers to follow the development of this patch: http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1369929&grou= p_id=3D73133&atid=3D536847 You can also download the patch here: http://www.loria.fr/~kow/download/patch-wxhaskell-unicode-07 On Mon, Nov 28, 2005 at 23:35:56 +0900, shelarcy wrote: > I found where is the problem, >=20 > I send Windows patch for your Unicode patch. --=20 Eric Kow http://www.loria.fr/~kow PGP Key ID: 08AC04F9 Merci de corriger mon fran=E7ais. --=20 Eric Kow http://www.loria.fr/~kow PGP Key ID: 08AC04F9 Merci de corriger mon fran=E7ais. |
From: shelarcy <she...@ca...> - 2005-11-30 13:59:20
|
On Wed, 30 Nov 2005 20:49:32 +0900, Eric Y. Kow <Eri...@lo...> wrote= : > That's great news, thanks very much. I have tested your patches under > Linux and Mac and (as would be expected) they also seem to work. > > You can also download the patch here: > http://www.loria.fr/~kow/download/patch-wxhaskell-unicode-07 Hmm... you forgot two point in your newer patch. One is eljbitmap.cpp must also chage three lines for Windows, like this. --- wxhaskell-0.9.4.orig/wxc/src/ewxw/eljbitmap.cpp Wed Nov 30 21:57:14 =20 2005 +++ wxhaskell-0.9.4/wxc/src/ewxw/eljbitmap.cpp Wed Nov 30 21:44:19 2005 @@ -92,7 +92,7 @@ EWXWEXPORT(int, wxBitmap_RemoveHandler)(void* name) { #ifdef __WIN32__ - return (int) wxBitmap::RemoveHandler((char*) name); + return (int) wxBitmap::RemoveHandler((wxChar*) name); #else return 0; #endif @@ -101,7 +101,7 @@ EWXWEXPORT(void*, wxBitmap_FindHandlerByName)(void* name) { #ifdef __WIN32__ - return (void*)wxBitmap::FindHandler((char*) name); + return (void*)wxBitmap::FindHandler((wxChar*) name); #else return NULL; #endif @@ -110,7 +110,7 @@ EWXWEXPORT(void*, wxBitmap_FindHandlerByExtension)(void* extension, int= =20 type) { #ifdef __WIN32__ - return (void*)wxBitmap::FindHandler((char*)extension, (long)type); + return (void*)wxBitmap::FindHandler((wxChar*)extension, (long)type); #else return NULL; #endif I added this patch. Anthor is the line end problem in Visual Studio (C++)' s project files. wxcu-2.6.2.dsp and wxcu-2.6.2.dsw should use CR + LF for line terminator. I don't know your enviorment can use CR + LF line terminator well. If you can't, I will change final patch on tracker. > For further reference, I have opened a new item on the sf tracker > which should help the wxhaskell developers to follow the development > of this patch: > http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1369929&= group_id=3D73133&atid=3D536847 --=20 shelarcy <shelarcy capella.freemail.ne.jp> http://page.freett.com/shelarcy/ |
From: shelarcy <she...@ca...> - 2005-11-30 14:10:55
|
On Wed, 30 Nov 2005 22:59:05 +0900, shelarcy =20 <she...@ca...> wrote: > Anthor is the line end problem in Visual Studio (C++)' s project files. > wxcu-2.6.2.dsp and wxcu-2.6.2.dsw should use CR + LF for line terminato= r. > > I don't know your enviorment can use CR + LF line terminator well. > > If you can't, I will change final patch on tracker. This is not your mistake. I'm misunderstood, this problem. "patch" command convert line terminator automatically. --=20 shelarcy <shelarcy capella.freemail.ne.jp> http://page.freett.com/shelarcy/ |
From: Eric Y. K. <Eri...@lo...> - 2005-12-01 11:57:47
|
Hi, Good thing you checked ^_^ I've updated the patch on the tracker=20 http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1369929&group= _id=3D73133&atid=3D536847 You can also download it from here: http://www.loria.fr/~kow/download/patch-wxhaskell-unicode-08 Not sure what to do about the CR+LF thing - maybe just post the files on the tracker? On Wed, Nov 30, 2005 at 22:59:05 +0900, shelarcy wrote: > Hmm... you forgot two point in your newer patch. > One is eljbitmap.cpp must also chage three lines for Windows, like this. --=20 Eric Kow http://www.loria.fr/~kow PGP Key ID: 08AC04F9 Merci de corriger mon fran=E7ais. |
From: shelarcy <she...@ca...> - 2005-12-01 15:11:26
|
On Thu, 01 Dec 2005 20:56:55 +0900, Eric Y. Kow <Eri...@lo...> wrote= : > Good thing you checked ^_^ > > I've updated the patch on the tracker > http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1369929&g= roup_id=3D73133&atid=3D536847 > > You can also download it from here: > http://www.loria.fr/~kow/download/patch-wxhaskell-unicode-08 Now,. patch almost works well on Windows. > Not sure what to do about the CR+LF thing - maybe just post the files o= n > the tracker? Yes ... I think. I don't know how to fix this problem, either .... On Wed, 30 Nov 2005 23:10:48 +0900, shelarcy =20 <she...@ca...> wrote: > "patch" command convert line terminator automatically. --=20 shelarcy <shelarcy capella.freemail.ne.jp> http://page.freett.com/shelarcy/ |
From: shelarcy <she...@ca...> - 2005-11-09 16:40:04
|
On Tue, 13 Sep 2005 03:05:48 +0900, Eric Y. Kow <Eri...@lo...> wrote= : > Attached is the next version (04) of the patch. It fixes compile issue= s > on Linux. > > Now the Unicode patch has been tested and seems to work on both > Mac and Linux. > > Could somebody give it a try on Windows? I am Windows and Visual C++ User. But I have only Japanese Edition that report error message in Japanese, so I didn't notice that. Now, Microsoft provied Visual C++ 2005 Express Edition (VC8) freely an Month, VC8 can use with Platform SDK, and VC8 has optimised compiler - so I tested and report today for 05 version patch. VC reports unresolved external symnol message below, and VC8 report also some warning messages by wxWidgets. Linking... wxmswu.lib(string.obj) : error LNK2005: "public: __thiscall =20 wxString::wxString(char const *,class wxMBConv &,unsigned int)" =20 (??0wxString@@QAE@PBDAAVwxMBConv@@I@Z) already defined in apppath.obj Creating library .\..\out\wxc/wxc-msw2.4.2-0.9.4.lib and object =20 .\..\out\wxc/wxc-msw2.4.2-0.9.4.exp eljwindow.obj : error LNK2001: unresolved external symbol "char const * =20 const wxEmptyString" (?wxEmptyString@@3PBDB) eljwizard.obj : error LNK2001: unresolved external symbol "char const * =20 const wxEmptyString" (?wxEmptyString@@3PBDB) eljtextctrl.obj : error LNK2001: unresolved external symbol "char const *= =20 const wxEmptyString" (?wxEmptyString@@3PBDB) eljtglbtn.obj : error LNK2001: unresolved external symbol "char const * =20 const wxEmptyString" (?wxEmptyString@@3PBDB) ...... eljwizard.obj : error LNK2001: unresolved external symbol "protected: voi= d =20 __thiscall wxStringBase::InitWith(char const *,unsigned int,unsigned int)= " =20 (?InitWith@wxStringBase@@IAEXPBDII@Z) eljtglbtn.obj : error LNK2001: unresolved external symbol "protected: voi= d =20 __thiscall wxStringBase::InitWith(char const *,unsigned int,unsigned int)= " =20 (?InitWith@wxStringBase@@IAEXPBDII@Z) eljtipwnd.obj : error LNK2001: unresolved external symbol "protected: voi= d =20 __thiscall wxStringBase::InitWith(char const *,unsigned int,unsigned int)= " =20 (?InitWith@wxStringBase@@IAEXPBDII@Z) ...... There are too long. So I added build log that is generated by VC8. --=20 shelarcy <shelarcy capella.freemail.ne.jp> http://page.freett.com/shelarcy/ |