Changes between Initial Version and Version 1 of Projects/GSoC/ApplicationConfigurationGUI

Timestamp:

01/26/10 04:02:14 (14 years ago)

Author:

JoelSherrill

Comment:

New page.

Projects/GSoC/ApplicationConfigurationGUI

@@ +1 @@
+= ApplicationConfigurationGUI =
+
+
+
+[[TOC(Projects/GSoC/ApplicationConfigurationGUI, depth=2)]]
+
+
+The goal is to have a graphical tool to configure RTEMS for a certain
+Application e.g. max number of tasks, semaphores etc. It could
+generate a userconf.h which includes confdefs.h. The complete list
+of RTEMS configuration parameters for version 4.9.1 of RTEMS are documented in the 
+[http://www.rtems.org/onlinedocs/releases/rtemsdocs-4.9.1/share/rtems/html/c_user/c_user00039.html
+Configuring a System] chapter in the User's Guide.
+
+There are a variety of ways to approach this project.
+
+ *  One solution is to write a GUI in Python.  This should be cross-platform.
+ *  Another solution could be a Wizard/Editor for Eclipse.  
+ *  Another solution is to use the config infrastructure used by the GNU/Linux kernel.
+ *  Another approach would be to use the configuration GUI from eCos and NutOS: http://www.ethernut.de/en/software/nutconf.html
+
+'''There is NO consensus on how best to approach this project and you must convince the community that your approach will be the right one.
+'''
+
+[wiki:TBR/User/JoelSherrill JoelSherrill] has used the GNU/Linux kernel config infrastructure for
+similar jobs in the past and things it is likely the best alternative
+as a baseline.  This would certainly provide multiple interfaces on
+GNU/Linux hosts (e.g. X11, menu, command line).  But we would like
+a solution that also addresses MS-Windows users.  
+
+A better possibility is to write a GUI program in Python which reads an XML format file describing the RTEMS configuration parameters.  As the user set values, the program would store this information in another XML format file.  When it was time to write the C code to use with the RTEMS application, the GUI application would write that.  So we would have:
+
+ *  XML file describing RTEMS configuration parameters
+ *  XML save file with user settings
+ *  C/H file output for use with RTEMS application