On Sat, Mar 03, 2007 at 11:14:11AM -0800, Ken Taylor wrote: > ... But not without some ugly hacks :P I figure clean cross-platform > building can be worked out by those with more experience in the area than > I -- I just wanted something to mess around with for the time being!
Great to hear! > - A recent update to the bzr branch caused a broken build due to > httpclient.cc not being able to find sys/socket.h or netinet/in.h, so I > removed it from my vos/libs/vos/extensions/http/Makefile.am for the moment. > A simple make -k didn't work because of a bug in automake on windows ( > http://cygwin.com/ml/cygwin/2005-01/msg00698.html ) That was just a quick hack so I wasn't thinking about cross platform issues, but unfortunately the Windows socket headers are different from the Unix ones. The correct solution is something like: #ifdef WIN32 #include <winsock2.h> #else #include <sys/socket.h> #include <netinet/in.h> #endif > - After building everything, I manually edited the libtool script and set > deplibs_check_method="pass_all" (which is set in 3 locations for some > reason), then went back and re-made csplugin. Yay, it made a dll for me :P > > - I renamed vos/inplace/lib/crystalspace/libvos_csplugin.csplugin to > libvos_csplugin-0.csplugin I just acquired a new (old) computer that I'm going to set up with Windows XP. I want to set up a continuous build so we can catch some of these cross platform issues earlier. > - I modified vos/inplace/etc/crystalspace/vfs.cfg to use paths from windows > root instead of the msys root "/c/..." (I had to do this for 0.23 as well) Hmm, okay. Did the installer distribution do this? I don't remember. > - This is all in addition to the changes I made earlier, modifying > vos/apps/tests/Makefile.am to set "sqltest = " and > vos/libs/vos/vutil/strftime_r.cc to #if out the env functions. > > So now wxterangreal runs! I'm still having the same keyboard-input problem I > was having when I tried to build my own wxgl.dll in 0.23, but mouse-input > seems to work fine. I'll have to look closer at how that gets built I guess. I don't know what's going on with the keyboard problem -- you may have to dig into the interaction between the Windows event loop and WxWidgets. Does the "wxtest" app in the Crystalspace directory build and work, and does that get keyboard input? It's also possible there's a bug in the translation from the wxwidgets event to the Crystal Space event, although if that were the case the rest of the UI would work fine and only the 3D panel would have keyboard input trouble (unless there's also a focus management problem). That's all speculation, though. I should mention that OS X has a similar problem with it not getting keyboard input. However, I think we tracked that down to an issue with the fact that OS X required applications jump through some additional hoops to be properly initialized. I haven't got things completely sorted out on OS X, though. My plans for s5 are to do parallel development for each platform as much as possible, with regular, automated builds on each of Windows, OS X and Linux. > Also, I'm still having trouble logging in to the default world > vip://interreality.org/world -- but I'm having this problem on 0.23 too. This seems to be a server side problem -- I believe there is a deadlock happening somewhere, because the VIP connection thread is accepting connections, but the site isn't responding. I'm want to to see if I can attach to it with a debugger and determine what is going on. -- [ Peter Amstutz ][ [EMAIL PROTECTED] ][ [EMAIL PROTECTED] ] [Lead Programmer][Interreality Project][Virtual Reality for the Internet] [ VOS: Next Generation Internet Communication][ http://interreality.org ] [ http://interreality.org/~tetron ][ pgpkey: pgpkeys.mit.edu 18C21DF7 ]
signature.asc
Description: Digital signature
_______________________________________________ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
