From: klaas.holwerda <kla...@nl...> - 2006-08-04 09:07:41
|
Hi, From my bindings.i file i get generated things like: extern (int) a2dDrawer2D_methodCount; and extern (int) s_wxluatag_a2dLauWrapper; On fedora gcc 4.0.0-8 this does not compile, if i remove the () and make plain int all is oke. Why is it (int), maybe it is better to generate it as only int? regards, Klaas -- Unclassified |
From: John L. <jla...@gm...> - 2006-08-04 15:21:27
|
On 8/4/06, klaas.holwerda <kla...@nl...> wrote: > From my bindings.i file i get generated things like: > > extern (int) a2dDrawer2D_methodCount; > and > extern (int) s_wxluatag_a2dLauWrapper; > > On fedora gcc 4.0.0-8 this does not compile, if i remove the () and make > plain int all is oke. > > Why is it (int), maybe it is better to generate it as only int? You need to add these lines to your rules file probably. Just use the dummy macros i you don't want to export them. -- Set the DLLIMPEXP macros for compiling these bindings into a DLL -- Use "WXLUA_NO_DLLIMPEXP" and "WXLUA_NO_DLLIMPEXP_DATA" for no IMPEXP macros output_cpp_impexpsymbol = "WXDLLIMPEXP_WXBIND" output_cpp_impexpdatasymbol = "WXDLLIMPEXP_DATA_WXBIND" -John Labenski |
From: klaas.holwerda <kla...@nl...> - 2006-08-07 10:13:57
|
Hi John, It seems to be only on Linux. The two lines you mention are set to the next in my case: output_cpp_impexpsymbol = "" output_cpp_impexpdatasymbol = "" But only on linux i get the (int) while on windows it is only int. I find it hard to believe myself, but checking it again it looks like there is a difference here?? Do you have a switch somewhere in the binding generator? Thanks, Klaas John Labenski wrote: > On 8/4/06, klaas.holwerda <kla...@nl...> wrote: > >> From my bindings.i file i get generated things like: >> >> extern (int) a2dDrawer2D_methodCount; >> and >> extern (int) s_wxluatag_a2dLauWrapper; >> >> On fedora gcc 4.0.0-8 this does not compile, if i remove the () and make >> plain int all is oke. >> >> Why is it (int), maybe it is better to generate it as only int? >> > > You need to add these lines to your rules file probably. Just use the > dummy macros i you don't want to export them. > > -- Set the DLLIMPEXP macros for compiling these bindings into a DLL > -- Use "WXLUA_NO_DLLIMPEXP" and "WXLUA_NO_DLLIMPEXP_DATA" for no IMPEXP macros > > output_cpp_impexpsymbol = "WXDLLIMPEXP_WXBIND" > output_cpp_impexpdatasymbol = "WXDLLIMPEXP_DATA_WXBIND" > > > -John Labenski > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Wxlua-users mailing list > Wxl...@li... > https://lists.sourceforge.net/lists/listinfo/wxlua-users > -- Unclassified |
From: John L. <jla...@gm...> - 2006-08-07 18:20:28
|
On 8/7/06, klaas.holwerda <kla...@nl...> wrote: > Hi John, > > It seems to be only on Linux. This can't happen, the genwxbind.lua doesn't do anything different in msw or linux. > The two lines you mention are set to the next in my case: > output_cpp_impexpsymbol = "" > output_cpp_impexpdatasymbol = "" > > But only on linux i get the (int) while on windows it is only int. These should be set to these empty macros, see bindings/wx_rules.lua output_cpp_impexpsymbol = "WXLUA_NO_DLLIMPEXP" output_cpp_impexpdatasymbol = "WXLUA_NO_DLLIMPEXP_DATA" They're defined in wxLua/modules/wxlua/include/wxlbind.h > I find it hard to believe myself, but checking it again it looks like > there is a difference here?? > Do you have a switch somewhere in the binding generator? No difference between platforms and no switch. John Labenski > John Labenski wrote: > > On 8/4/06, klaas.holwerda <kla...@nl...> wrote: > > > >> From my bindings.i file i get generated things like: > >> > >> extern (int) a2dDrawer2D_methodCount; > >> and > >> extern (int) s_wxluatag_a2dLauWrapper; > >> > >> On fedora gcc 4.0.0-8 this does not compile, if i remove the () and make > >> plain int all is oke. > >> > >> Why is it (int), maybe it is better to generate it as only int? > >> > > > > You need to add these lines to your rules file probably. Just use the > > dummy macros i you don't want to export them. > > > > -- Set the DLLIMPEXP macros for compiling these bindings into a DLL > > -- Use "WXLUA_NO_DLLIMPEXP" and "WXLUA_NO_DLLIMPEXP_DATA" for no IMPEXP macros > > > > output_cpp_impexpsymbol = "WXDLLIMPEXP_WXBIND" > > output_cpp_impexpdatasymbol = "WXDLLIMPEXP_DATA_WXBIND" > > > > > > -John Labenski > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share your > > opinions on IT & business topics through brief surveys -- and earn cash > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > Wxlua-users mailing list > > Wxl...@li... > > https://lists.sourceforge.net/lists/listinfo/wxlua-users > > > > > -- > Unclassified > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Wxlua-users mailing list > Wxl...@li... > https://lists.sourceforge.net/lists/listinfo/wxlua-users > |
From: Klaas H. <db...@nl...> - 2006-08-10 10:20:25
|
Hi John, Updating to the latest version of wxLua solved it. Actually it is the first time i get my app working with wxLua on Linux. (with the older version i had still static initialization problems). So things go very well. BUT when configuring wxLua, it did not find wxstedit correctly. I did also install the lattest wxstedit. And lloked in /usr/local/lib/, and there is see libstedit.a and libsteditd.a which is gooed i think. I did find stedit.h in /usr/local/include/wx/stedit/ So all fine i think. Therefore i went to see in config.log, why configure did not find wxstedit. And there i see things like this: configure:4959: checking if wxStEdit (version >= 1.2.0) is available configure:4994: g++ -o conftest -g3 -O0 -Wall -Wundef -Wno-ctor-dtor-privacy -I/usr/local/lib/wx/include/gtk2-ansi-debug-static-2.6 -I/usr/local/include/wx-2.6 -D__WXDEBUG__ -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D_LARGEFILE_SOURCE=1 -DNO_GCC_PRAGMA conftest.cc -lstedit -L/usr/local/lib -pthread -L/usr/X11R6/lib /usr/local/lib/libwx_gtk2d_stc-2.6.a /usr/local/lib/libwx_gtk2d_xrc-2.6.a /usr/local/lib/libwx_gtk2d_html-2.6.a /usr/local/lib/libwx_gtk2d_adv-2.6.a /usr/local/lib/libwx_based_net-2.6.a /usr/local/lib/libwx_based_xml-2.6.a /usr/local/lib/libwx_gtk2d_core-2.6.a /usr/local/lib/libwx_based-2.6.a -lexpat -pthread -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lglib-2.0 -lXinerama -lXxf86vm -lpng -ljpeg -ltiff -lz -ldl -lm >&5 /usr/local/include/wx/stedit/stedit.h:18: error: aggregate 'WXDLLEXPORT wxMenu' has incomplete type and cannot be defined /usr/local/include/wx/stedit/stedit.h:19: error: aggregate 'WXDLLEXPORT wxKeyEvent' has incomplete type and cannot be defined /usr/local/include/wx/stedit/stedit.h:20: error: aggregate 'WXDLLEXPORT wxFindDialogEvent' has incomplete type and cannot be defined /usr/local/include/wx/stedit/stedit.h:21: error: aggregate 'WXDLLEXPORT wxToolBar' has incomplete type and cannot be defined /usr/local/include/wx/stedit/stedit.h:22: error: aggregate 'WXDLLEXPORT wxConfigBase' has incomplete type and cannot be defined /usr/local/include/wx/stedit/stedit.h:23: error: aggregate 'WXDLLEXPORT wxFileHistory' has incomplete type and cannot be defined /usr/local/include/wx-2.6/wx/event.h:1352: error: 'wxMenu' is not a type /usr/local/include/wx-2.6/wx/event.h:1366: error: expected ';' before '*' token /usr/local/include/wx-2.6/wx/event.h:1368: error: expected `;' before 'virtual' /usr/local/include/wx-2.6/wx/event.h:1372: error: expected ';' before '*' token /usr/local/include/wx-2.6/wx/event.h: In constructor 'wxMenuEvent::wxMenuEvent(wxEventType, int, int*)': /usr/local/include/wx-2.6/wx/event.h:1354: error: 'm_menu' was not declared in this scope /usr/local/include/wx-2.6/wx/event.h: In copy constructor 'wxMenuEvent::wxMenuEvent(const wxMenuEvent&)': /usr/local/include/wx-2.6/wx/event.h:1357: error: 'm_menu' was not declared in this scope /usr/local/include/wx-2.6/wx/event.h:1357: error: 'const class wxMenuEvent' has no member named 'm_menu' /usr/local/include/wx-2.6/wx/event.h: At global scope: /usr/local/include/wx-2.6/wx/event.h:2508: error: cannot declare pointer to 'void' member /usr/local/include/wx-2.6/wx/event.h:2508: error: typedef 'wxCharEventFunction' is initialized (use __typeof__ instead) /usr/local/include/wx-2.6/wx/event.h:2508: error: expected primary-expression before ')' token /usr/local/include/wx-2.6/wx/generic/accel.h:51: error: expected ',' or '...' before '&' token /usr/local/include/wx-2.6/wx/generic/accel.h:52: error: expected ',' or '...' before '&' token And in the end of course: configure:5000: $? = 1 configure: failed program was: | | /* confdefs.h. */ | | #define PACKAGE_NAME "wxLua" | #define PACKAGE_TARNAME "wxlua" | #define PACKAGE_VERSION "0" | #define PACKAGE_STRING "wxLua 0" | #define PACKAGE_BUGREPORT "fr...@us..." | #ifdef __cplusplus | extern "C" void std::exit (int) throw (); using std::exit; | #endif | /* end confdefs.h. */ | #include <wx/stedit/stedit.h> | int | main () | { | | wxSTEditor dummy; | | // version check | #if defined(STE_MAJOR_VERSION) && defined(STE_MINOR_VERSION) && defined(STE_RELEASE_VERSION) | #if (STE_MAJOR_VERSION > (1) || (STE_MAJOR_VERSION == (1) && STE_MINOR_VERSION > (2)) || (STE_MAJOR_VERSION == (1) && STE_MINOR_VERSION == (2) && STE_RELEASE_VERSION >= (0))) | // this component is recent enough | #else | #error wxStEdit is too old ! At least version 1.2.0 is required | #endif | #else | #error wxStEdit does not define its version symbols STE_MAJOR_VERSION, STE_MINOR_VERSION, STE_RELEASE_VERSION | #endif | | ; | return 0; | } | Is this also my fault, or is something wrong? Thanks, Klaas John Labenski wrote: > > >>I find it hard to believe myself, but checking it again it looks like >>there is a difference here?? >>Do you have a switch somewhere in the binding generator? > > > No difference between platforms and no switch. > -- Unclassified |
From: Doug C. <dou...@gm...> - 2006-08-10 12:50:01
|
Thursday, August 10, 2006, 6:19:40 AM, Klaas Holwerda wrote: > [...] > BUT when configuring wxLua, it did not find wxstedit correctly. > I did also install the lattest wxstedit. And lloked in /usr/local/lib/, > and there is see libstedit.a and libsteditd.a which is gooed i think. > I did find stedit.h in /usr/local/include/wx/stedit/ This is the same problem I had with a `configure` based build with mingw/msys on Windows. > [...] > /usr/local/include/wx/stedit/stedit.h:18: error: aggregate 'WXDLLEXPORT > wxMenu' has incomplete type and cannot be defined The configure script seems to be using #include <wx/stedit/stedit.h> in a generated c file to see if the version of wxStEdit is OK. But stedit.h needs to have some other headers included (wx.h?) to compile properly. e -- Doug Currie Londonderry, NH |
From: Doug C. <dou...@gm...> - 2006-08-10 13:09:41
|
I just tested my conjecture, and adding the line: #include <wx/wx.h> in the configure script here: /* end confdefs.h. */ #include <wx/wx.h> #include <wx/stedit/stedit.h> works for me. e Thursday, August 10, 2006, 8:49:59 AM, Doug Currie wrote: > Thursday, August 10, 2006, 6:19:40 AM, Klaas Holwerda wrote: >> [...] >> BUT when configuring wxLua, it did not find wxstedit correctly. >> I did also install the lattest wxstedit. And lloked in /usr/local/lib/, >> and there is see libstedit.a and libsteditd.a which is gooed i think. >> I did find stedit.h in /usr/local/include/wx/stedit/ > This is the same problem I had with a `configure` based build with > mingw/msys on Windows. >> [...] >> /usr/local/include/wx/stedit/stedit.h:18: error: aggregate 'WXDLLEXPORT >> wxMenu' has incomplete type and cannot be defined > The configure script seems to be using > #include <wx/stedit/stedit.h> > in a generated c file to see if the version of wxStEdit is OK. But > stedit.h needs to have some other headers included (wx.h?) to compile > properly. > e -- Doug Currie Londonderry, NH |
From: John L. <jla...@gm...> - 2006-08-10 20:02:08
|
On 8/10/06, Doug Currie <dou...@gm...> wrote: > I just tested my conjecture, and adding the line: > > #include <wx/wx.h> > > in the configure script here: > > /* end confdefs.h. */ > #include <wx/wx.h> > #include <wx/stedit/stedit.h> > > works for me. Yes this has already been fixed in the CVS version of wxStEdit. I will also adjust the configure script to #include "wx/wx.h" just to be sure. Additionally I am trying to get configure to work a little more seamlessly and have added some hacks so that you can specify the wxstedit path and the actual lib to link against. Unfortunately we need a nice way to systematically name the libs uniformly, ideally using the exact same syntax for the build settings that wxWidgets uses. (I have asked about that on wx-dev years ago, but the need for this fell on deaf ears unfortunately) I think that we (I and other wxCode people) should add this naming ability to our bakefiles, but I'm not sure how to go about just yet. I'm still trying to get the configure working properly. If you're using Linux, you might want to just use the Makefiles in the src dirs, where the ones in the apps dirs will automatically build whatever that app needs. These Makefiles use wx-config and are fairly simple to understand, they output the libs to the "wx-config --exec-prefix" dir so that must be writable. The apps themselves are just compiled to the src dir you're building from. I will try to work some more on configure as I have not tried it before a few days ago, unfortunately Francesco is away for the next couple weeks and we use a modified version of Bakefile so some of the changes they might need to be made can't be done properly until we get the bakefiles redone. Sorry about the problems, hopefully I can get it sorted out fairly quickly John Labenski > > Thursday, August 10, 2006, 8:49:59 AM, Doug Currie wrote: > > > Thursday, August 10, 2006, 6:19:40 AM, Klaas Holwerda wrote: > > >> [...] > > >> BUT when configuring wxLua, it did not find wxstedit correctly. > >> I did also install the lattest wxstedit. And lloked in /usr/local/lib/, > >> and there is see libstedit.a and libsteditd.a which is gooed i think. > >> I did find stedit.h in /usr/local/include/wx/stedit/ > > > This is the same problem I had with a `configure` based build with > > mingw/msys on Windows. > > >> [...] > > >> /usr/local/include/wx/stedit/stedit.h:18: error: aggregate 'WXDLLEXPORT > >> wxMenu' has incomplete type and cannot be defined > > > The configure script seems to be using > > > #include <wx/stedit/stedit.h> > > > in a generated c file to see if the version of wxStEdit is OK. But > > stedit.h needs to have some other headers included (wx.h?) to compile > > properly. > > > e > > -- > Doug Currie > Londonderry, NH > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Wxlua-users mailing list > Wxl...@li... > https://lists.sourceforge.net/lists/listinfo/wxlua-users > |
From: Klaas H. <db...@nl...> - 2006-08-11 10:18:06
|
Hi John, John Labenski wrote: Unfortunately we > need a nice way to systematically name the libs uniformly, ideally > using the exact same syntax for the build settings that wxWidgets > uses. (I have asked about that on wx-dev years ago, but the need for > this fell on deaf ears unfortunately) I think that we (I and other > wxCode people) should add this naming ability to our bakefiles, but > I'm not sure how to go about just yet. I find the way the wxlua libs are named rather nice. And i thought the idea is to have it the way wxwidgets does it. Only wxlua in front of it. We discussed this when the whole bakefile stuff started fro wxLua. Why not use the same for stedit or any other wxCode project? Do you not like it? Klaas -- Unclassified |
From: John L. <jla...@gm...> - 2006-08-11 19:27:00
|
On 8/11/06, Klaas Holwerda <db...@nl...> wrote: > Hi John, > > John Labenski wrote: > Unfortunately we > > need a nice way to systematically name the libs uniformly, ideally > > using the exact same syntax for the build settings that wxWidgets > > uses. (I have asked about that on wx-dev years ago, but the need for > > this fell on deaf ears unfortunately) I think that we (I and other > > wxCode people) should add this naming ability to our bakefiles, but > > I'm not sure how to go about just yet. > > I find the way the wxlua libs are named rather nice. And i thought the > idea is to have it the way wxwidgets does it. Only wxlua in front of it. > We discussed this when the whole bakefile stuff started fro wxLua. > Why not use the same for stedit or any other wxCode project? Do you not > like it? I do like it, but it has to be implemented. The only problem is when to find the time. :( Regards, John Labenski |
From: klaas.holwerda <kho...@xs...> - 2006-08-11 22:07:17
|
John Labenski wrote: > > > I do like it, but it has to be implemented. The only problem is when > to find the time. :( > I see, same problem here with wxArt2D :-( But knowing that Francesco is very far with a wxWindows package tool, i think it will eventually be organized that way. At least i can not imagine packages working properly without a good naming convention for the generated libraries. So maybe you should just wait a little in this case, until wxPm is out? I have the feeling this is what Francesco has in mind for wxCode ;-) regards, Klaas |
From: John L. <jla...@gm...> - 2006-08-14 14:31:24
|
On 8/11/06, klaas.holwerda <kho...@xs...> wrote: > John Labenski wrote: > > > > > > I do like it, but it has to be implemented. The only problem is when > > to find the time. :( > > > I see, same problem here with wxArt2D :-( > But knowing that Francesco is very far with a wxWindows package > tool, i think it will eventually be organized that way. > At least i can not imagine packages working properly without a good > naming convention for the generated libraries. > > So maybe you should just wait a little in this case, until wxPm is out? > I have the feeling this is what Francesco has in mind for wxCode ;-) Ok, we'll wait Thanks, John Labenski |