You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The target cafUserInterface uses QtSvg but doesn't list it as a link dependency, but leaves it to its consumers to do the linking. Shouldn't the target introducing a dependency also be responsible for linking to it?
The targets cafTestApplication, cafTestCvfApplication and cafUserInterface_UnitTests all consumes cafUserInterface and have to manually link to QtSvg as it is today.
The text was updated successfully, but these errors were encountered:
marthinsen
added a commit
to marthinsen/ResInsight
that referenced
this issue
Dec 14, 2023
The project cafUserInterface requires the library QtSvg because of the
use of QSvgRenderer in cafUiIconFactory.cpp. The library has to be
linked into the final executable. The target introdicing the dependency
should also be the one specifying it.
This allows us to remove the dependency from targets that doesn't
directly use QtSvg at all.
ClosesOPM#10955
The project cafUserInterface requires the library QtSvg because of the
use of QSvgRenderer in cafUiIconFactory.cpp. The library has to be
linked into the final executable. The target introdicing the dependency
should also be the one specifying it.
This allows us to remove the dependency from targets that doesn't
directly use QtSvg at all.
Closes#10955
The target
cafUserInterface
uses QtSvg but doesn't list it as a link dependency, but leaves it to its consumers to do the linking. Shouldn't the target introducing a dependency also be responsible for linking to it?The targets
cafTestApplication
,cafTestCvfApplication
andcafUserInterface_UnitTests
all consumescafUserInterface
and have to manually link to QtSvg as it is today.The text was updated successfully, but these errors were encountered: