| Re: hiding idl code [message #6833] |
Tue, 27 August 1996 00:00 |
Robert Moss
Messages: 74
Registered: February 1996
|
Member |
|
|
Claus Hammerl wrote:
>
> Hi there,
>
> I wrote an idl application and want it to be used by others, but I
> don't want others to look at the source code ... is there any
> possibility to do a compilation and run the compiled code or do
> I always have to run IDL and read the source code to run it ...
>
> thanks in advance
>
> claus hammerl
> hammerl@physik.uni-augsburg.de
You can use something like
.RUN myapp ;compile the top of the food chain
RESOLVE_ALL ;compile all routines that are called by myapp
SAVE, /ROUTINES, FILENAME = 'myapp.sav' ;save all routines
This will create an IDL saveset called 'myapp.sav' which has all
of the compiled routines in it (see help for RESOLVE_ALL). This
is machine independent. Your customers would then use
RESTORE, FILENAME='myapp.sav'
before starting youir application. By the way, they will have to run
IDL. I believe that run-time licenses of IDL are available from
Research Systems under certain circumstances.
--
Robert M. Moss, Ph.D. - mossrm@texaco.com - FAX (713)954-6911
------------------------------------------------------------ -----
This does not necessarily reflect the opinions of Texaco Inc.
|
|
|
|
| Re: hiding idl code [message #6836 is a reply to message #6833] |
Tue, 27 August 1996 00:00  |
Phil Williams
Messages: 78
Registered: April 1996
|
Member |
|
|
Claus Hammerl wrote:
>
> Hi there,
>
> I wrote an idl application and want it to be used by others, but I
> don't want others to look at the source code ... is there any
> possibility to do a compilation and run the compiled code or do
> I always have to run IDL and read the source code to run it ...
>
> thanks in advance
>
> claus hammerl
> hammerl@physik.uni-augsburg.de
Check out the documentation for save.
Basically compile the routine then do the following:
IDL> save, filename='compiled.routines',/routines,'pro1','pro2'
to save the two compiled procedures named pro1 and pro2
Hope this helps.
--
/*********************************************************** ********/
Phil Williams, Ph.D.
Research Instructor
Children's Hospital Medical Center "One man gathers what
Imaging Research Center another man spills..."
3333 Burnet Ave. -The Grateful Dead
Cincinnati, OH 45229
email: williams@irc.chmcc.org
URL: http://scuttle.chmcc.org/~williams/
/*********************************************************** ********/
|
|
|
|
| Re: hiding idl code [message #6837 is a reply to message #6833] |
Tue, 27 August 1996 00:00 |
Christian Soeller
Messages: 46
Registered: August 1996
|
Member |
|
|
hammerl@ibm01s.RZ.Uni-Augsburg.DE (Claus Hammerl) writes:
> I wrote an idl application and want it to be used by others, but I
> don't want others to look at the source code ... is there any
Have a look at the documentation of the save procedure using the
Routines keyword. Using save/restore should achieve just what you
want and is exactly the way RSI used to hide their demo source code
from us.
Regards,
Christian
------------------------------------------------------------ --------
Christian Soeller mailto: csoelle@sghms.ac.uk
St. Georges Hospital Medical School Dept. of Pharmacology
Cranmer Terrace London SW17 0RE
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
