Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic Rhapsody (steve huntington)
Decrease font size
Increase font size
Topic Title: Problem generating a COM Library
Topic Summary:
Created On: 28-Sep-2007 14:16
Status: Read Only
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 28-Sep-2007 14:16
User is offline View Users Profile Print this message


David Cunningham

Posts: 2
Joined: 28-Sep-2007

I have a model with a number of components.

Component A has (amongst other things) a Package "CustomTypes" which contains a type "BYTE" (typedef unsigned char).

Component B is a COM Library with a single Package containing a number of COM Interfaces. "CustomTypes" is not in Scope for Component B.

One of the Interfaces in Component B has a method ForceAtrLength(BYTE bLength) - BYTE in this case being the COM UI1 type not the "CustomTypes" BYTE.

"CustomTypes" is not in scope for Component B.

Component B fails to build as it generates an idl file for the interface containing ForceAtrLength with the statement "#include "CustomTypes.idl".

Any ideas how to works around this issue?

Incidently, there's a second method in Component B SetSimAtr(SAFEARRAY(BYTE)). The component builds fine if ForcesAtrLength is removed (& SetSimAtr remains).
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic Rhapsody forum.
There are currently 1 users logged in.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.