IMHO requires are a PITA. You then have the hassle of trying to figure out what which libs you need to require. I am sure everyone here has spent time scratching their head trying to figure out just what lib they have forgotten to include when their app won't compile/run. One fairly common solution is to 'shotgun' and require everything, defeating the object of requires in the first place.
A single shared lib with all bindings sounds good to me. Les John Labenski wrote: > Ok, one thing at a time, but I think we almost have everything else > working, but we'll only know that when people try it. > > For the monolithic build: > > How do you envision it? A single shared library with wxLua and all the > bindings? I assume this is so that wx.so/dll is just a single file. > Or? > > Note: The wxLua libraries were separated since wxPython (for good or > bad) separates them, but goes even further by making you import each > library and even classes, "import wx; import wx.lib.docview" for > example. > > Would wxLua like to have to have in addition to wx.so, wxlua.so, > wxlua_base.so, wxlua_core.so, wxlua_xxx so you can "require" only the > bits you really want. > > Regards, > John > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ wxlua-users mailing list wxlua-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxlua-users
