--- On Fri, 9 Sep 2011 21:24:03 "D. Michael McIntyre" 
<michael.mcint...@rosegardenmusic.com> wrote:
> I had this working perfectly there for awhile, but at some
> point I screwed 
> something up, and now Rosegarden will compile against 4.7,
> but fails to link.  
> I never did sort that out, I'm afraid to say.  Still,
> I had it all working 
> once, and I'm sure the problem can be solved for less
> effort than upgrading 
> your entire system.

A while back, I did have multiple versions of QT's on a machine.  The only 
thing it would work for me (either runtime, or development) is I have to run my 
own shell command to setup the proper PATH, and LD_LIBRARY_PATH:

   .  /home/userid/bin/setEnvQT451.bash


   .  /home/userid/bin/setEnvQT471.bash

Note the "." at the start of the command, which will take effect in the current 
command-shell (at least with Bash shell).  I don't remember if QT_DIR, or QTDIR 
was needed, so I set both.

The following example of /home/userid/bin/setEnvQT471.bash , I also have my 
own, separate copy of QtCreator 2.0.1, :

#!/bin/bash -x

export QT_DIR=/home/userid/compile/qt-4.7.1
export QTDIR=/home/userid/compile/qt-4.7.1
export QMAKESPEC=${QTDIR}/mkspecs/linux-g++



export PATH=$PATH


So after running 

   .  /home/userid/bin/setEnvQT471.bash

from the command line, I keep that command line to launch 

    qtcreator &

or my QT-runtime app, which works with the specific PATH, LD_LIBRARY_PATH I 
need for that version of QT.

Similar usage could be done for multiple runtime environments (if I want to run 
multiple versions of my own app separately).

> Or you could just upgrade.  Karmic is obsolete, and no
> longer supported by 
> Ubuntu.  You could probably upgrade it to LTS
> relatively easily, being the 
> next step in line, and then you could build Rosegarden from
> there without any 
> further ado.
> -- 
> D. Michael McIntyre

Most folks keep only one copy of Linux installed on their system.  Upgrading 
would be a huge pain, and potentially be crippling for a few days (even 1-2 
weeks) while configuring the new installation.  The more important apps get 
used first, and less important apps may not get used until a week or two later 
and need time to tweak...

My way around that is to have a separate partition of about 20-30 GB of space 
for each Linux installation (full install, not using separate /home mount 
point).  So each copy of some some Linux variation, or version could function 
independently.  This way, I can switch to my old installation when I needed 
something done right away.  In the mean time, I can take my time to tweak some 
newly installed Linux distro, or version at my own pace, I can mount the other 
installed Linux partitions as read-only so I can even compare configuration 
files, like


Of course, I keep data files in its own partition(s), and mount those 
partitions from each Linux install (at boot time, or as needed).

I have used such setup when I need to try "distro hopping", or when I want to 
try a new version of my preferred distro.  It helps me quite abit.  Of course, 
I have to be mindful of which partion has which Linux flavor and version.

Perhaps this kind of setup would help some folks out there.  It doubles as my 
"instant backup" if I messed up in one Linux partition, I can boot up to the 
other Linux partition, which has all my apps already installed and configured.  
May not be too practical for older laptops because of limited diskpace, but 
works well if you can spare the disk space.  Enjoy.


BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
Learn about the latest advances in developing for the 
BlackBerry&reg; mobile platform with sessions, labs & more.
See new tools and technologies. Register for BlackBerry&reg; DevCon today!
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe

Reply via email to