On 06/28/2013 02:07 PM, Phil Blundell wrote:
On Fri, 2013-06-28 at 13:19 -0700, Saul Wold wrote:
So, if I remember correctly there was issues with this because there are
a number of packages that have to modify specifically the security
related flags (see the list in security_flags.inc), the ordering/timing
of being able to due that correctly did not allow for setting it
directly in CFLAGS or TARGET_CFLAGS.
What exactly were the issues? I can't think of any obvious reason why
it wouldn't work for security.inc to do:
SECURITY_CFLAGS = "-fstack-protector-all -pie -fpie -D_FORTIFY_SOURCE=2"
SECURITY_CFLAGS_pn-curl = "-fstack-protector-all -pie -fpie"
CFLAGS += "${SECURITY_CFLAGS}"
Seems either will work, this or TARGET_CFLAGS_append, I guess the
problem I had in the past was trying to do it in the recipe or some
other ordering problem. I think part of it is that these are special
since they use "export"
So now the question is which place them TARGET_*FLAGS or *FLAGS??
TARGET_* makes it clear we are modifying those flags.
Sau!
p.
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
