On 07/19/11 08:14, MacArthur, Ian (SELEX GALILEO, UK) wrote:
>> I just tried a test on linux + osx where I removed the file
>> and ran a 'make clean; make'. The build stopped at that file
>> on both platforms, so it *is* getting linked on normal builds.
>>
>> Seems like we gotta fix this.
>
> Bother.
>
> Did it choke because we *need* the file, or just 'cause it could not
> find it and the Makefile calls it up?
The latter; I didn't try the former.
My concern (as a commercial developer that releases
static builds) is not whether the code is used,
but that it's in the lib at all.
True: if the code is not called, it shouldn't
appear in the linked executables by optimization.
And legally I imagine that's all that matters.
And in my quick builds on linux, if I put some unique
strings in the body of the scandir code and do a static
build against the lib, I don't see that string in the
executable, so offhand it seems app developers have
nothing to worry about regarding released binaries.
Still though, it should be "fixed", by which
I mean either rewritten or removed.
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
