[Bug 1001550] STM32 F2 and STM3220G-EVAL / STM3240G-EVAL contribution from eCosCentric

[bugzilla-daemon@bugs.ecos.sourceware.org]

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001550

--- Comment #21 from Jonathan Larmour <jifl@ecoscentric.com> 2012-04-05 16:42:25 BST ---
(In reply to comment #20)
> Why isn't this available in CDL?

It isn't available in CDL because, as Bart would tell you, he's never been
given time to develop it. Although Bart did take a sabbatical year and
host-side CDL and configuration improvements was something he was going to be
working on in that time, I think in practice he found it difficult to make good
progress on it. I'm afraid I don't know what the status is or what the plans
are at the moment - it may be nearly complete, or he may not be developing it
much at the moment.

> I always wanted some kind of soft "requires",
> that will set/change default value but not hinder user override. My proposed
> name was supposed to be "recommends" but "set_value" is perhaps better. 

This is a slightly different issue than the provision of targets by packages.
Yes what you ask for is indeed something which we have known for quite a while
is desirable, although wasn't in the original design. Bart did propose two
additions to CDL for this at some point in the past "default_value -weak" and
"override_default", but again these have not yet been implemented.

In the meantime, the workaround is to have two CDL values if this is needed.
Once is the option itself, and it has a default_value of the other option
(which will have the same name suffixed with _DEFAULT). Packages which need to
change the default do the "requires" on the _DEFAULT option, not the real one.

Anyway, this is getting a bit off-topic in the context of this STM32 patch. If
there are no objections, I'll close this 'bug' shortly (it can still be
reopened again).

Jifl

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.