#73 Remove code optimisations specific to UDB3-

[Anonymous]

Originally created by: uavflightdirector
Originally owned by: robert.dickenson (code.google.com)

Remove conditional code compilations used to reduce memory usage for UDB3-.
In particular any variables that are conditionally variable or const will be made variable only.

The aim is to reduce clutter and reduce test load.

What still needs to be decided?

What still needs to be done?

[Anonymous]

Originally posted by: uavflightdirector

Move to release 4.5

Labels: -Milestone-Release4.2 Milestone-Release4.5

[Anonymous]

Originally posted by: robert.dickenson (code.google.com)

Most of the preprocessor macros to support the legacy boards was removed prior to the 4.0 release. Compiling in support for all GPS types which are supported is completed and ready for completing the merge to trunk.

To be decided:
The level of runtime configuration we want to support. Now that the UDB4/5 & AUAV3 have plentiful code and data space we can aim for a more general purpose default build with most code features compiled in.

To be done:
The next round will include reducing code complexity due to memory optimisations as described above. Ongoing work to include the three supported OSD devices and continued development of a runtime initialisation file as prototyped in the AUAV3 branch.

Owner: robert.dickenson

[Anonymous]

Originally posted by: uavflightdirector

There are still some optimizations that remain and obscure the code.  One example is the altitudeCntrl and altitudeCntrlVariable libraries. Another example is the option specific way that values are declared as variable or const.

Ownership for this activity is likely to be moved around as different devs do different parts of the cleanup.

This is a wide ranging change which will cause problems with other merges if done too early. As such I have moved it on to release 5.0.

Labels: -Milestone-Release4.5 Milestone-Release5.0

[Anonymous]

Originally posted by: robert.dickenson (code.google.com)

(No comment was entered for this change.)

Status: Started