jazzplusplus-devel

Re: [jazzplusplus-devel] JAZZ ease of installation

[Kevin C. <ke...@do...>]

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....

Re: [jazzplusplus-devel] JAZZ ease of installation

[Dave F. <dav...@co...>]

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