[aadl-modeling]: AADL library

David K fux1235 at googlemail.com
Mon May 14 05:05:18 EDT 2018


Thank you for your answer. This works exactly as I wanted.

Kind regards
David

2018-05-09 14:58 GMT+02:00 Philip Alldredge <pwa0001 at uah.edu>:

> What I would recommend is having an AADL Project which will contain all
> your library packages/property sets and referencing it from your other
> projects. To do this, you'll need to add a reference to the library project
> from any project that needs to use it.
> - Right click on the non-library project and select Properties to open the
> properties dialog.
> - Select Project References
> - Check the library project.
>
> At that point, you should be able to reference any of the packages or
> property sets which are located in the library project.
>
> Please note that for OSATE specific questions would probably be best
> suited for the OSATE google group at https://groups.google.com/
> forum/#!forum/osate.
>
> Philip Alldredge
> Research Scientist
> Rotorcraft Systems Engineering and Simulation Center
> University of Alabama in Huntsville
> VBRH A-4
> 256-824-4837
> Philip.Alldredge at uah.edu
>
> On Wed, May 9, 2018 at 7:42 AM, David K <fux1235 at googlemail.com> wrote:
>
>> Good afternoon,
>>
>> I have a short question about librarys. Is it possible to create a
>> library of components which could be used in different AADL-projects in
>> OSATE. I scanned the standard document and the book "Model Based
>> Engineering with AADL" for it and found nothing. The book only describes
>> how it works in one specific project (if I understand it right) but not for
>> several projects. The only way I found was putting the relevant files for
>> the library in the "Plugin_Contributions" in OSATE which I assume isn't the
>> right way to do it.
>>
>>
>> Kind regards
>> David Kupper
>>
>
>
-------------- next part --------------
HTML attachment scrubbed and removed


More information about the aadl-modeling mailing list