cds.lib not in start directory

[Guenther Sohler]

Is it possible to tell icfb not to
use/create the ceds.lib in the start directory, but using on in another
path eg
CDS_WORKAREA ?


In my place it always creates a new cds.lib including the global one.
This is not the expected behaviour. can this be changed ?

 

[Bernd Fischer]

ddSetForcedLib( strcat( getShellEnvVar( "CDS_WORKAREA" ) "/cds.lib" ) )
ddUpdateLibList( )

Bernd

Guenther Sohler wrote:

Is it possible to tell icfb not to
use/create the ceds.lib in the start directory, but using on in another
path eg
CDS_WORKAREA ?


In my place it always creates a new cds.lib including the global one.
This is not the expected behaviour. can this be changed ?

 

[Roger Light]

Guenther Sohler wrote:

Is it possible to tell icfb not to
use/create the ceds.lib in the start directory, but using on in another
path eg
CDS_WORKAREA ?

Alternatively to what Bernd said, create an alias/script so that you cd
to CDS_WORKAREA first and then run icfb. This not only prevents the
cds.lib being recreated but also keeps any temporary/log files in the
same working directory.

What we do is something like:

#!/bin/bash

source /appropriate/config/files

cd $CDS_WORKAREA
icfb

#

Hope that helps,

Roger

 

[Trevor Bowen]

crude, but effective... alias/append icfb command:

icfb -cdslib $CDS_WORKAREA/cds.lib

Guenther Sohler wrote:

Is it possible to tell icfb not to
use/create the ceds.lib in the start directory, but using on in another
path eg
CDS_WORKAREA ?


In my place it always creates a new cds.lib including the global one.
This is not the expected behaviour. can this be changed ?