[cosmic-users] idl_to_picml problem

[Sowayan, Abdullah (N-DUA)]

Jeff, 

Great, that is awesome!!! I have one problem though. How do I get this
stuff? I tried getting it from the repository

svn checkout svn://svn.dre.vanderbilt.edu/DOC/cosmic
svn: No repository found in 'svn://svn.dre.vanderbilt.edu/DOC/cosmic'

But I was unable to. Where is the cosmic repository located?

I assume that all I have to do is to compile
CoSMIC/PIM/PICML/interpreters/IDLImporter to get the next idl_to_picml,
and that would work with CosMIC 0.4.8, right? 

If not, I guess I have to compile all of CosMIC.

Thanks a lot,
Abdul

>>-----Original Message-----
>>From: Jeff Parsons [mailto:j.parsons at vanderbilt.edu]
>>Sent: Friday, December 08, 2006 12:31 PM
>>To: Sowayan, Abdullah (N-DUA); cosmic-users at list.isis.vanderbilt.edu
>>Cc: kitty at dre.vanderbilt.edu
>>Subject: RE: [cosmic-users] idl_to_picml problem
>>
>>Hi Abdul,
>>
>>Finally got around to looking at this, just checked in
>>a fix. In a nutshell, at some point I deferred the setting
>>of the AttributeMember's "referred" GME attribute, in
>>order to catch the case where the type of an IDL
>>attribute is modified. I must have then forgot to go back
>>and test and case where the IDL attribute is added (your
>>case) or I would have found that the diagnostic output
>>for the case of adding an IDL attribute was now making
>>a call on a null pointer ;-).
>>
>>At any rate, we should now get the correct diagnostic in
>>either case, and with no abort ;-).
>>
>>The details are in the ChangeLog entry, for anyone who's
>>interested. Sorry it took so long to get to this.
>>
>>Jeff
>>
>>> -----Original Message-----
>>> From: cosmic-users-bounces at list.isis.vanderbilt.edu
>>> [mailto:cosmic-users-bounces at list.isis.vanderbilt.edu] On
>>> Behalf Of Sowayan, Abdullah (N-DUA)
>>> Sent: Tuesday, December 05, 2006 11:14 AM
>>> To: cosmic-users at list.isis.vanderbilt.edu
>>> Subject: [cosmic-users] idl_to_picml problem
>>>
>>> Sorry for cross posting. PRF says to post it here, I didn't
>>> realize that
>>> initially.
>>>
>>> ------------------------------
>>> ACE_VERSION:    5.5.4
>>> TAO_VERSION:    1.5.4
>>> CIAO_VERSION:   0.5.3
>>> GME_VERSION:    5.11.18
>>> COSMIC_VERSION: 0.4.8
>>>
>>> First, do these type of questions go to the CIAO's users group?
>>>
>>> Consider the following IDL file:
>>>
>>> --------------------------------
>>> #ifndef FOO_IDL_
>>> #define FOO_IDL_
>>>
>>> interface Foo
>>> {
>>>   void Bar();
>>>
>>>   //attribute boolean ok;
>>> };
>>>
>>> #endif /* FOO_IDL_ */
>>> ---------------------------------
>>>
>>> Initially, the attribute is commented out.
>>>
>>> I run the following command to import the IDL to PICML:
>>> C:\IDL>idl_to_picml -I. -I%ACE_ROOT% -I%ACE_ROOT%/ace -I%TAO_ROOT%
>>> -I%TAO_ROOT%/tao -I%CIAO_ROOT% -I%CIAO_ROOT%/ciao -x ABDUL Foo.idl
>>>
>>> Everything works fine. It generates ABDUL.xme which I can import
into
>>> PICML.
>>>
>>> Then, say I need to update the IDL above to add an attribute, so I
>>> remove the comment from the attribute section, then I run the
>>> following
>>> command to update the PICML model:
>>>
>>> C:\IDL>idl_to_picml -I. -I%ACE_ROOT% -I%ACE_ROOT%/ace -I%TAO_ROOT%
>>> -I%TAO_ROOT%/tao -I%CIAO_ROOT% -I%CIAO_ROOT%/ciao -i
>>> ABDUL.xme -x ABDUL2
>>> Foo.idl tao-idli_ZNBPo1.cpp Added Attribute ok in Object Foo Unknown
>>> exception in BE_produce Fatal Error - Aborting
>>>
>>>
>>> I get the error above.
>>>
>>> Is there a way to update the model, i.e., is the use case
>>> above expected
>>> to work? Or should I recreate the whole model everytime I
>>> need to add a
>>> new IDL file or modify the IDL.
>>>
>>> Thanks,
>>> Abdul
>>> _______________________________________________
>>> cosmic-users mailing list
>>> cosmic-users at list.isis.vanderbilt.edu
>>> http://list.isis.vanderbilt.edu/mailman/listinfo/cosmic-users
>>>