-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CI] Add sirius lib to PATH #1725
Conversation
Signed-off-by: Sylvain Leclerc <[email protected]>
Signed-off-by: Sylvain Leclerc <[email protected]>
This reverts commit 9f4fe85.
Kudos, SonarCloud Quality Gate passed! |
i personally use |
Ah, thanks! it sound better, if it works, it does not require the user to alter the environment outside of cmake related commands and files. |
Unfortunately, only
So it seems that it's necessary to add it in the PATH. |
🤐 |
Is the solution described up to date? The code change does not explicitly refer to target_link_library Also, does it impact local development in any way? Looking only at the changelog I would say yes because dependency is not copied anymore but maybe it supported by other configuration? |
Yes it is: the goal of the change is that using
Indeed it does: the developer must ensure to have sirius in its PATH too (or any other place that windows searches for). For me it does not invalidate the solution: it does not make sense to copy libs we want to use in all directories where we want to execute something. The goal of shared libraries is to be shared from the one place where they are installed :) |
I’m takin it |
Watermelon AI SummaryAI Summary deactivated by sylvlecl GitHub PRs
Antares_Simulator is an open repo and Watermelon will serve it for free. |
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
**Description** On windows, running antares requires to have sirius DLL in the search path for libraries. In particular, unit tests linked with sirius need that. The current implemented solution is a somewhat dirty workaround: for each executable linked (possibly transitively) with sirius, we have a special CMake macro which needs to be used to copy sirius DLL to the same directory as the executable. This requires developers to modify the build just to solve an installation issue, and this for **each** executable that are linked with sirius. **Solution** Instead, the PR proposes to add sirius installation directory to the PATH variable. Executing unit tests will now rely on normal windows DLL search mechanism, and the developer only has to use the standard `target_link_libraries` in CMake files. --------- Signed-off-by: Sylvain Leclerc <[email protected]> Co-authored-by: Florian OMNES <[email protected]>
Description
On windows, running antares requires to have sirius DLL in the search path for libraries.
In particular, unit tests linked with sirius need that.
The current implemented solution is a somewhat dirty workaround:
for each executable linked (possibly transitively) with sirius, we have a special CMake macro which needs to be used to copy sirius DLL to the same directory as the executable.
This requires developers to modify the build just to solve an installation issue, and this for each executable that are linked with sirius.
Solution
Instead, the PR proposes to add sirius installation directory to the PATH variable.
Executing unit tests will now rely on normal windows DLL search mechanism, and the developer only has to use the standard
target_link_libraries
in CMake files.