Menu
▾
▴
jazzplusplus-devel
|
From: Patrick E. <pa...@pa...> - 2004-03-23 07:48:10
|
I forgot to mention the headers... you'll also need the include files
from this dir:
wxGTK-2.4/contrib/include/wx/xrc
An easy solution would be to copy the xrc directory into your /usr/
include/wx hierarchy.
Patrick
|
|
From: Dave F. <dav...@co...> - 2004-03-23 08:06:09
|
On Tuesday 23 March 2004 07:48 am, Patrick Earl wrote: > I forgot to mention the headers... you'll also need the include files > from this dir: > > wxGTK-2.4/contrib/include/wx/xrc > > An easy solution would be to copy the xrc directory into your /usr/ > include/wx hierarchy. Odd thing is, it got all the way to the linking stage before bombing out over that. I suspect the mandrake wx packages are broke in this way. :( So I'm building again now just with the static library in my jazz/src directory. If it links, great. If it fails on include files, then I'll do that. ;) Dave > Patrick > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > jazzplusplus-devel mailing list > jaz...@li... > https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel -- Visit my website! http://www.davefancella.com/?event=em Honi soit la vache qui rit. |
|
From: Patrick E. <pa...@pa...> - 2004-03-23 08:14:56
|
On Monday 22 March 2004 17:06, Dave Fancella wrote:
> Odd thing is, it got all the way to the linking stage before
> bombing out over that. I suspect the mandrake wx packages are
> broke in this way. :( So I'm building again now just with the
> static library in my jazz/src directory. If it links, great. If
> it fails on include files, then I'll do that. ;)
If it made it to the linker, it must be that mandrake included the
headers. Funny that they'd include the headers and not the library
itself.
Anyways, is it compiling now? I wanna take off, but I also wanna know
if it's working. :)
Patrick
|
|
From: Dave F. <dav...@co...> - 2004-03-23 08:32:43
|
On Tuesday 23 March 2004 08:14 am, Patrick Earl wrote: > Anyways, is it compiling now? I wanna take off, but I also wanna know > if it's working. :) If you're still there, be satisfied that it *will* build, even if it hasn't. :) Now I'm getting undefined symbols, but I think that's because I configured wxGTK with default options and my mandrake-supplied package requires GTK2 instead. So I'll go do that, and I believe it will build after I do that. Dave -- Visit my website! http://www.davefancella.com/?event=em A penny saved has not been spent. |
|
From: Dave F. <dav...@co...> - 2004-03-23 09:11:49
|
On Tuesday 23 March 2004 08:14 am, Patrick Earl wrote: > Anyways, is it compiling now? I wanna take off, but I also wanna know > if it's working. :) Last time on this subject, I swear. :) I'm building again, here's what I had to do. Configure wxWidgets with --enable-gtk2 (had to delete config.cache for the change to take effect, since I had originally configured with default options). Build xrc according to your instructions. I didn't check out the changed configure.in you made, so I copied the resulting library (called libwx_gtk2_xrc.a) to /usr/lib. Then I had to modify my configure.in to link to libwx_gtk2_xrc. Note the "2" in there, because Mandrake compiled wxGTK against GTK2 rather than the old, ugly GTK. So, to make a check, we need to run wxconfig --basename in configure.in and check the base name, so we know what to link against. Then we could try compiling a test app against the xrc library and see if it runs. I added an if statement to check wx-config --basename and set the $LIBS accordingly for XRC, but no check for XRC itself. Still just assuming it's there.... So I committed configure.in. :) Anyway, just sticking what I'm thinking right now about the configure check, maybe I'll get to it sometime soon. Probably not. :) I didn't get as much done tonight as I'd hoped, but I'm going to bed. *yawn* The Doxy thing is important, though, and it's done, and I'm happy about that. :) Dave -- Visit my website! http://www.davefancella.com/?event=em A gourmet who thinks of calories is like a tart that looks at her watch. -- James Beard |
|
From: Patrick E. <pa...@pa...> - 2004-03-23 09:51:22
|
On Monday 22 March 2004 18:11, Dave Fancella wrote:
> On Tuesday 23 March 2004 08:14 am, Patrick Earl wrote:
> > Anyways, is it compiling now? I wanna take off, but I also wanna
> > know if it's working. :)
Okay... so much for going to bed early tonight. :)
> So, to make a check, we need to run wxconfig --basename in
> configure.in and check the base name, so we know what to link
> against. Then we could try compiling a test app against the xrc
> library and see if it runs. I added an if statement to check
> wx-config --basename and set the $LIBS accordingly for XRC, but no
> check for XRC itself. Still just assuming it's there....
Well, being a little crazy, I went and imported the xrc source into
the jazz tree. It's the same source under windows and linux and
such, so I figure it'll be happy with whatever compilation system
we're using. Right now it uses a standard Makefile and wx-config to
compile itself. This means that a standard check-out from the CVS
will now build with just the plain wxWidgets libraries. We don't
have to assume the library exists, since we build it ourselves.
Okay, now I'm going to bed. :)
Patrick
|
|
From: Dave F. <dav...@co...> - 2004-03-23 08:21:22
|
On Tuesday 23 March 2004 08:14 am, Patrick Earl wrote: > On Monday 22 March 2004 17:06, Dave Fancella wrote: > > Odd thing is, it got all the way to the linking stage before > > bombing out over that. I suspect the mandrake wx packages are > > broke in this way. :( So I'm building again now just with the > > static library in my jazz/src directory. If it links, great. If > > it fails on include files, then I'll do that. ;) > > If it made it to the linker, it must be that mandrake included the > headers. Funny that they'd include the headers and not the library > itself. > > Anyways, is it compiling now? I wanna take off, but I also wanna know > if it's working. :) Man. No. ;) With the library copied to jazz/src it failed to link. So I copied it to /usr/local/lib and ran ldconfig, and the damn thing is compiling every single .cpp again. Shouldn't have to, I didn't change anything! ;( This could take awhile, so unless you really want to stick around, you should take off. Dave > Patrick > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > jazzplusplus-devel mailing list > jaz...@li... > https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel -- Visit my website! http://www.davefancella.com/?event=em "We all know Linux is great...it does infinite loops in 5 seconds." (Linus Torvalds about the superiority of Linux on the Amterdam Linux Symposium) |
|
From: Patrick E. <pa...@pa...> - 2004-03-23 08:35:34
|
On Monday 22 March 2004 17:21, Dave Fancella wrote:
> With the library copied to jazz/src it failed to link. So I copied
> it to /usr/local/lib and ran ldconfig, and the damn thing is
> compiling every single .cpp again. Shouldn't have to, I didn't
> change anything! ;( This could take awhile, so unless you really
> want to stick around, you should take off.
That reminds me. Jazz takes a long time to compile. There's probably
too many headers being included in too many places. Some of the
headers even have code in them. Anyone know a good way to weed out
header dependencies?
BTW, ldconfig only affects shared libraries.
I change the configure.in file and it should now let you have the
libwx_gtk_xrc.a file in your src dir.
Patrick
|
|
From: Dave F. <dav...@co...> - 2004-03-23 08:44:20
|
On Tuesday 23 March 2004 08:35 am, Patrick Earl wrote: > On Monday 22 March 2004 17:21, Dave Fancella wrote: > > With the library copied to jazz/src it failed to link. So I copied > > it to /usr/local/lib and ran ldconfig, and the damn thing is > > compiling every single .cpp again. Shouldn't have to, I didn't > > change anything! ;( This could take awhile, so unless you really > > want to stick around, you should take off. > > That reminds me. Jazz takes a long time to compile. There's probably > too many headers being included in too many places. Some of the > headers even have code in them. Anyone know a good way to weed out > header dependencies? Brute force? No good way.... There's a lot of inline functions that require the compiler to know about the class it's calling. Whenever we see an inline function, I think we should ask "Does this really need to be inline?". The only reason I know of to use inline functions is performance. Granted that's a good reason. Anyway, then we should determine if the inline function requires knowledge of a class that is being included in a header file. If the answer is 'no' we can leave it inline, whether or not it needs to be, because performance is a good thing. Then we need to use forward declarations as much as possible in the header files so that each cpp file includes all the headers it needs to run, but each header file ideally should only include header files it needs. I also noticed quite a few header files being included that weren't needed at all. So there's a lot of places where we can eliminate included header files with forward declarations, and a lot of places where we can eliminate included header files that are needlessly included and move them to the .cpp file instead. I figure as I factor out engine code from the GUI I'll check each file I touch and either mark it as unfinished (with a '\todo' comment :) ), or finish it and just put a regular comment to say it's done. Maybe doxygen has a directive we can use and later ignore for this purpose. But if we all do this, then eventually the job will either be done or properly sized anyway and we'll know how big a job it is. :) Or we can just ignore it and wait for GCC 3.4, which is rumored to have precompiled header support contributed by Apple..... Dave > BTW, ldconfig only affects shared libraries. > > I change the configure.in file and it should now let you have the > libwx_gtk_xrc.a file in your src dir. > > Patrick > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > jazzplusplus-devel mailing list > jaz...@li... > https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel -- Visit my website! http://www.davefancella.com/?event=em Is knowledge knowable? If not, how do we know that? |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X