Project Home
Project Home		 Source Code
Source Code		 Documents
Documents		 Wiki
Wiki		 Discussion Forums
Discussions		 Project Information
Project Info
Core Development Tools/Discussion/General/Co-existence of 6.3.2 and 6.4 on a Linux Host/List of Posts
Forum Topic - Co-existence of 6.3.2 and 6.4 on a Linux Host: (5 Items)
   
Update
Rajat Jain
10/01/2008 2:32 AM
post14290
Co-existence of 6.3.2 and 6.4 on a Linux Host   
Hi,

I'm using a Red Hat Linux Host and have installed 6.4 development environment to compile the latest 6.4 BSPs. 

However, I want to install 6.3.2 environment as well to compile certain old code. Will I be able to install 6.3.2 on the
 host without disturbing anything related to 6.4? 

While compilation (and I ALWAYS use command line - not IDE), how do I tell which one to use? Which one will be the 
default?

Thanks,

Rajat
Aleksandar Ristovski(deleted)
10/02/2008 11:31 PM
post14391
Re: Co-existence of 6.3.2 and 6.4 on a Linux Host   
For command line builds, you need to make sure the following env. variables are pointing to the right directories:
QNX_HOST, QNX_TARGET, MAKEFLAGS and PATH. See your /etc/profile to see how is our installer setting them up.

You can change them "manually" to 632 or 640 depending which version you need.

I have both 6.3.2 and 6.4.0 on my linux machine and they do not interfere with each other.
Dell Drummond(deleted)
10/21/2008 9:12 AM
post15311
Re: Co-existence of 6.3.2 and 6.4 on a Linux Host   
You can also use qconfig. 

Here is the use message:

%C - Query and Display all QNX installs/configurations

%C [-d <path>] [-n <install name>] [-l|-i|-e|-a] [-bp] [-h]

Where:
    -d <path>           Specifies QNX_CONFIGURATION directory.
    -n <install_name>   Select a specific installation by name. 
    -l                  List all installs in human readable format (default).
    -a                  List all installs in a new easy-to-parse form.
    -b                  When used with -l or -a only list base installs.
    -p                  When used with -l or -a only list additional product installs. 
    -e                  Used to setup runtime environment (see examples).
    -c                  Print runtime environment strings in csh style.
    -i                  List all installs in easy-to-parse form.
    -r <program>        Run the given program with the proper environment.


Notes:

    This utility needs to know where to find the per-install configuration
files.  It first attempts to use the environment variable QNX_CONFIGURATION,
and then looks for the -d option to override it.  If neither of these produce
a valid location it will fall back to looking in /etc/qnx/qconfig/ before 
giving up and returning an error.
   
    If no install is given (-n), then qconfig will use the most current version
that it can find.


Examples:

    List all the QNX installations:
        qconfig

    Setup your shell environment for a specific install:
        eval `qconfig -n "QNX 6.3.0 Install" -e`

    Run a specific instance of qde (the IDE).
        qconfig -n "QNX 6.3.0 Install" -r qde
Colin Burgess(deleted)
10/21/2008 9:19 AM
post15313
Re: Co-existence of 6.3.2 and 6.4 on a Linux Host   
That's great if you can actually install the darned thing - I don't think the installer will let you install two 
different installs?

I just copied /opt/qnx632 over from another machine and have a shell script which sets up my environment variables 
(qconfig could do that, I guess)

Dell Drummond wrote:
> You can also use qconfig. 
> 
> Here is the use message:
> 
> %C - Query and Display all QNX installs/configurations
> 
> %C [-d <path>] [-n <install name>] [-l|-i|-e|-a] [-bp] [-h]
> 
> Where:
>     -d <path>           Specifies QNX_CONFIGURATION directory.
>     -n <install_name>   Select a specific installation by name. 
>     -l                  List all installs in human readable format (default).
>     -a                  List all installs in a new easy-to-parse form.
>     -b                  When used with -l or -a only list base installs.
>     -p                  When used with -l or -a only list additional product installs. 
>     -e                  Used to setup runtime environment (see examples).
>     -c                  Print runtime environment strings in csh style.
>     -i                  List all installs in easy-to-parse form.
>     -r <program>        Run the given program with the proper environment.
> 
> 
> Notes:
> 
>     This utility needs to know where to find the per-install configuration
> files.  It first attempts to use the environment variable QNX_CONFIGURATION,
> and then looks for the -d option to override it.  If neither of these produce
> a valid location it will fall back to looking in /etc/qnx/qconfig/ before 
> giving up and returning an error.
>    
>     If no install is given (-n), then qconfig will use the most current version
> that it can find.
> 
> 
> Examples:
> 
>     List all the QNX installations:
>         qconfig
> 
>     Setup your shell environment for a specific install:
>         eval `qconfig -n "QNX 6.3.0 Install" -e`
> 
>     Run a specific instance of qde (the IDE).
>         qconfig -n "QNX 6.3.0 Install" -r qde
>    
> 
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post15311
> 

-- 
cburgess@qnx.com
Natalia Miyusova
10/21/2008 10:03 AM
post15326
Re: Co-existence of 6.3.2 and 6.4 on a Linux Host   
Co-existence of 6.3.2 and 6.4.0 on Linux is officially supported.

Installation of 6.4.0 after 6.3.2 is installed has been fully tested.

There should not be any problems installing in reverse order - 6.3.2 after 6.4.0 is installed.  The installer supports 
these scenario.  

However, if you decide to uninstall 6.3.2 while 6.4.0 is still installed, you'll need to start the uninstaller with the 
following argument:

./uninstaller.bin -W beanDeleteConfigDir.active="False"

Otherwise, the installation of 6.4.0 will be corrupted.

Natalia

Return


  A subsidiary of BlackBerry             All content ©2004-2013, QNX Software Systems