| Anonymous | Login | 2022-01-22 03:18 UTC |  |
| My View | View Issues | Change Log | Roadmap |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0000812 | OMNeT++ | IDE / other | public | 2015-02-23 10:25 | 2017-02-06 10:18 | ||||
| Reporter | till | ||||||||
| Assigned To | rhornig | ||||||||
| Priority | low | Severity | feature | Reproducibility | always | ||||
| Status | resolved | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | 4.6 | ||||||||
| Target Version | Fixed in Version | 5.1pre3 | |||||||
| Summary | 0000812: Make oppfeature dependencies project independent | ||||||||
| Description | It would be really nice for the user when the developers could specify feature dependencies for features in other projects. For example: we require certain modules of INET to make our features work. We even have project dependencies like that: Our Simulation -> Some complex Gateway Model -> A Basic Real-Time Ethernet Model -> INET Framework | ||||||||
| Additional Information | This would probably require some sort of namespace for the features: e.g. inet.Ethernet and the ability to find features in referenced projects. Perhaps something like: <ext-feature ns="inet.*" name="INET Framework" description = "Download at http://github.com/inet-framework/"/> [^] Would also help. The IDE could then display a nice message: "This feature requires features from INET Framework - Download at http://github.com/inet-framework/" [^] | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
|
(0000985) andras (administrator) 2015-02-23 15:09 |
Makes sense, thank you for the suggestion! |
|
(0001169) rhornig (administrator) 2016-03-04 10:25 |
Cross project dependency checking is now possible with the new opp_featuretool's 'isenabled' command. The tool can generate an include file which contains all the defined macros for the enabled features. You still have to watch for feature name clashes + not all features define a macro, but it's possible to check for the features on command line (and in the makefile of course). |
|
(0001250) rhornig (administrator) 2017-01-12 17:05 |
This can be implemented by the model using the opp_featuretool by checking if required features are enabled in an other project. This should be implemented in a makefrag file or in a separate top level makefile. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2015-02-23 10:25 | till | New Issue | |
| 2015-02-23 15:09 | andras | Note Added: 0000985 | |
| 2015-10-12 09:28 | ammmar1988 | Issue cloned: 0000865 | |
| 2016-03-04 10:25 | rhornig | Note Added: 0001169 | |
| 2016-03-04 10:25 | rhornig | Status | new => postponed |
| 2016-03-04 10:25 | rhornig | Fixed in Version | => 5.0 |
| 2016-03-04 10:25 | rhornig | Resolution | open => suspended |
| 2016-03-04 10:25 | rhornig | Assigned To | => rhornig |
| 2017-01-12 17:05 | rhornig | Note Added: 0001250 | |
| 2017-01-12 17:05 | rhornig | Status | postponed => resolved |
| 2017-01-12 17:05 | rhornig | Fixed in Version | 5.0 => 5.1 |
| 2017-01-12 17:06 | rhornig | Resolution | suspended => fixed |
| 2017-02-06 10:18 | rhornig | Fixed in Version | 5.1 => 5.1pre3 |
|
Issue History |
| Copyright © 2000 - 2022 MantisBT Team |
 |