1068 | Integrate BMC C++ SDK Tests into GitHub Build Workflow

[Salonso1602]

Resolves

https://focusuy.atlassian.net/browse/BMC2-1068

Dependencies

#20

How to test

• Go to actions
• Run Tests workflow from this branch

What to expect

• All tests pass as expected

Notes

Linux may still have the SEGFAULT error when you get down to testing

[joaquin-urrisa]

I noticed that the tests are currently failing across all builds (see the latest run). I understand that Linux fails due to a known bug, whereas Mac and Windows fail due to the bridge version. Wasn't the bridge removed and now needs to be installed independently? (I saw that the PR for ticket 1050 was merged.)

Additionally, I noticed that you added the staging_dirs.txt.in file. I see it's referenced in both the CMakeLists.txt and the workflow file. I’m not entirely sure how it’s being used or what role it plays in the build process. Could you clarify?

[Salonso1602]

I noticed that the tests are currently failing across all builds (see the latest run). I understand that Linux fails due to a known bug, whereas Mac and Windows fail due to the bridge version. Wasn't the bridge removed and now needs to be installed independently? (I saw that the PR for ticket 1050 was merged.)

That is true, I must revise how the Bridge should be fetched in this PR now that we use a prebuilt bridge

Additionally, I noticed that you added the staging_dirs.txt.in file. I see it's referenced in both the CMakeLists.txt and the workflow file. I’m not entirely sure how it’s being used or what role it plays in the build process. Could you clarify?

the staging dirs txt file is a way of keeping track between actions of where the libs were built and staged so they can be added to PATH, in hindsight it may not be the best solution nor do I have the context how It came to be.
I will give it some reading and get back t you