On Mon, Apr 7, 2008 at 11:38 PM, John Labenski <[EMAIL PROTECTED]> wrote:
> Try to explain your problems. You are right that, currently we do not
> have a build to create a single monolithic wx.dll as I am not sure how
> to persuade Bakefile to generate something like that (at least not
> yet, but I do see the advantage of having that build so I will work on
> it).
>
> Regards,
> John
>
OK I will try to explain what I am doing. I made an application at work that
wraps our (Works) shared library. In this library I added many things to
vanilla Lua interpreter and it makes other, non-programmers be able to write
tests and applications without bothering a Software Engineer. Now as the
project when on I was asked to support GUI from my application. This
prompted me to use wxLua as a Lua module, because:
1. Not all people/scripts need a GUI.
2. wxLua already exists and is really good once built.
3. Re-use of other common libraries without re-building my application
would be MUCH easier
to maintain.
So the real problem is deployment of my application. Once the wxLua module
is used I need to include 8+ dlls along with my application. Now that sounds
OK for you or me, but my goal it to have these scripts be easy enough to
deploy that our customers can use these scripts. They can't be expected to
know anything about how to get this to work. Also the skill level for the
"non-programmers" is not high enough to also create an installer for all the
scripts they write, so that they can deploy them to other people. So in this
case I see a benefit to wxLuaFreeze, but I can't make "my" additions to Lua
as a Lua module at this point because it would be too much work and time.
And wxLua already supports wx as a Lua module.
Another problem is using the default build files fail for me. It is the
OpenGL libraries that fail. Now you and I have talked a few times about this
and it just doesn't work for me. So I have actually created my own set of
build files that work exactly as I need (plus they include OpenGL too so I
don't know what is going wrong), except I am linking against the wxWidgets
dll as a monolithic target. I build with MinGW and not VC and I think this
is part of the reason the current build files don't work. I would rather
just have one dll instead, but having 4 dlls is OK for me right now.
I am using Premake for this task and I just "plug" it in to the wxLua source
tree under the build directory and it works great. If I could get a few
ideas on what actually needed to be done to link a wx.dll as a single dll I
could probably add this to my solution. This could maybe help others as well
(including yourself ;) ) I could help you with how I set it up. I don't know
if they are ready for every bodies eyes just yet, but they are very close.
They give you build files for all of VC 6-2005, Code::Blocks, and GNU make
files.
Hope this helps explain my wxLua use.
--
Regards,
Ryan
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Register now and save $200. Hurry, offer ends at 11:59 p.m.,
Monday, April 7! Use priority code J8TLD2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
wxlua-users mailing list
wxlua-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxlua-users
