Menu
▾
▴
jazzplusplus-devel
|
From: Kevin C. <ke...@co...> - 2008-03-20 16:28:11
|
On 19 March 2008 at 10:47, "Peter J. Stieber" <dev...@to...> wrote: > I'm planning on posting wxWidgets build instructions on the Jazz++ web > site. These instructions should build a version of wxWidgets that is > compatible with Jazz++. Unfortunately, that will not happen until > tonight (I am current at my day job). Until then, this is how to go > about it... [snip] > Robert I really appreciate you attempt to build Jazz++ on a Debian box. When you get those instructions, please post something here. I'd like to try building on my Mandriva 2007.0 box. Do you know the relationship between wxWidgets and wxGTK? I've got the latter installed, of course the version is too old. Thanks..... P.S.: I used to build & use Jazz++ years ago. I'm glad to see someone resurrecting it! -- Kevin |
|
From: Kevin C. <ke...@co...> - 2008-03-20 18:42:28
|
On 20 March 2008 at 9:58, Pete Stieber <pst...@ve...> wrote: > KC> Do you know the relationship between wxWidgets and wxGTK? > KC> I've got the latter installed, of course the version is > KC> too old. > > Requires GTK 2. Here's what I have installed on my Fedora 8 box. This > is way more than what you need. You need the gtk2-devel packages. Does that mean that wxWidgets built with gtk2 is equivalent to wxGTK, disregarding version numbers for the moment? I'm trying to figure out a clean way to get wxGTK and wxWindows to coexist on my machine, and looking to the future when my distribution supplied wxGTK might fulfill the Jazz++ requirements. Thanks... -- Kevin |
|
From: Pete S. <pst...@ve...> - 2008-03-20 20:21:39
|
KC = Kevin Cosgrove KC>>> Do you know the relationship between wxWidgets and wxGTK? KC>>> I've got the latter installed, of course the version is KC>>> too old. PS = Pete Stieber PS>> Requires GTK 2. Here's what I have installed on my PS>> Fedora 8 box. This is way more than what you need. PS>> You need the gtk2-devel packages. KC> Does that mean that wxWidgets built with gtk2 is KC> equivalent to wxGTK, disregarding version numbers KC> for the moment? Yes. KC> I'm trying to figure out a clean way to get wxGTK KC> and wxWindows to coexist on my machine, wxGTK is wxWidgets. Note that Microsoft forced a name change. wxWindows is now wxWidgets. wxWidgets built for the Microsoft Windows API is called wxMSW. wxWidgets built using GTK is called wxGTK. KC> and looking to the future when my distribution KC> supplied wxGTK might fulfill the Jazz++ KC> requirements. I think I understand. Audacity (http://audacity.sourceforge.net/) also uses wxWidgets and someone builds an RPM for both wxWidgets and Audacity that end up on the Fedora mirrors. In this case, Audacity (audacity-1.3.2-17.fc8.x86_64) uses version 2.6.4 of wxWidgets installed as a package called compat-wxGTK26-2.6.4-0.8.x86_64. There is also a more current version of wxWidgets (2.8.4) available on Fedora using GTK that is called wxGTK-2.8.4-6.fc8.x86_64. We probably couldn't use that version because it is probably a stock build. If I used shared objects from wxGTK, we might need something like jazz-wxGTK-2.8.7-0.1.x86_64, but I statically link with wxGTK. We might just be able to distribute Jazz++ without a wxGTK (i.e. wxWidgets) distribution on Linux. Hope that helps, Pete |
|
From: Kevin C. <ke...@co...> - 2008-03-20 20:50:55
|
On 20 March 2008 at 13:06, Pete Stieber <pst...@ve...> wrote: > wxGTK is wxWidgets. Note that Microsoft forced a name change. > wxWindows is now wxWidgets. wxWidgets built for the Microsoft Windows > API is called wxMSW. wxWidgets built using GTK is called wxGTK. > > I think I understand. Audacity (http://audacity.sourceforge.net/) also > uses wxWidgets and someone builds an RPM for both wxWidgets and Audacity > that end up on the Fedora mirrors. In this case, Audacity > (audacity-1.3.2-17.fc8.x86_64) uses version 2.6.4 of wxWidgets installed > as a package called compat-wxGTK26-2.6.4-0.8.x86_64. > > There is also a more current version of wxWidgets (2.8.4) available on > Fedora using GTK that is called wxGTK-2.8.4-6.fc8.x86_64. We probably > couldn't use that version because it is probably a stock build. > > If I used shared objects from wxGTK, we might need something like > jazz-wxGTK-2.8.7-0.1.x86_64, but I statically link with wxGTK. We might > just be able to distribute Jazz++ without a wxGTK (i.e. wxWidgets) > distribution on Linux. Aha! That makes sense now. Presuming that whatever additions Jazz++ requires make it into the next wxWidgets release (2.8.8?) then my distribution will eventually pick that up, including wxGTK2.8-2.8.8-1mdv2009.0.i586.rpm and its development companions in the distribution repository and maybe even on the installation media. Now I just need to decide for myself whether or not to attempt to follow Mandriva's parallel library version installation scheme. My alternative is to install the alpha wxWidgets in a jazz++ specific place. > Hope that helps, It does! Thanks.... -- Kevin |
|
From: Pete S. <pst...@ve...> - 2008-03-20 21:02:47
|
PS = Pete Stieber PS>> wxGTK is wxWidgets. Note that Microsoft forced a PS>> name change. wxWindows is now wxWidgets. wxWidgets PS>> built for the Microsoft Windows API is called wxMSW. PS>> wxWidgets built using GTK is called wxGTK. PS>> PS>> I think I understand. Audacity PS>> (http://audacity.sourceforge.net/) also uses wxWidgets PS>> and someone builds an RPM for both wxWidgets and Audacity PS>> that end up on the Fedora mirrors. In this case, PS>> Audacity (audacity-1.3.2-17.fc8.x86_64) uses version PS>> 2.6.4 of wxWidgets installed as a package called PS>> compat-wxGTK26-2.6.4-0.8.x86_64. PS>> PS>> There is also a more current version of wxWidgets (2.8.4) PS>> available on Fedora using GTK that is called PS>> wxGTK-2.8.4-6.fc8.x86_64. We probably couldn't use that PS>> version because it is probably a stock build. PS>> PS>> If I used shared objects from wxGTK, we might need PS>> something like jazz-wxGTK-2.8.7-0.1.x86_64, but I PS>> statically link with wxGTK. We might just be able to PS>> distribute Jazz++ without a wxGTK (i.e. wxWidgets) PS>> distribution on Linux. KC = Kevin Cosgrove KC> Aha! That makes sense now. KC> KC> Presuming that whatever additions Jazz++ requires make KC> it into the next wxWidgets release (2.8.8?) I haven't made any changes to the wxWidgets source. I just build it with configure options that are different from the stock build. KC> then my distribution will eventually pick that up, KC> including wxGTK2.8-2.8.8-1mdv2009.0.i586.rpm and its KC> development companions in the distribution repository KC> and maybe even on the installation media. I'm guessing you will not have to deal with a wxGTK distribution, but building wxGTK with Jazz++ compatible options, then building Jazz++, on each platform you wish to create a Jazz++ distribution. I believe Audacity is using shared objects (*.so files) from wxGTK, so they need to distribute them. I'm statically linking against wxGTK, so you will not need to distribute wxGTK. Maybe this will make distribution generation easier for you :-) KC> Now I just need to decide for myself whether or not to KC> attempt to follow Mandriva's parallel library version KC> installation scheme. My alternative is to install the KC> alpha wxWidgets in a jazz++ specific place. Thanks for thinking about and dealing with all of these issues. Pete |
|
From: Kevin C. <ke...@co...> - 2008-03-20 21:24:25
|
On 20 March 2008 at 14:03, Pete Stieber <pst...@ve...> wrote: > I haven't made any changes to the wxWidgets source. I just > build it with configure options that are different from the > stock build. Cool. I'll see what Mandriva has in their RPM spec file for wxGTK and see if/how the config options differ. > KC> then my distribution will eventually pick that up, > KC> including wxGTK2.8-2.8.8-1mdv2009.0.i586.rpm and its > KC> development companions in the distribution repository and > KC> maybe even on the installation media. > > I'm guessing you will not have to deal with a wxGTK > distribution, but building wxGTK with Jazz++ compatible > options, then building Jazz++, on each platform you wish to > create a Jazz++ distribution. I believe Audacity is using > shared objects (*.so files) from wxGTK, so they need to > distribute them. I'm statically linking against wxGTK, so > you will not need to distribute wxGTK. Maybe this will make > distribution generation easier for you :-) I think we're using the word "distribution" to mean different things. I mean in the context of Fedora, Ubuntu and Mandriva are distributions. I'm not referring to distributing files. > Thanks for thinking about and dealing with all of these issues. No problem.... -- Kevin |
|
From: Pete S. <pst...@ve...> - 2008-03-20 17:00:25
|
PS = Pete Stieber PS>> I'm planning on posting wxWidgets build instructions PS>> on the Jazz++ web site. These instructions should PS>> build a version of wxWidgets that is compatible with PS>> Jazz++. Unfortunately, that will not happen until PS>> tonight (I am current at my day job). Until then, PS>> this is how to go about it... KC = Kevin Cosgrove KC> [snip] PS>> Robert I really appreciate you attempt to build PS>> Jazz++ on a Debian box. KC> When you get those instructions, please post something KC> here. Done. http://jazzplusplus.sourceforge.net/developers/ KC> I'd like to try building on my Mandriva 2007.0 box. KC> KC> Do you know the relationship between wxWidgets and wxGTK? KC> I've got the latter installed, of course the version is KC> too old. Requires GTK 2. Here's what I have installed on my Fedora 8 box. This is way more than what you need. You need the gtk2-devel packages. I'm just being lazy with my grep ;-) # rpm -qa | grep gtk GConf2-gtk-2.20.1-1.fc8.x86_64 pygtk2-libglade-2.12.0-2.fc8.x86_64 usermode-gtk-1.93.1-1.fc8.x86_64 pygtk2-codegen-2.12.0-2.fc8.x86_64 pygtk2-devel-2.12.0-2.fc8.x86_64 gtk2-2.12.5-1.fc8.i386 gtkhtml2-2.11.1-2.fc8.x86_64 gtkmm24-2.12.3-1.fc8.x86_64 gtk-nodoka-engine-0.6.2-1.fc8.x86_64 pygtksourceview-2.0.0-1.fc8.x86_64 authconfig-gtk-5.3.18-1.fc8.x86_64 pygtk2-2.12.0-2.fc8.x86_64 gtk2-2.12.5-1.fc8.x86_64 gnome-python2-gtkhtml2-2.19.1-12.fc8.x86_64 gtkspell-2.0.11-4.fc8.x86_64 gtk2-engines-2.12.2-1.fc8.x86_64 pygtk2-devel-2.12.0-2.fc8.i386 gtk2-engines-2.12.2-1.fc8.i386 gtk-sharp2-2.10.0-6.fc8.x86_64 gtkglext-libs-1.2.0-5.fc8.x86_64 xdg-user-dirs-gtk-0.6-2.fc8.x86_64 gtksourceview2-2.0.2-1.fc8.x86_64 pygtkglext-1.1.0-3.fc8.x86_64 gtk2-devel-2.12.5-1.fc8.x86_64 gtk-doc-1.9-4.fc8.noarch Pete |
|
From: Robert V. <vo...@ct...> - 2008-03-20 18:38:53
|
Hi Pete, Thank you for your excellent directions. wxwidgets downloaded and compiled clean (the log is huge, but a quick scan shows no apparent problems.) Also I configured, compiled, and installed Jazz++. It can open screens, it talks to alsa. it drives a softsynth, and displays are looking reaonable. For me it is not configured quite right though. I put in a path for install of /usr/local/bin, but it actually put a binary in /usr/local/bin/bin. I copied the binary into /usr/local/bin and ran it. It seems to have a problem locating its own configuration file. (A couple of screen shots attached. Don't know if they'll get through on this list.) Looks like a good start. Bob ----- Original Message ----- From: "Pete Stieber" <pst...@ve...> To: <jaz...@li...> Sent: Thursday, March 20, 2008 12:58 PM Subject: Re: [jazzplusplus-devel] Any thoughts on this ? > PS = Pete Stieber > PS>> I'm planning on posting wxWidgets build instructions > PS>> on the Jazz++ web site. These instructions should > PS>> build a version of wxWidgets that is compatible with > PS>> Jazz++. Unfortunately, that will not happen until > PS>> tonight (I am current at my day job). Until then, > PS>> this is how to go about it... > > KC = Kevin Cosgrove > KC> [snip] > > PS>> Robert I really appreciate you attempt to build > PS>> Jazz++ on a Debian box. > > KC> When you get those instructions, please post something > KC> here. > > Done. > > http://jazzplusplus.sourceforge.net/developers/ > > KC> I'd like to try building on my Mandriva 2007.0 box. > KC> > KC> Do you know the relationship between wxWidgets and wxGTK? > KC> I've got the latter installed, of course the version is > KC> too old. > > Requires GTK 2. Here's what I have installed on my Fedora 8 box. This > is way more than what you need. You need the gtk2-devel packages. I'm > just being lazy with my grep ;-) > > # rpm -qa | grep gtk > GConf2-gtk-2.20.1-1.fc8.x86_64 > pygtk2-libglade-2.12.0-2.fc8.x86_64 > usermode-gtk-1.93.1-1.fc8.x86_64 > pygtk2-codegen-2.12.0-2.fc8.x86_64 > pygtk2-devel-2.12.0-2.fc8.x86_64 > gtk2-2.12.5-1.fc8.i386 > gtkhtml2-2.11.1-2.fc8.x86_64 > gtkmm24-2.12.3-1.fc8.x86_64 > gtk-nodoka-engine-0.6.2-1.fc8.x86_64 > pygtksourceview-2.0.0-1.fc8.x86_64 > authconfig-gtk-5.3.18-1.fc8.x86_64 > pygtk2-2.12.0-2.fc8.x86_64 > gtk2-2.12.5-1.fc8.x86_64 > gnome-python2-gtkhtml2-2.19.1-12.fc8.x86_64 > gtkspell-2.0.11-4.fc8.x86_64 > gtk2-engines-2.12.2-1.fc8.x86_64 > pygtk2-devel-2.12.0-2.fc8.i386 > gtk2-engines-2.12.2-1.fc8.i386 > gtk-sharp2-2.10.0-6.fc8.x86_64 > gtkglext-libs-1.2.0-5.fc8.x86_64 > xdg-user-dirs-gtk-0.6-2.fc8.x86_64 > gtksourceview2-2.0.2-1.fc8.x86_64 > pygtkglext-1.1.0-3.fc8.x86_64 > gtk2-devel-2.12.5-1.fc8.x86_64 > gtk-doc-1.9-4.fc8.noarch > > Pete > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > jazzplusplus-devel mailing list > jaz...@li... > https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel > |
|
From: Pete S. <pst...@ve...> - 2008-03-20 20:03:32
|
RV = Robert Vogel RV> Thank you for your excellent directions. RV> wxwidgets downloaded and compiled clean RV> (the log is huge, but a quick scan shows RV> no apparent problems.) Glad to hear that was a success. RV> Also I configured, compiled, and installed RV> Jazz++. It can open screens, it talks to RV> alsa. it drives a softsynth, and displays RV> are looking reaonable. Excellent! RV> For me it is not configured quite right RV> though. I put in a path for install of RV> /usr/local/bin, So does this mean you added --prefix=/usr/local/bin to you configure line? If you did, you don't need to do this. The default installation location is /usr/local and any binary files will automatically be placed in /usr/local/bin. If you specify --prefix, this is considered the top-level installation directory for all architecture independent files, and subdirectories will be created under this directory. You can specify a particular location for the executable files, but that configure option is --bindir. If you want them in /usr/local/bin, you don't have to specify anything because this is the default. To see all of the options available to you when running configure, type $ ./configure --help This is standard operating procedure for the configure file generated by the autotools, so you can use what you are learning here for any package that uses the autotools. Since the code "isn't ready for prime time" I usually install the code in a build directory that is in parallel with my source tree. Under my home directory I create a subdirectory called Jazz++. Under that directory I checkout the entire subversion repository. This creates a jazzplusplus directory under Jazz++. In parallel to (at the same level as) the jazzplusplus directory I create a directory called "Build". I run configure and make from the Build directory. This allows me to remove everything under the Build directory without worrying that I have removed something vital. My configure command usually looks like the following: ../jazzplusplus/trunk/jazz/configure --prefix=/home/pstieber/Jazz++/TestInstall --enable-alsa --enable-sequencer2 That should all be on one line. Also note that if you only check out the trunk, the path to configure would be shorter... ../jazz/configure --prefix=/home/pstieber/Jazz++/TestInstall --enable-alsa --enable-sequencer2 Notice the --prefix option. Instead of using the default value (/usr/local) I let the installer create yet another directory in parallel with Build and the source directory. If you do the same, you can run "make install" without root privilege and it will install the code under your home directory. The binary (jazz) should end up in $HOME/Jazz++/TestInstall/bin. If not, something is wrong. You will also notice a directory called $HOME/Jazz++/TestInstall/share that contains the configuration files. If my guess is correct and you you set the prefix option to /usr/local/bin you may also have a /usr/local/bin/share directory that should be in /usr/local/share. Since this install is under your directory structure, you have permission to remove it, making an uninstall a snap. Simply add the bin directory to your PATH and you can you it from it from any directory. RV> but it actually put a RV> binary in /usr/local/bin/bin. I hope my guess above and explanation will help you with this. RV> I copied the binary into /usr/local/bin and ran it. RV> It seems to have a problem locating its own RV> configuration file. I haven't put much effort into this yet, but I thought I had some code in Jazz++ to prompt you for the location of the configuration file. This information is stored in a Jazz++ rc file that should find the configuration information on successive invocations (if it hasn't moved). RV> (A couple of screen shots attached. Don't know if RV> they'll get through on this list.) I administer the list and approved your post so they should have ;-) RV> Looks like a good start. Thanks and thanks for trying the build. Look for more subversion updates. Pete |
×
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