On Fri, May 4, 2012 at 12:31 PM, Andre Arpin <ar...@kingston.net> wrote: > John Labenski <jlabenski@...> writes: > > OK there is a light at the end of the tunnel. > > using the following batch > > cd "E:\wxWidgets\wxLua\ > md cmake > cd cmake > cmake -trace -G "Visual Studio 9 2008" > -DwxWidgets_ROOT_DIR:STRING=E:/wxWidgets > -DwxWidgets_LIB_DIR:STRING=E:/wxWidgets/lib/vc_lib E:/wxWidgets/wxLua > > and removing the incremental link in > > wxLua > wxLuaCan > wxLuaFreeze > > Compile successfully.
The incremental linker in 2008 seems to have a lot of problems. For awhile I had to always build twice or more because the first time the linker died. This wasn't the case here was it? In other words, when you build the wxLua app one of the wxLua libs that the apps links to had not built correctly. If you turn the incremental linker back on and press build a few times do you see the linker (segfault or whatever it was) error in the build output window? I applied SP1 to VS2008 and it seemed to have made it a little better, but the linker would still crash. Mysteriously, a half a year later the linker now works great... I didn't change anything, unless some Win7 security patch fixed something. Here's one of the discussions about it, there are many many more... http://social.msdn.microsoft.com/Forums/en/vcgeneral/thread/2a29f8ec-7c71-475d-a358-f2f1b0458f8b > The current version does not seem to support unicode characters. > ex: > echo ["╪"] > xx How is the file encoded, UTF-8 or UTF-16? If I run this code in wxLua or wxLuaEdit I get a message box with that character as the caption and the text so it works fine when pasted into a program's source code. wx.wxMessageBox("╪", "╪") I made a change recently to use UTF8 for Lua, this means that if you use Lua to open a file as a string, the string is treated as though it's UTF8 when it is passed to wxWidgets, i.e. nothing is done if it's just regular ASCII 0-127, but translated otherwise. However, if you try to open a file that is UTF16 (what windows uses/ed it's confusing) you'll have a problem. There was a message thread last week where this was discussed, see rev 67. http://wxlua.svn.sourceforge.net/viewvc/wxlua/trunk/wxLua/modules/wxlua/include/wxlstate.h?view=log If you change the defines 30 #define WXLUA_USE_WXSTR_CONVUTF8 1 31 #define WXLUA_USE_WXSTR_CONVCURRENT 0 to 30 #define WXLUA_USE_WXSTR_CONVUTF8 0 31 #define WXLUA_USE_WXSTR_CONVCURRENT 1 does it fix it for you? Even it does, we can't revert since otherwise the text in the GUI is broken, I think it has something to do with the file encoding and reading it from disk. Regards, John ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ wxlua-users mailing list wxlua-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxlua-users
