Opened 18 years ago

Last modified 17 years ago

#73 new enhancement

The 'shared-linkable' property

Reported by: james.mansion@… Owned by: somebody
Priority: major Milestone: M16 - Various fixes
Component: component1 Version:
Keywords: Cc:

Description

From the boost-build mailing list:

So ... The compilation switches that need to be applied to a source file to create an object should really relate to whether it will eventually be directly linked into an executable, or linked into a DLL. It should not be determined by whether it gets aggregated into a static library as an intermediate step.

This can be done by creating new property <shared-linkable>, that control if the object file will eventually end up in a shared library.

Change History (2)

comment:1 by ghost, 17 years ago

Summary: Need new property to specify that an object (in a static lib) will eventually end up in a DLLThe 'shared-linkable' property

comment:2 by ghost, 17 years ago

Milestone: M16 - Various fixes

I think the ideal approach is to add shared-linktable feature. When building a shared library, thisfeature should be set to on, so that all dependencies are also built with that property. The problems are:

  1. The linking-generator already gets the source targets, so it's to late to add a property to build request for dependencies.
  1. If this property is not set for exe, then we'll get extra element in target path, which is undesirable.
Note: See TracTickets for help on using tickets.