Load my SKILL code

Guest
Hello,

I have written a SKILL code to create menus in the CIW. But each time I
start cadence I have to load this code from the CIW.
I would like to open Cadence and the code at the same, so that I
directly get the menus I have created.
How can I do that?

(sorry for aking something that should be so easy to realise)

Thanks!
 
One of the the very many ways to do it is to add your load command for
the code in your .cdsinit file.

kirscher_jerome@yahoo.fr wrote:
Hello,

I have written a SKILL code to create menus in the CIW. But each time I
start cadence I have to load this code from the CIW.
I would like to open Cadence and the code at the same, so that I
directly get the menus I have created.
How can I do that?

(sorry for aking something that should be so easy to realise)

Thanks!
Click to expand...
 
First, in your skill code add a line to call your function at the end of
the file.

For example:
your skill code currently have
procedure(createMenu()
let(()

)
);pro

add the following line at the end of your skill
createMenu()

Second, create a file name ".cdsinit" under your working directory where
you invoke the cadence from.
In this file adding the following line:
load "path_to_skill/file_name"

where path_to_skill is where you store your skill
file_name is the name of your skill code

once you are done, you can invoke the cadence and see what happen.

Hope it helps,
Michael
 
Hi,

So, if I create a context file (or simply leave the plain skill), is
it possible for me just to create the context file somewhere and have it
auto-sourced without changing the .cdsinit?

Thanks,
Stefano

mxn731 wrote:
First, in your skill code add a line to call your function at the end of
the file.

For example:
your skill code currently have
procedure(createMenu()
let(()

)
);pro

add the following line at the end of your skill
createMenu()

Second, create a file name ".cdsinit" under your working directory where
you invoke the cadence from.
In this file adding the following line:
load "path_to_skill/file_name"

where path_to_skill is where you store your skill
file_name is the name of your skill code

once you are done, you can invoke the cadence and see what happen.

Hope it helps,
Michael
Click to expand...
 
Stefano,

can tell me the reason you don't want to load your skill in .cdsinit?
There may be other ways to solve your problem. Explain me more what you
are trying to do.

Michael
 
Hi Michael,

Thanks a lot!
The problem is that I deliver a product that installs on top of
Virtuoso. We have had many issues with people forgetting to update their
..cdsinit, making various mistakes etc. I need a way to drop a context
file somewhere in the Cadence installation so that the context is
autoloaded without requiring the user/administrator to do anything.

Regards,
Stefano

mxn731 wrote:
Stefano,

can tell me the reason you don't want to load your skill in .cdsinit?
There may be other ways to solve your problem. Explain me more what you
are trying to do.

Michael
Click to expand...
 
Stefano,

I understand your issue now. You need to put your .cdsinit in a central
place. I suggest you go to Cadence Document, see "Setting Cadence
Environment Variables" section under Cadence Design Framework II Help. It
will show you how to create and load your customized .cdsinit file in
central location.

Hope it helps,
Michael
 
Hi Michael,

I actually do not want to touch the .cdsinit at all. I want to be
able (if at all possible) to have dfII autoload a context file without
any change to the installation. If not possible, I would like to find
out the minimal change I have to do.

Thanks,
Stefano


mxn731 wrote:
Stefano,

I understand your issue now. You need to put your .cdsinit in a central
place. I suggest you go to Cadence Document, see "Setting Cadence
Environment Variables" section under Cadence Design Framework II Help. It
will show you how to create and load your customized .cdsinit file in
central location.

Hope it helps,
Michael
Click to expand...
 
Stefano,

You can try -replay option of icfb command as follow:
- Create a file my.replay in your directory and add a load command line
as below:
\a load("path_to_context/context_name")

- Your user need to invoke Cadence as follow:
icfb -replay your_directory/my.replay

Hope it helps,
Michael
 
Stefano,

I tried to reply your email but can't go through. Something wrong with you
email address. If you send me another good email address. I will reply back
to you.

Michael
 
Hi Stefano,

No, you cannot have a context auto-loaded, unless there is some definition
of an autoload property on a function, or it is explicitly loaded from the
..cdsinit file. Cadence context files auto-load because the executables are told
(in the code itself) which contexts it should auto-load, and it then uses the
..toc and .aux files to seed the autoloader. However, this mechanism can't be
used for context files for which the executable has no knowledge (such as your
own), so you have to update the .cdsinit file for this to work.

Regards,

Andrew.

On Thu, 25 Aug 2005 16:03:49 -0700, stefano zanella <stefanoDOTzanella@pdf.com>
wrote:

Hi Michael,

I actually do not want to touch the .cdsinit at all. I want to be
able (if at all possible) to have dfII autoload a context file without
any change to the installation. If not possible, I would like to find
out the minimal change I have to do.

Thanks,
Stefano


mxn731 wrote:
Stefano,

I understand your issue now. You need to put your .cdsinit in a central
place. I suggest you go to Cadence Document, see "Setting Cadence
Environment Variables" section under Cadence Design Framework II Help. It
will show you how to create and load your customized .cdsinit file in
central location.

Hope it helps,
Michael
Click to expand...
 
Hi Andrew, Everybody,

Thanks a lot for you answer.
I was afraid you would say that, so I was prepared for the worst :)

It would be great if this were possible (e.g. put a context in some
location and the executables will know about it).

Have a good week-end,
Stefano



Andrew Beckett wrote:
Hi Stefano,

No, you cannot have a context auto-loaded, unless there is some definition
of an autoload property on a function, or it is explicitly loaded from the
.cdsinit file. Cadence context files auto-load because the executables are told
(in the code itself) which contexts it should auto-load, and it then uses the
.toc and .aux files to seed the autoloader. However, this mechanism can't be
used for context files for which the executable has no knowledge (such as your
own), so you have to update the .cdsinit file for this to work.

Regards,

Andrew.

On Thu, 25 Aug 2005 16:03:49 -0700, stefano zanella <stefanoDOTzanella@pdf.com
wrote:


Hi Michael,

I actually do not want to touch the .cdsinit at all. I want to be
able (if at all possible) to have dfII autoload a context file without
any change to the installation. If not possible, I would like to find
out the minimal change I have to do.

Thanks,
Stefano


mxn731 wrote:

Stefano,

I understand your issue now. You need to put your .cdsinit in a central
place. I suggest you go to Cadence Document, see "Setting Cadence
Environment Variables" section under Cadence Design Framework II Help. It
will show you how to create and load your customized .cdsinit file in
central location.

Hope it helps,
Michael
Click to expand...
 
Stefano,

you want to plae your code in "central" place. I suppose you mean that it is a
place where only administrator can write and where all users can read. The only
such place that you know about in your client site, is the cadence install. If
you deliver you product as a context file, you will be bound to the exact IC
version, so I suggest you install your cxt file and the skill snippet that loads
it directly in the IC install tree. You should make some install scripts with
enough intelligence to modify or create the tools/dfII/local/.cdsinit , so that
a normal sysadmin can install your package. And also document what the install
scripts do, so that an EDA AE can make a custom install.

If you want to make things nicer, you can use the autoload mecanism, instead
of loading your cxt at startup. A little more than dropping the cxt file in a
directory is involved, but it is simple and documented in the SKILL UG.


stefano zanella wrote:

Hi Andrew, Everybody,

Thanks a lot for you answer.
I was afraid you would say that, so I was prepared for the worst :)

It would be great if this were possible (e.g. put a context in some
location and the executables will know about it).

Have a good week-end,
Stefano



Andrew Beckett wrote:

Hi Stefano,

No, you cannot have a context auto-loaded, unless there is some
definition
of an autoload property on a function, or it is explicitly loaded from
the
.cdsinit file. Cadence context files auto-load because the executables
are told
(in the code itself) which contexts it should auto-load, and it then
uses the
.toc and .aux files to seed the autoloader. However, this mechanism
can't be
used for context files for which the executable has no knowledge (such
as your
own), so you have to update the .cdsinit file for this to work.

Regards,

Andrew.

On Thu, 25 Aug 2005 16:03:49 -0700, stefano zanella
stefanoDOTzanella@pdf.com
wrote:


Hi Michael,

I actually do not want to touch the .cdsinit at all. I want to be
able (if at all possible) to have dfII autoload a context file
without any change to the installation. If not possible, I would like
to find out the minimal change I have to do.

Thanks,
Stefano


mxn731 wrote:

Stefano,

I understand your issue now. You need to put your .cdsinit in a central
place. I suggest you go to Cadence Document, see "Setting Cadence
Environment Variables" section under Cadence Design Framework II
Help. It
will show you how to create and load your customized .cdsinit file in
central location.

Hope it helps,
Michael
Click to expand...
 
Hi All,

Thanks a lot for all your suggestions. I think I have enough food for
thought :)

Thanks,
Stefano

PS: we already do autoloading

fogh wrote:
Stefano,

you want to plae your code in "central" place. I suppose you mean that
it is a place where only administrator can write and where all users can
read. The only such place that you know about in your client site, is
the cadence install. If you deliver you product as a context file, you
will be bound to the exact IC version, so I suggest you install your cxt
file and the skill snippet that loads it directly in the IC install
tree. You should make some install scripts with enough intelligence to
modify or create the tools/dfII/local/.cdsinit , so that a normal
sysadmin can install your package. And also document what the install
scripts do, so that an EDA AE can make a custom install.

If you want to make things nicer, you can use the autoload mecanism,
instead of loading your cxt at startup. A little more than dropping the
cxt file in a directory is involved, but it is simple and documented in
the SKILL UG.


stefano zanella wrote:

Hi Andrew, Everybody,

Thanks a lot for you answer.
I was afraid you would say that, so I was prepared for the worst :)

It would be great if this were possible (e.g. put a context in some
location and the executables will know about it).

Have a good week-end,
Stefano



Andrew Beckett wrote:

Hi Stefano,

No, you cannot have a context auto-loaded, unless there is some
definition
of an autoload property on a function, or it is explicitly loaded
from the
.cdsinit file. Cadence context files auto-load because the
executables are told
(in the code itself) which contexts it should auto-load, and it then
uses the
.toc and .aux files to seed the autoloader. However, this mechanism
can't be
used for context files for which the executable has no knowledge
(such as your
own), so you have to update the .cdsinit file for this to work.

Regards,

Andrew.

On Thu, 25 Aug 2005 16:03:49 -0700, stefano zanella
stefanoDOTzanella@pdf.com
wrote:


Hi Michael,

I actually do not want to touch the .cdsinit at all. I want to be
able (if at all possible) to have dfII autoload a context file
without any change to the installation. If not possible, I would
like to find out the minimal change I have to do.

Thanks,
Stefano


mxn731 wrote:

Stefano,

I understand your issue now. You need to put your .cdsinit in a
central
place. I suggest you go to Cadence Document, see "Setting Cadence
Environment Variables" section under Cadence Design Framework II
Help. It
will show you how to create and load your customized .cdsinit file in
central location.

Hope it helps,
Michael
Click to expand...
 
You must log in or register to reply here.

Welcome to EDABoard.com

Sponsor

Back
Top