Bug 497243 - Command line code generator must support externalized profile applications
Summary: Command line code generator must support externalized profile applications
Status: UNCONFIRMED
Alias: None
Product: Papyrus-rt
Classification: Modeling
Component: codegen (show other bugs)
Version: 0.7.2   Edit
Hardware: All All
: P3 normal
Target Milestone: Future   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-04 10:52 EDT by Peter Cigehn CLA
Modified: 2016-10-31 14:25 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Cigehn CLA 2016-07-04 10:52:57 EDT 
As discussed in Bug 496299 Comment 20, the code generator must support the case when profile applications have been externalized into own resources. In general it should be supported for any profile, but a good example is probably the externalization of the RtCppProperties profile, to be able to generate different code depending on which target or deployment configuration that the code is generated for.

Which externalized profile application to use for a specific build needs to be specified in some way, e.g. using a command line option to the code-generator or some build configuration file (similar to the transformation configuration files in the legacy tooling, where this concept is referred to as a marking model).
Comment 1 Charles Rivet CLA 2016-09-04 20:08:02 EDT 
Currently in MVP3 plan (post v1.0).