Menu
▾
▴
jazzplusplus-devel — Discussion Forum for Jazz Developers
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
(189) |
Apr
(40) |
May
(8) |
Jun
(6) |
Jul
(5) |
Aug
|
Sep
|
Oct
|
Nov
(13) |
Dec
(10) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(4) |
Feb
(1) |
Mar
(3) |
Apr
|
May
(7) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(1) |
| 2006 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
(8) |
Oct
(19) |
Nov
(19) |
Dec
(7) |
| 2007 |
Jan
(6) |
Feb
(6) |
Mar
(3) |
Apr
(6) |
May
(1) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
(2) |
Dec
(1) |
| 2008 |
Jan
(19) |
Feb
(1) |
Mar
(40) |
Apr
(31) |
May
(174) |
Jun
(24) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(64) |
Dec
(17) |
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(14) |
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(7) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
(5) |
Mar
(1) |
Apr
(1) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(11) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Patrick E. <pa...@pa...> - 2004-03-24 03:39:12
|
The file is included in the first of these rpms from suse 9.0: ftp://ftp.suse.com/pub/suse/i386/9.0/suse/i586/ wxGTK-2.4.1.2-70.i586.rpm ftp://ftp.suse.com/pub/suse/i386/9.0/suse/i586/ wxGTK-devel-2.4.1.2-70.i586.rpm There doesn't appear to be a wxwin.m4 in 8.2. If those don't work, you could try digging around on rpmfind.net. Anyone know why they'd put the m4 in the main package and not in the devel file? To me, it doesn't seem particularly useful without the headers and libraries. Failing all that, you could always install Debian. ;) Patrick On Tuesday 23 March 2004 21:52, Matt Kelly wrote: > All, > > I tried to build Jazz from CVS, and it fails in the aclocal > command: > > > aclocal: configure.in: 119: macro `AM_OPTIONS_WXCONFIG' not found > in library aclocal: configure.in: 122: macro `AM_PATH_WXCONFIG' not > found in lib > > I'm running on SuSE 8.2 pro, using the WxGTK packages that come > with it. It's 2.4.0. > > This is some kind of M4 thang, but I'm not sure how to resolve it. > Where are you Mandrake guys getting this macro from?? Looks like > there needs to be a wxwin.m4 as mentioned in configure.in, but my > system does not have this file. > > Matt > > > > ------------------------------------------------------- > 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=cli >ck _______________________________________________ > jazzplusplus-devel mailing list > jaz...@li... > https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel |
|
From: Patrick E. <pa...@pa...> - 2004-03-24 03:19:23
|
Hmm.. Go in to the jazz dir (the root dir with configure in it) and
run a "cvs update -PAd". If that doesn't fix it, try checking out a
new copy of the source. I just did this on my box:
> mv jazz jazz2
> cvs co jazz
... snip snip ...
> find jazz -name "*dia*"
jazz/bitmaps/dialog.xpm
jazz/dialogs.txt
jazz/src/dialogs.cpp
jazz/src/dialogs.h
jazz/src/dialogs
The bmp shouldn't be there anymore either. Looks like your copy just
isn't updating nicely.
Patrick
|
|
From: Matt K. <ra...@ch...> - 2004-03-24 01:55:17
|
All, I tried to build Jazz from CVS, and it fails in the aclocal command: aclocal: configure.in: 119: macro `AM_OPTIONS_WXCONFIG' not found in library aclocal: configure.in: 122: macro `AM_PATH_WXCONFIG' not found in lib I'm running on SuSE 8.2 pro, using the WxGTK packages that come with it. It's 2.4.0. This is some kind of M4 thang, but I'm not sure how to resolve it. Where are you Mandrake guys getting this macro from?? Looks like there needs to be a wxwin.m4 as mentioned in configure.in, but my system does not have this file. Matt |
|
From: Matt K. <ra...@ch...> - 2004-03-23 22:46:12
|
Patrick, Nope, still can't see it. Here's what I did: warp>> cvs -z3 -d:pserver:ano...@cv...:/cvsroot/jazzplusplus update -d . ? config.log cvs server: Updating . cvs server: Updating bitmaps cvs server: Updating conf cvs server: Updating contrib cvs server: Updating contrib/CakeWalk-Converter cvs server: Updating contrib/borland cvs server: Updating midinetd cvs server: Updating mswin cvs server: Updating scripts cvs server: Updating song cvs server: Updating song/arpeggio cvs server: Updating song/rmg cvs server: Updating song/shuffle cvs server: Updating src cvs server: Updating src/commands cvs server: Updating src/dialogs cvs server: Updating src/gui cvs server: Updating xrc cvs server: Updating xrc/expat cvs server: Updating xrc/expat/xmlparse cvs server: Updating xrc/expat/xmltok cvs server: Updating xrc/include cvs server: Updating xrc/include/wx cvs server: Updating xrc/include/wx/xrc warp>> Looks up to date. Then, I did: warp>> find . -name "*dia*" ./src/dialogs ./src/dialogs.h ./src/dialogs.cpp ./bitmaps/dialog.bmp ./bitmaps/dialog.xpm warp>> What am I missing??? Matt > > Hmm, it's in the CVS now. It might not have been when I wrote the > message. I've been making stupid little mistakes all day... didn't > get much sleep last night. > > Patrick > > On Tuesday 23 March 2004 15:43, Matt Kelly wrote: > > > 2. Work on porting dialogs. It's pretty easy to get started > > > porting a dialog. I added a dialogs.txt file to the CVS that > > > provides some info in that area. > > > > Patrick -- I can't find this file, and I just did a CVS update. > > Did you check it in? > > > > Matt > > > > ------------------------------------------------------- > 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 > |
|
From: Patrick E. <pa...@pa...> - 2004-03-23 22:33:58
|
Hmm, it's in the CVS now. It might not have been when I wrote the
message. I've been making stupid little mistakes all day... didn't
get much sleep last night.
Patrick
On Tuesday 23 March 2004 15:43, Matt Kelly wrote:
> > 2. Work on porting dialogs. It's pretty easy to get started
> > porting a dialog. I added a dialogs.txt file to the CVS that
> > provides some info in that area.
>
> Patrick -- I can't find this file, and I just did a CVS update.
> Did you check it in?
>
> Matt
|
|
From: Matt K. <ra...@ch...> - 2004-03-23 22:27:45
|
> 2. Work on porting dialogs. It's pretty easy to get started porting > a dialog. I added a dialogs.txt file to the CVS that provides some > info in that area. Patrick -- I can't find this file, and I just did a CVS update. Did you check it in? Matt |
|
From: Patrick E. <pa...@pa...> - 2004-03-23 22:27:28
|
On Tuesday 23 March 2004 06:31, Dave Fancella wrote:
> We should look at using xpm on windows and Mac instead of bmp, I
> think. It's supposed to be supported by wx2.4. Then we can get
> rid of the non-xpm stuff and just use xpm for graphics.
I checked into it as well, and XPM is supported on all platforms. I
killed the bmp files and the makefile that converted them.
BTW, has anyone tried editing XPM files in xemacs (or perhaps even
emacs)? It's a little surreal. :)
Patrick
|
|
From: Patrick E. <pa...@pa...> - 2004-03-23 22:02:59
|
I wanted to let people know what I'm working on and list a few
opportunities that have not yet been filled.
Aside from random jobs here and there, I've been working on the code
for the piano window (specifically pianowin.cpp). My goal is to
simplify the code and to fix any bugs that have been created by the
porting process. Since trackwin.cpp and eventwin.cpp are closely
related, I will be expanding my efforts to the cleanup of all three
of those files. I will be working on the GUI side of things.
I will continue development of tResourceDialog as needed to support
different types of XML dialogs (resdlg.cpp and resdlg.h).
What are some concrete opportunities to help out?
1. Fix the midi code. This may involve cleaning up the ALSA code,
using PortMidi, or perhaps other options. This is one of the more
complicated tasks that remains.
2. Work on porting dialogs. It's pretty easy to get started porting
a dialog. I added a dialogs.txt file to the CVS that provides some
info in that area.
3. Pick a window (for example, the harmony browser) and make sure
that all of the keystrokes, mouse clicks, dialogs, and GUI work
properly.
Patrick
|
|
From: Dave F. <dav...@co...> - 2004-03-23 21:31:34
|
On Tuesday 23 March 2004 07:32 pm, Patrick Earl wrote: > BTW, I removed the automatically generated configure and Makefile.in > files from the CVS. It probably wasn't such a great idea to put them > there in the first place. I left the .xpm files there for people who > don't have the bmptoppm, etc. utilities. Thank you. :) I was going to mention it when I noticed my last commit updating all the generated stuff. We should look at using xpm on windows and Mac instead of bmp, I think. It's supposed to be supported by wx2.4. Then we can get rid of the non-xpm stuff and just use xpm for graphics. Dave > Patrick > > On Tuesday 23 March 2004 12:09, Matt Kelly wrote: > > All, > > > > This may be a bit premature, but I feel we need to keep in mind > > which environments we want JAZZ to be able to run in. > > > > The old JAZZ would work OK on Windoze and most Linuxes distros > > without much problem. > > > > I worry that the shiny new JAZZ will only run on the latest distros > > with all the latest bleeding edge packages installed, and nothing > > else! If this happens, adoption will be slow -- if using the latest > > JAZZ requires one to upgrade one's distro, that will be a problem, > > IMHO. > > > > I'm not saying we need to support Slackware 1.0 or anything, but > > whatever we do, we need to make sure that it will install fairly > > easily on most reasonably current systems. We need to be sure we > > supply all needed RPMs, etc. right in our section of the > > sourceforge site, if at all possible, and clearly state which RPMs > > are needed in which situations. > > > > Another thing I worry about is the possibility of hosing a user's > > system up by forcing them to install, for example, GTK2.x. I've > > heard of situations where doing so made their X sessions not run > > anymore, since they were based on GTK1.x. > > > > The easier it is for people to install and use JAZZ, the more > > people will use it. > > > > Anyway, sorry to ramble, too much coffee this morning! > > > > Matt K. > > ------------------------------------------------------- > 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 LILO, you've got me on my knees! (from David Black, db...@pi..., with apologies to Derek and the Dominos, and Werner Almsberger) |
|
From: Dave F. <dav...@co...> - 2004-03-23 21:29:05
|
On Tuesday 23 March 2004 08:29 pm, Kevin Cosgrove wrote: > On 23 March 2004 at 12:32, Patrick Earl <pa...@pa...> wrote: > > I agree. It's kinda tricky to produce portable software. We've > > committed to the path of using the autotools, which helps, but it > > also complicates things. A full development environment is more > > difficult to create on a Windows system. > > Some consideration for Linux systems are or have been: > > OSS, ALSA 0.5, ALSA 0.9, ALSA 1.0 This right here is the reason I want to offload the interface to the midi sequencer to another library that has that level of support and will be updated to pick up new APIs and stuff. :) We also need to consider, on windows, WMME, DirectSound, and ASIO. On Mac we have three sound libraries as well, both Alsa and ASIO, and there's a third I think is called CoreAudio or something like that. And then there's all the others, BSD (using an OSS interface, I believe), BeOs, and a few others. > wxWindows 1.68e, wxWidgets 2.X wxWindows 168e is obsolete. I don't think it's unreasonable at all to ask them upgrade from an obsolete version. If they *require* it for some reason, we can direct them to the old jazz that uses it already. (and keep copies of the old jazz around for download if people really want it) Granted, they won't get the latest bleeding edge features and stuff we're working on, but that's the price you pay for using obsolete libraries. wx2 and wx2.2 I think we should forget about as well, for similar reasons. They're both deprecated, wx2.4 has been out long enough that all the major distributions have picked it up, and we can reasonably be certain that a package exists for any user's system. We can easily provide links and so forth, as well. > GTK 1 vs. 2. GTK2 in wx2.4 is still considered experimental. I would prefer to support both as much as possible, since GTK2 in wxWidgets is coming, and GTK1 will ultimately be deprecated and rendered obsolete by GTK2, so we need to plan for it. But you guys are right, we need to support GTK1 now no matter what. For those of us using Mandrake, we need support for GTK2, since that's what the Mandrake RPMs of wxWidgets are compiled for. For that matter, isn't GTK2 considered experimental? ;) What I wouldn't give for wxWidgets with at least Qt, preferably KDE support.... > LessTif Does anybody still use this? I thought LessTif was rendered obsolete when all the Motif desktops disappeared to be replaced by Gnome and KDE. In any case, there's no currently maintained wxMotif port anymore, and if we commit to wx2.4 (which I think we should), then we have to forget about wxMotif. We can think about supporting wxUniversal, though, which uses wxWidgets's's own widget set rather than a native widget set, in case people don't want to use GTK at all. That might be a good alternative to trying to support LessTif. > gcc 2.95.3 vs. 3.X I'm in the 3.3 school right now, and it's pretty sturdy. The way I understand it, anything that builds with 3.3 should build smoothly with 2.95, although the reverse isn't necessarily true because 3.3 is stricter in a lot of ways. But yeah, we should support multiple compilers as much as possible. I also think we should support Cygwin as a build environment, because I don't think it's fair to give someone Free software and require them to purchase a proprietary development IDE to build it. > I'm certainly not advocating supporting all of that. I've been > through a lot of gyrations regarding building jazz++ on various > versions of Makdrake from 7.0 through 9.0. It's a real pain to > preserve a usable build environment. Keeping the binary usable > on various systems would be possible. We should decide what > the requirements are and work toward that. > > > Aside from the midi/audio driver dependencies, the only dependency in > > Jazz right now is the core wxWidgets 2.4 library. All of the > > discussion about problems with XRC is now obsolete. The xrc source > > was added to the jazz distribution and now has a proper Makefile.am. > > It should compile anywhere Jazz itself will compile. > > What system versions are people working with now? I'm running on > Mandrake 9.0 and will move to 9.2. If someone can give me the build > and run-time dependencies, then I can post the versions of those > tools available on my distributions. Hmmm, not sure what the question is yet. XRC is currently the preferred resource file for wxWindows, but it's still considered experimental. It will ultimately be merged into wxWidgets, and when that happens we can quit worrying about it to some extent (or rather, we'll check for it in configure and if the user's system wxWidgets has XRC, then we'll use it instead of ours). Dave > TTFN.... > > > > > ------------------------------------------------------- > 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 For thee the wonder-working earth puts forth sweet flowers. -- Titus Lucretius Carus |
|
From: joakim v. <jo...@ve...> - 2004-03-23 21:00:00
|
Now it compiles! And starts, even :-) Thanks for including the wxxrc stuff Patrick. Now to figure out what to do.... hmmm. Cheers, /Joakim |
|
From: Kevin C. <ke...@do...> - 2004-03-23 20:30:10
|
On 23 March 2004 at 12:32, Patrick Earl <pa...@pa...> wrote:
> I agree. It's kinda tricky to produce portable software. We've
> committed to the path of using the autotools, which helps, but it
> also complicates things. A full development environment is more
> difficult to create on a Windows system.
Some consideration for Linux systems are or have been:
OSS, ALSA 0.5, ALSA 0.9, ALSA 1.0
wxWindows 1.68e, wxWidgets 2.X
GTK 1 vs. 2.
LessTif
gcc 2.95.3 vs. 3.X
I'm certainly not advocating supporting all of that. I've been
through a lot of gyrations regarding building jazz++ on various
versions of Makdrake from 7.0 through 9.0. It's a real pain to
preserve a usable build environment. Keeping the binary usable
on various systems would be possible. We should decide what
the requirements are and work toward that.
> Aside from the midi/audio driver dependencies, the only dependency in
> Jazz right now is the core wxWidgets 2.4 library. All of the
> discussion about problems with XRC is now obsolete. The xrc source
> was added to the jazz distribution and now has a proper Makefile.am.
> It should compile anywhere Jazz itself will compile.
What system versions are people working with now? I'm running on
Mandrake 9.0 and will move to 9.2. If someone can give me the build
and run-time dependencies, then I can post the versions of those
tools available on my distributions.
TTFN....
|
|
From: Patrick E. <pa...@pa...> - 2004-03-23 19:32:13
|
I agree. It's kinda tricky to produce portable software. We've
committed to the path of using the autotools, which helps, but it
also complicates things. A full development environment is more
difficult to create on a Windows system.
Aside from the midi/audio driver dependencies, the only dependency in
Jazz right now is the core wxWidgets 2.4 library. All of the
discussion about problems with XRC is now obsolete. The xrc source
was added to the jazz distribution and now has a proper Makefile.am.
It should compile anywhere Jazz itself will compile.
BTW, I removed the automatically generated configure and Makefile.in
files from the CVS. It probably wasn't such a great idea to put them
there in the first place. I left the .xpm files there for people who
don't have the bmptoppm, etc. utilities.
Patrick
On Tuesday 23 March 2004 12:09, Matt Kelly wrote:
> All,
>
> This may be a bit premature, but I feel we need to keep in mind
> which environments we want JAZZ to be able to run in.
>
> The old JAZZ would work OK on Windoze and most Linuxes distros
> without much problem.
>
> I worry that the shiny new JAZZ will only run on the latest distros
> with all the latest bleeding edge packages installed, and nothing
> else! If this happens, adoption will be slow -- if using the latest
> JAZZ requires one to upgrade one's distro, that will be a problem,
> IMHO.
>
> I'm not saying we need to support Slackware 1.0 or anything, but
> whatever we do, we need to make sure that it will install fairly
> easily on most reasonably current systems. We need to be sure we
> supply all needed RPMs, etc. right in our section of the
> sourceforge site, if at all possible, and clearly state which RPMs
> are needed in which situations.
>
> Another thing I worry about is the possibility of hosing a user's
> system up by forcing them to install, for example, GTK2.x. I've
> heard of situations where doing so made their X sessions not run
> anymore, since they were based on GTK1.x.
>
> The easier it is for people to install and use JAZZ, the more
> people will use it.
>
> Anyway, sorry to ramble, too much coffee this morning!
>
> Matt K.
|
|
From: Matt K. <ra...@ch...> - 2004-03-23 18:53:38
|
All, This may be a bit premature, but I feel we need to keep in mind which environments we want JAZZ to be able to run in. The old JAZZ would work OK on Windoze and most Linuxes distros without much problem. I worry that the shiny new JAZZ will only run on the latest distros with all the latest bleeding edge packages installed, and nothing else! If this happens, adoption will be slow -- if using the latest JAZZ requires one to upgrade one's distro, that will be a problem, IMHO. I'm not saying we need to support Slackware 1.0 or anything, but whatever we do, we need to make sure that it will install fairly easily on most reasonably current systems. We need to be sure we supply all needed RPMs, etc. right in our section of the sourceforge site, if at all possible, and clearly state which RPMs are needed in which situations. Another thing I worry about is the possibility of hosing a user's system up by forcing them to install, for example, GTK2.x. I've heard of situations where doing so made their X sessions not run anymore, since they were based on GTK1.x. The easier it is for people to install and use JAZZ, the more people will use it. Anyway, sorry to ramble, too much coffee this morning! Matt K. |
|
From: Patrick E. <pa...@pa...> - 2004-03-23 17:11:57
|
The source is in jazz/xrc. That directory could probably use a proper
Makefile.am.
Patrick
On Tuesday 23 March 2004 03:53, Joakim Verona wrote:
> Hello,
>
> Ok so I got it to configure now, but not to build.
> It bombs on "wxxrc".
>
> Whats this and how do you get it?
>
> If I can figure out this, maybe I can contribute a proper
> configure.in test.
>
> Cheers,
> /Joakim
>
>
>
> -------------------------------------------------------
> 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=cli
>ck _______________________________________________
> jazzplusplus-devel mailing list
> jaz...@li...
> https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel
|
|
From: Joakim V. <jo...@ve...> - 2004-03-23 10:56:29
|
Hello, Ok so I got it to configure now, but not to build. It bombs on "wxxrc". Whats this and how do you get it? If I can figure out this, maybe I can contribute a proper configure.in test. Cheers, /Joakim |
|
From: Joakim V. <jo...@ve...> - 2004-03-23 10:41:35
|
Hello, I was going to try the new build on sourceforge CVS. It doesnt configure out of the box, because the configure script can't find wx-config. With my set of wx rpms the script is now called wxgtk-2.4-config. This sequence does work: ./bootstrap ./configure --enable-alsa=yes --enable-sequencer2=yes --with-wx-config=wxgtk-2.4-config make anyway... Im using the wxGTK rpms from CCRMA. The automake include is from the same rpm, so its odd. Regards /Joakim |
|
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 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: 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? |
|
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: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 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: Dave F. <dav...@co...> - 2004-03-23 08:16:30
|
On Tuesday 23 March 2004 08:08 am, Patrick Earl wrote: > On Monday 22 March 2004 16:53, Dave Fancella wrote: > > All, > > > > There's a new jazz.doxy file in the root. If you have doxygen > > installed, you can just type 'doxygen jazz.doxy' from the root. > > Then open a browser at 'doc/html/index.html' to browse the class > > documentation. > > > > Anyone not know how to document code with doxygen? I'll be happy > > to throw up the rudimentary stuff I do here... > > The whos whatsit? Actually, I've never used it before. I wouldn't > mind seeing some samples and/or a pointer to reference material. http://www.doxygen.org/ Here's what I do, and this is really all I do, but I'm not opposed to finding out cooler things to do. :) In the header file, over each member declaration, something like this: /// This is a brief description of this thing Note the three slashes. In the .cpp file, over each member definition, something like this: /** * This is a long description * that spans multiple lines. */ You can also add this: /** * This is a long description of the member. * * params * @firstargument * description */ You've probably seen comment blocks like that before, I'll bet. In any case, note the extra asterisk on the first line of the comment block: /** The three slashes '///' and the extra asterisk '/**' tell doxygen that *this* code block documents the member that appears right after it. if you have a block like this: // \todo // Fix this stupid bug *name bug here* Then doxygen will generate a todo list. When you run doxygen, using the jazz.doxy file, doxygen will recursively scan every source file in the jazz/src directory looking for those comment blocks and build documentation in the jazz/doc directory. It'll build both html and latex versions of the docs. I figure we just distribute the doxy file and tell people if they want to build the documentation, run doxygen on it. 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 You know you have a small apartment when Rice Krispies echo. -- S. Rickly Christian |
|
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
|
86 messages has been excluded from this view by a project administrator.
