extra_objects and dependencies
Hi!
We have the problem that if you list additional objects as extra_objects in an Extension object, the linker is NOT called when one of these object files changes. Does that count as a bug?
Ciao, Jürgen
-- Jürgen Hermann, Developer (jhe@webde-ag.de) WEB.DE AG, http://webde-ag.de/
Juergen Hermann wrote:
Hi!
We have the problem that if you list additional objects as extra_objects in an Extension object, the linker is NOT called when one of these object files changes. Does that count as a bug?
Changing line 396 in distutils/commands/build_ext.py from
if not (self.force or newer_group(sources, ext_filename, 'newer')):
to
if not (self.force or newer_group(sources + ext.extra_objects, ext_filename, 'newer')):
might help. (But I have not tested it for myself.) Default value of ext.extra_objects is [] so it should not influence any other cases.
If this works someone who has write access to CVS might add it.
Kind regards Rene Liebscher
From: "Rene Liebscher" R.Liebscher@gmx.de
Juergen Hermann wrote:
Hi!
We have the problem that if you list additional objects as extra_objects in an Extension object, the linker is NOT called when one of these object files changes. Does that count as a bug?
Changing line 396 in distutils/commands/build_ext.py from
if not (self.force or newer_group(sources, ext_filename, 'newer')):
to
if not (self.force or newer_group(sources + ext.extra_objects, ext_filename, 'newer')):
might help. (But I have not tested it for myself.) Default value of ext.extra_objects is [] so it should not influence any other cases.
If this works someone who has write access to CVS might add it.
The recommended way to make sure this doesn't get forgotten is to submit this patch to the sourceforge bug or patch tracker.
Thomas
participants (3)
-
Juergen Hermann -
Rene Liebscher -
Thomas Heller