A
Andrey Orlenko 1038630570
Guest
Can I compile SKILL-code to binary file ? How to make it ?
--
Andrey Orlenko
ICQ# 157544292
e-mail: eagle@ukr.net
--
Andrey Orlenko
ICQ# 157544292
e-mail: eagle@ukr.net
Navigation
Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
More options
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
G
George Patrick
Guest
Andrey Orlenko 1038630570 wrote:
No.Can I compile SKILL-code to binary file ? How to make it ?
A
Andrey Orlenko 1038630570
Guest
George Patrick wrote:
of file). For exaple, I've got Design Kit with binary skill-code ...
--
Andrey Orlenko
ICQ# 157544292
e-mail: eagle@ukr.net
But I've seen some working skill-programms in binary mode (not text viewAndrey Orlenko 1038630570 wrote:
Can I compile SKILL-code to binary file ? How to make it ?
No.
of file). For exaple, I've got Design Kit with binary skill-code ...
--
Andrey Orlenko
ICQ# 157544292
e-mail: eagle@ukr.net
K
Kholdoun TORKI
Guest
This is encrypted Skill using the Skill function encrypt()
================================================================
Kholdoun TORKI
http://cmp.imag.fr
================================================================
Andrey Orlenko 1038630570 wrote:
================================================================
Kholdoun TORKI
http://cmp.imag.fr
================================================================
Andrey Orlenko 1038630570 wrote:
George Patrick wrote:
Andrey Orlenko 1038630570 wrote:
Can I compile SKILL-code to binary file ? How to make it ?
No.
But I've seen some working skill-programms in binary mode (not text view
of file). For exaple, I've got Design Kit with binary skill-code ...
A
Andrew Beckett
Guest
Perhaps you're thinking of either encrypted files, or context files.
See the SKILL Language User Guide, Chapter 10, "Delivering Products".
Andrew.
On Tue, 02 Mar 2004 17:21:32 +0200, Andrey Orlenko 1038630570
<eagle@quad.ntu-kpi.kiev.ua> wrote:
Andrew Beckett
Senior Technical Leader
Custom IC Solutions
Cadence Design Systems Ltd
See the SKILL Language User Guide, Chapter 10, "Delivering Products".
Andrew.
On Tue, 02 Mar 2004 17:21:32 +0200, Andrey Orlenko 1038630570
<eagle@quad.ntu-kpi.kiev.ua> wrote:
--George Patrick wrote:
Andrey Orlenko 1038630570 wrote:
Can I compile SKILL-code to binary file ? How to make it ?
No.
But I've seen some working skill-programms in binary mode (not text view
of file). For exaple, I've got Design Kit with binary skill-code ...
Andrew Beckett
Senior Technical Leader
Custom IC Solutions
Cadence Design Systems Ltd
B
Bernd Fischer
Guest
SKILL is an interpreter programming language therefore
you can not create executable binaries like you are used
with non interpreter programming languages like C.
But there are ways to, lets say to convert your SKILL code.
1. Use the SKILL function 'encrypt' to encrypt your SKILL
text file. Refer to the docs for more details.
Note: If you want to protect your SKILL code use always
the password argument for the 'encrypt' function.
There is flying some code around which otherwise can
decrypt it.
Encrypted SKILL files can be treated like text SKILL
files, use the 'load' function to make the code present.
2. You can build a context file form you SKILL code.
A context file has to be loaded with the 'loadContext'
function without extension and in general it should
have the extension *.cxt.
I have never done that, so for more details refer to
the docs again.
Bernd
Andrey Orlenko 1038630570 wrote:
you can not create executable binaries like you are used
with non interpreter programming languages like C.
But there are ways to, lets say to convert your SKILL code.
1. Use the SKILL function 'encrypt' to encrypt your SKILL
text file. Refer to the docs for more details.
Note: If you want to protect your SKILL code use always
the password argument for the 'encrypt' function.
There is flying some code around which otherwise can
decrypt it.
Encrypted SKILL files can be treated like text SKILL
files, use the 'load' function to make the code present.
2. You can build a context file form you SKILL code.
A context file has to be loaded with the 'loadContext'
function without extension and in general it should
have the extension *.cxt.
I have never done that, so for more details refer to
the docs again.
Bernd
Andrey Orlenko 1038630570 wrote:
Can I compile SKILL-code to binary file ? How to make it ?
F
F ogh
Guest
Andrey Orlenko 1038630570 wrote:
What do you want to achieve actually ? performance or obfuscation ?
is encrypt, as mentioned before.Can I compile SKILL-code to binary file ? How to make it ?
I believe the drcExtractRules() does more or less that. Otherwise there
What do you want to achieve actually ? performance or obfuscation ?
A
Andrey Orlenko 1038630570
Guest
Andrey Orlenko 1038630570 wrote:
--
Andrey Orlenko
Ukraine, Kiev
ICQ# 157544292
e-mail: eagle@ukr.net
http://flying.h11.ru/
Ok, I understood it - Thanks !!!Can I compile SKILL-code to binary file ? How to make it ?
--
Andrey Orlenko
Ukraine, Kiev
ICQ# 157544292
e-mail: eagle@ukr.net
http://flying.h11.ru/
J
John Gianni
Guest
Bernd Fischer <bernd.fischer@xignal.de> wrote in message news:<4044C3B2.6030700@xignal.de>...
jjg
---------------------------------------------------------------------
A quick step-by-step Hello-World SKILL coding/encryption walk-thru
---------------------------------------------------------------------
1. First, you _should_ name both the IL file and all the SKILL
procedures defined inside starting with an upper-case prefix,
e.g., create a file named:
/tmp/MyHelloWorld.il
Which consist of, for example, this simple common test procedure:
procedure(MyTestProc()
printf("Hello World\n");
);end of my test procedure
Note: Cadence strongly recommends Customers and Application
personnel make use of upper-case prefixes while Cadence
applications (shipped on the software CDROM) use only
lower-case prefixes. Private functions should begin with
both an underscore and a prefix. This allows the user to
easily identify, on sight, the support status of a function.
---------------------------------------------------------------------
2. Cut and paste these simple examples below to run your first SKILL:
Start any DFII executable; load & run the desired procedure, e.g.:
csh% skill
csh% icfb
CIW: load("/tmp/MyHelloWorld.il")
CIW: MyTestProc()
This should execute the SKILL procedure & print the message.
CIW: exit
Or, for non-graphical applications, use 'nograph' options, e.g.:
csh% icfb -nograph
csh% icfb -ilLoadIL /dev/null -nograph -log /tmp/Log$$
csh% icfb -ilLoadIL /tmp/MyHelloWorld.il -nograph -log /tmp/Log$$
csh% cat > /tmp/MyTest.il <<EOF
load("/tmp/MyHelloWorld.il")
MyTestProc()
EOF
Then, use that batch file in a DFII non-graphical session, e.g.:
csh% icfb -replay /tmp/MyTest.il -nograph -log /tmp/Log$$
This should execute the SKILL procedure & print the message
into the desired log file (the $$ appends the process id).
In a batch session, if you don't want the .cdsinit file loaded, use:
csh% icfb -replay MyTest.il -cdshi_nocdsinit -nograph -log Log$$
This should execute the SKILL procedure & print the message
into the desired log file.
---------------------------------------------------------------------
3. In addition, you can add security via encryption or context files:
A simple example of encrypting your SKILL code, for example, is:
csh% skill
Note: Test by loading and executing the encrypted SKILL file:
csh% icfb -nograph
csh% icfb -nograph
Note: Test by loading the encrypted SKILL file with the password:
csh% icfb -nograph
procedure(MyBuildContext(MyContext)
setContext(MyContext)
sstatus(writeProtect t)
loadi(strcat(MyContext ".il"))
saveContext(strcat(MyContext ".cxt"))
callInitProc(MyContext)
)
MyBuildContext("MyHelloWorld")
exit
EOF
Note: This should create a '/tmp/MyBuildContext.il' SKILL file.
Then, create a simple IL context out of that file above:
csh% icfb -ilLoadIL /tmp/MyBuildContext.il -nograph -log /tmp/Log$$
This command should create a 'MyHelloWorld.cxt' context file.
Which you can test after loading the context into your session:
csh% icfb -nograph
John Gianni
I posted this howto long ago, but it's germane to this conversation:1. Use the SKILL function 'encrypt' to encrypt your SKILL
2. You can build a context file form you SKILL code.
jjg
---------------------------------------------------------------------
A quick step-by-step Hello-World SKILL coding/encryption walk-thru
---------------------------------------------------------------------
1. First, you _should_ name both the IL file and all the SKILL
procedures defined inside starting with an upper-case prefix,
e.g., create a file named:
/tmp/MyHelloWorld.il
Which consist of, for example, this simple common test procedure:
procedure(MyTestProc()
printf("Hello World\n");
);end of my test procedure
Note: Cadence strongly recommends Customers and Application
personnel make use of upper-case prefixes while Cadence
applications (shipped on the software CDROM) use only
lower-case prefixes. Private functions should begin with
both an underscore and a prefix. This allows the user to
easily identify, on sight, the support status of a function.
---------------------------------------------------------------------
2. Cut and paste these simple examples below to run your first SKILL:
Start any DFII executable; load & run the desired procedure, e.g.:
csh% skill
Or use any DFII graphical executable, e.g.:load("/tmp/MyHelloWorld.il")
MyTestProc()
This should execute the SKILL procedure & print the message.
exit
csh% icfb
CIW: load("/tmp/MyHelloWorld.il")
CIW: MyTestProc()
This should execute the SKILL procedure & print the message.
CIW: exit
Or, for non-graphical applications, use 'nograph' options, e.g.:
csh% icfb -nograph
Or, if you do not need contexts to be autoloaded, skip them using:load("/tmp/MyHelloWorld.il")
MyTestProc()
This should execute the SKILL procedure & print the message.
exit
csh% icfb -ilLoadIL /dev/null -nograph -log /tmp/Log$$
Or, if you wish to load the test file for immediate execution:load("/tmp/MyHelloWorld.il")
MyTestProc()
This should execute the SKILL procedure & print the message.
exit
csh% icfb -ilLoadIL /tmp/MyHelloWorld.il -nograph -log /tmp/Log$$
Or, if desired, create a batch test-sequence file to run in toto:MyTestProc()
This should execute the SKILL procedure & print the message.
exit
csh% cat > /tmp/MyTest.il <<EOF
load("/tmp/MyHelloWorld.il")
MyTestProc()
EOF
Then, use that batch file in a DFII non-graphical session, e.g.:
csh% icfb -replay /tmp/MyTest.il -nograph -log /tmp/Log$$
This should execute the SKILL procedure & print the message
into the desired log file (the $$ appends the process id).
In a batch session, if you don't want the .cdsinit file loaded, use:
csh% icfb -replay MyTest.il -cdshi_nocdsinit -nograph -log Log$$
This should execute the SKILL procedure & print the message
into the desired log file.
---------------------------------------------------------------------
3. In addition, you can add security via encryption or context files:
A simple example of encrypting your SKILL code, for example, is:
csh% skill
"MyHelloWorld.ile".encrypt("/tmp/MyHelloWorld.il" "/tmp/MyHelloWorld.ile")
exit
Note: This should create the encrypted IL file:
Note: Test by loading and executing the encrypted SKILL file:
csh% icfb -nograph
A simple example of encrypting to a password is shown below:load("/tmp/MyHelloWorld.ile")
MyTestProc()
This should print the desired message.
exit
csh% icfb -nograph
"MyHelloWorld.ile".encrypt("/tmp/MyHelloWorld.il" "/tmp/MyHelloWorld.ile" "Fun2Win")
exit
Note: This should create the password-protected encrypted file:
Note: Test by loading the encrypted SKILL file with the password:
csh% icfb -nograph
csh% cat > MyBuildContext.il <<EOFload("/tmp/MyHelloWorld.ile" "Fun2Win")
MyTestProc()
This should print the desired message.
exit
A simple example of incorporating your SKILL code into a context file:
procedure(MyBuildContext(MyContext)
setContext(MyContext)
sstatus(writeProtect t)
loadi(strcat(MyContext ".il"))
saveContext(strcat(MyContext ".cxt"))
callInitProc(MyContext)
)
MyBuildContext("MyHelloWorld")
exit
EOF
Note: This should create a '/tmp/MyBuildContext.il' SKILL file.
Then, create a simple IL context out of that file above:
csh% icfb -ilLoadIL /tmp/MyBuildContext.il -nograph -log /tmp/Log$$
This command should create a 'MyHelloWorld.cxt' context file.
Which you can test after loading the context into your session:
csh% icfb -nograph
This should execute the SKILL procedure & print the message.loadContext("MyHelloWorld.cxt")
MyTestProc()
Please improve so that others benefit.exit
---------------------------------------------------------------------
John Gianni