-
Notifications
You must be signed in to change notification settings - Fork 49
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
Testing C++11 compilation #309
Conversation
Preview page for your plugin is ready here: |
Codecov ReportPatch and project coverage have no change.
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more Additional details and impacted files@@ Coverage Diff @@
## main #309 +/- ##
=======================================
Coverage 84.87% 84.87%
=======================================
Files 30 30
Lines 1957 1957
Branches 296 296
=======================================
Hits 1661 1661
Misses 212 212
Partials 84 84 ☔ View full report in Codecov by Sentry. |
To support older versions of C++ we could look into https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners |
Had a look. The old link https://github.com/eigenteam/eigen-git-mirror says it is deprecated and may be removed at any time. Hence why we removed it. |
(will give this a go tomorrow as I don't have my macbook on me today) |
works for me! |
For macOS Mojave 10.14.6 users if you struggle to get btrack to work you may notice these errors: When trying to run tracks in your notebook:
While building:
To overcome this issue in your btrack folder go to Makefile(txt file) and remove this bit : This will result in successful outcome. Then install the whole package! Many thanks to @quantumjot for solving this issue!!! |
This works for me too. Thank you. Sorry about the delay but I've been running btrack on a virtual machine to get around this. Glad to move it all back on our cluster computer. BTW, the optimization is much faster now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some comments
@@ -7,7 +7,7 @@ mkdir ./btrack/obj | |||
# clone Eigen | |||
if [ ! -e ./btrack/include/eigen/signature_of_eigen3_matrix_library ] | |||
then | |||
git clone https://gitlab.com/libeigen/eigen.git ./btrack/include/eigen | |||
git clone --depth 1 --branch 3.3.9 https://gitlab.com/libeigen/eigen.git ./btrack/include/eigen |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems like a good compromise rather than using the old repository. I've just realised that --branch
here also accepts tags https://stackoverflow.com/a/39067940/7359333. My concern at first was that they may delete the branch.
XLD_FLAGS = -arch x86_64 -arch arm64 | ||
XLDFLAGS = |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Curious to know whether any of the XLDFLAGS
are actually required?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For some of the compilers they are required (I think!)
@@ -20,7 +20,7 @@ | |||
#include <algorithm> | |||
#include <cmath> | |||
#include <ctime> | |||
#include <filesystem> | |||
// #include <experimental/filesystem> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here and elsewhere should we just remove rather than comment out?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I'd like to leave this in if possible, since we might want to reinstate it once we can move back to C++17 (or greater). Probably fine to delete though, it's not an essential function - mostly used for debugging.
FYI, I can no longer compile on my machine. Do we want to support old machines or new ones? I'm on an M1 macOS |
Weird - I just tried compiling on my M1 Mac and it was fine |
I'm still having issues on my standard
|
This is a test of compilation of the latest version of
btrack
using an older compiler for compatibility.@markdane @ania-m-b @nthndy - could you try this fix out, since I know you were all having issues on your respective machines?