Cmake gave us the great power to flexibly configure many options and features of FORTE. This allows to fine tune FORTE for your specific target, mainly reducing flash and RAM footprint. However a typical FORTE user will not need most of them. Especially when starting with FORTE these options may be overwhelming. Therefore I suggest to move the following options into the advanced section:
In my point of view it should be moved also to the advanced section. It is what I would expect as user of 4DIAC. Moreove, in my point of view it doesn't make sense to have different configurations for 4DIAC-IDE (there is no support from the IDE to deactive the monitoring service and to hide it in the menu) and FORTE (configuration via cmake).
Last edit: Thomas Strasser 2014-04-28
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I also find it very useful to move the above mentioned options into the advanced section. A new and not so well informed 4DIAC user may get confused with too many options setting up the FORTE build environment.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In my opinion monitoring should also go to advanced settings. A user which needs the performance/space gains of deactivating the monitoring support is, in my opinion, an advanced user
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
To further simplify FORTE configuration I thought it is a good idea to make architecture selection possible with a combo box. Today I played a little with CMake the results can be found under [issues:#853]. I hope you like it as well.
Cmake gave us the great power to flexibly configure many options and features of FORTE. This allows to fine tune FORTE for your specific target, mainly reducing flash and RAM footprint. However a typical FORTE user will not need most of them. Especially when starting with FORTE these options may be overwhelming. Therefore I suggest to move the following options into the advanced section:
What do you think? Are these to much options or to little? Are the default values for these options already the ones most suitable for novice users?
Cheers,
Alois
I fully agree that these options should be moved to the advanced section.
Kind regards,
Martin
I also agree to move this options into the advanced section.
I agree as well ... maybe the monitoring option would be nice to stay in the default section
As monitoring is enabled per default since the last version do you think it should be in the default section?
I would now deactivate monitoring only for space sensitive devices.
In my point of view it should be moved also to the advanced section. It is what I would expect as user of 4DIAC. Moreove, in my point of view it doesn't make sense to have different configurations for 4DIAC-IDE (there is no support from the IDE to deactive the monitoring service and to hide it in the menu) and FORTE (configuration via cmake).
Last edit: Thomas Strasser 2014-04-28
I also find it very useful to move the above mentioned options into the advanced section. A new and not so well informed 4DIAC user may get confused with too many options setting up the FORTE build environment.
In my opinion monitoring should also go to advanced settings. A user which needs the performance/space gains of deactivating the monitoring support is, in my opinion, an advanced user
ok I am convinced to move Monitoring into the advanced section
Thanks for the feedback. Based on it I create the [issues:#852] to capture the result of the discussion.
Related
Issues:
#852To further simplify FORTE configuration I thought it is a good idea to make architecture selection possible with a combo box. Today I played a little with CMake the results can be found under [issues:#853]. I hope you like it as well.
Related
Issues:
#853I like the combo box for the architecture (although it took me a while why a internal module had some linker problems ;-) ).
May I take this for an additional RFC regarding the options - what about disabling the FORTE_TRACE_EVENTS by default?
Last edit: Gerhard Ebenhofer 2014-05-05
with cset [forte:6ae019] the linking issues in all the FORTE CMakeFiles should now be resolved.
Related
Commit: [6ae019]
The combo-box is a very good idea. Yes, also the FORTE_TRACE_EVENTS shoule be deactivated by default in my point of view.
Thanks. Oopsi I think I will have to check some of the modules. As the checking for architectures has changed.
I was not sure about the FORTE_TRACE_EVENTS but I'm happy to deactivate it per default. Should we move this also into the advanced section?
I would be in favour to move it to the advanced section!