On Tue, Apr 8, 2008 at 10:49 AM, Ryan Pusztai <[EMAIL PROTECTED]> wrote:
>
> 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
On Tue, Apr 8, 2008 at 6:01 AM, andre arpin <[EMAIL PROTECTED]> wrote:
> John Labenski <[EMAIL PROTECTED]> writes:
>
> I agree it is just that wxLuaFreeze would have had to create a new program so
> I use the name lux.
Ok I see, you want the equivalent of wxLuaFreeze, but using the wx.dll
instea
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
debug.trace does not seems to work when using wx.dll.
Andre
-
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 co
Here is a simpler test.
Start the editor and create 3 new documents.
It fail for me.
Andre
-
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.,
John Labenski <[EMAIL PROTECTED]> writes:
> Look at the samples and you'll see that the wx.dll module is always
> "required", but of course if you're running the wxLuaFreeze executable
> it is already loaded so require "wx" does nothing.
>
> So, I don't think we need a new program lux.exe, since
On Wed, Apr 2, 2008 at 2:51 PM, Ryan Pusztai <[EMAIL PROTECTED]> wrote:
> On Wed, Apr 2, 2008 at 12:57 AM, John Labenski <[EMAIL PROTECTED]> wrote:
>
> > On the other hand, why not just use a staticly built wxLuaFreeze as
> > your Lua executable? It is the minimal version of a wxLua program and
> >
On Thu, Apr 3, 2008 at 10:20 AM, andre arpin <[EMAIL PROTECTED]> wrote:
> >
>
> What I would like is to be able to do is to replace lua.exe by lux.exe.
>
> lux X.lua which is a normal lua program run normally
> lux W.lua which uses wx.dll runs the same way as wxlua W.lua
>
> How would you conf
Ryan Pusztai <[EMAIL PROTECTED]> writes:
>
>
> On Wed, Apr 2, 2008 at 12:57 AM, John Labenski wrote:
> On the other hand, why not just use a staticly built wxLuaFreeze as
> your Lua executable? It is the minimal version of a wxLua program and
> can run any Lua program that lua.exe can. Is there
On Wed, Apr 2, 2008 at 12:57 AM, John Labenski <[EMAIL PROTECTED]> wrote:
> On the other hand, why not just use a staticly built wxLuaFreeze as
> your Lua executable? It is the minimal version of a wxLua program and
> can run any Lua program that lua.exe can. Is there any reason to want
> to dynam
>
> So... in order to get the single wx.dll, I think we need to build
> static libs for everything (wxWidgets and wxLua) and then link the
> wx.dll to them. I suppose that this could work; however we use
> bakefile to generate the build files and I am not sure that you can
> specify that all the o
I should note that I get a quite a few warnings, but I'm not sure how
to fix or appropriately silence them. They're typically "pointer
truncation from 'void *' to 'long'" or the other way around.
I haven't gone though them all. but for the most part they're for
wxWidgets functions that take or re
On Tue, Apr 1, 2008 at 12:13 PM, andre arpin <[EMAIL PROTECTED]> wrote:
> >
> > I don't use VC2005, I use VC6, but this doesn't seem right. The wxLua
> > module is uses DLLs from the other libs. If you want to link against
> > the other libs (not the DLLs) you should use the monolithic build
>
>
> I don't use VC2005, I use VC6, but this doesn't seem right. The wxLua
> module is uses DLLs from the other libs. If you want to link against
> the other libs (not the DLLs) you should use the monolithic build
> which will generate a single wx.dll that only depends on the wxWidgets
> DLLs.
>
>
On Sun, Mar 30, 2008 at 1:18 PM, andre arpin <[EMAIL PROTECTED]> wrote:
> The compile fail. The following changes create a usable dll.
>
> Change where made within VS2005 but should apply to other version
>
> change:
>
> C++
> (preprocessor)
> WXUSINGDLL to WXMAKINGDLL_BINDWXADV
>
> LINKER
>
andre arpin <[EMAIL PROTECTED]> writes:
Should have mentionned that this applies to mod_luamodule
mod_luamodule_mono does not compile in VS2005 as well maybe related I do nnot
know.
Andre
-
Check out the new SourceForge.ne
The compile fail. The following changes create a usable dll.
Change where made within VS2005 but should apply to other version
change:
C++
(preprocessor)
WXUSINGDLL to WXMAKINGDLL_BINDWXADV
LINKER
(general)
(additional library directories)
change all the vc_dll to vc_lib
(input)
(additional d
17 matches
Mail list logo
