[Openroad-users] Included applications

[Simon Lovell]

This can be done in theory by making the calls in the common_frames application dynamic i.e.:

lv_call = 'frame_in_app_a';
callframe :lv_call();

However, it would be easier to just ensure that all the programs called by common_frames are included in that application.  A compiler warning is issued when a frame is called which doesn't exist.  Is there a reason this is not possible?

HTH

-----Original Message-----
From: "Allan Biggs" [Allan.Biggs at gbr.dupont.com]
Date: 26/01/2007 11:28 PM

We are trying to split an application into its 2 component applications application_a and application_p and a common set of frames - hopefully this will reduce maintenance and implementation issues in the future. 

What we have discovered is that to call a frame in  the common_frames app from application_a or application_p we have to include both application_a_objects and application_p_objects  in the common_frames application as well as in their parent applications.  [Frames in the common_frames app use objects also used by the main application] 

application_a 
    (included apps) 
    common_frames 
    application_a_objects 

application_p 
    (included apps) 
    common_frames 
    application_p_objects 



common_frames 
    (included apps) 
    common_objects 
    application_a_objects 
    application_p_objects 


This is fine for development but I perceive an issue when we come to create an image of application_a and application_p; reading the user guide the only way I can see of doing this is to link to the common application rather than include the common_frames.  At present we just include all applications in the combined image.   

I wonder if I am misreading this -  we would prefer to have stand-alone applications application_a and application_p  with all applications included and to avoid dynamically linking to the common_frames app. 

We are using OpenROAD 4.1/0403 on XP 

We would appreciate any pointers. 

Thanks Allan 

for anyone old enough to remember this is a similar nightmare to linking tasks for RSX11M !! 

This communication is for use by the intended recipient and contains
information that may be Privileged, confidential or copyrighted under
applicable law. If you are not the intended recipient, you are hereby
formally notified that any use, copying or distribution of this e-mail,
in whole or in part, is strictly prohibited. Please notify the sender by
return e-mail and delete this e-mail from your system. Unless explicitly
and conspicuously designated as "E-Contract Intended", this e-mail does
not constitute a contract offer, a contract amendment, or an acceptance
of a contract offer. This e-mail does not constitute a consent to the
use of sender's contact information for direct marketing purposes or for
transfers of data to third parties.

Francais Deutsch Italiano  Espanol  Portugues  Japanese  Chinese  Korean

           http://www.DuPont.com/corp/email_disclaimer.html