| Re: [AD] Fortify and Allegro |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
> Seems dodgy, as you'd then need to add a lot of enable-* to cater
> for everything you might want only in the debug build, but not in
> release. eg, you may want the debug lib to be in C, but the release
> lib to be in asm. Or the debug lib to not use pentium opts, but to
> include them in the release build.
I think it's not the same situation: Fortify is useful for debugging only.
> But I agree it's counterintuitive to only enable Fortify for the debug lib.
It's not counterintuitive, it's simply broken: you can't silently discard a
configure option without telling the user.
> An ideal solution would allow the user to configure differently for each
> target (release, debug, profile). But that would probably mean lots of
> changes in the build process.
Yes, probably. But we need a real solution anyway because I'm already hearing
the users' complaints about this "--enable-fortify option that doesn't do
anything at all."
--
Eric Botcazou