On 9/5/07, John Labenski <[EMAIL PROTECTED]> wrote:
>
> You're using the wxWidgets monolithic build it seems using mingw?
Yes I am using monolithic MinGW.
Do you use "configure" with mingw or just makefile.gcc?
I am using the makefile.gcc.
The monolithic
> build is broken because nobody's checked it. In fact I don't even know
> what gets put into the monolithic build?
Wow. That is not good. You are planning on fixing that, right? I think the
monolithic dll version is the only way, I personally, would use the dll
version. I don't like having 6+ dll's as dependencies. I could deal with it
for static linking, but I figure, that is just more setup and more setting I
need to set in my main project that will use wxLua. ;-)
If I remember correctly the
> GL lib is not part of it, just like the jpeg lib isn't. Is there a
> list somewhere about what is part of the monolithic build so that we
> can add the extra libs for wxLua to link to?
Good question. I don't have a real need for GL so I never use it, so I
couldn't say. As for jpeg and other image libraries, I think they are
included in the wx dll. I will check for sure when I get back to work
tomorrow.
..\..\..\lib\gcc_lib/libwxlua_msw28_wxbindgl.a(wxbindgl_lib_wxgl_bind.o):wxgl_bind.cpp:(.data+0xc):
> > undefined reference
> > to `wxGLCanvas::ms_classInfo'
>
> Ok, this says clearly that you need to link to the wxWidgets GL lib
> since it's not part of -lwxmsw28.
I have added that in the location in the makefile where the Bakefile named
variable is located and I still got the same results. I will double verify
this tomarrow at work and post the errors.
You should have a wxmsw28_gl.lib file (just like -lwxmsw28_stc) in the
> wxWidgets lib dir if you've built it.
Yes. I definatly have it and it is right next to the other build files. What
compilers are actively tested? Is it only VC?
I'll try to find some time to look into it again, but I could not
> figure out how to get bakefile to work right for this before.
That is kind of the point I was driving at in my previous email. Your
project is only as good as your ability to build it.
I should write something about this. There is a little about the
> modules in the wxlua.html file with some comments on what depends on
> what. You need modules/wxlua and modules/wxbind at least. The parts of
> modules/wxbind are exactly like the wxWidgets libs, take the ones you
> want, typically base, core, adv...
That would be a great help. Thanks.
A lot of work has gone into making the bakefiles work as well as they
> do. I personally have a hard time understanding the XML/python nature
> of them, but Francesco does and I believe he is still on vacation. I
> hope he has time to look at this when he gets back. wxLua uses
> bakefile since that's what wxWidgets uses, if it works for them it
> should be able to work for us since we target the same systems and
> compilers.
Yes, I understand that. There is a very massive code base for that. It makes
sense. I just want get a feel for how the project runs.
--
Regards,
Ryan
RJP Computing
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
wxlua-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wxlua-users
