Closed tomeichlersmith closed 1 week ago
I think this is expected see https://github.com/acts-project/acts/pull/3507
We didn't end up removing the flag in that PR, but maybe this is reason to do that. The alternative is to use preprocessor ifs to remove the code that uses tbb conditionally.
I would argue we can just accept that tbb is required for the examples and move on.
That works for me! As I mentioned, the only reason we were confused is because it seemed like it was optional. :)
That PR is still open, should this decision be put into that PR or should a separate PR be opened?
This issue/PR has been automatically marked as stale because it has not had recent activity. The stale label will be removed if any interaction occurs.
This is not a critical bug but is a usability obstacle for downstream ACTS users. I chose to label this a bug since the CMakeLists.txt including this as an option implies to me that the examples should be able to build without TBB.
I am building ACTS within a fixed environment where TBB is unavailable. I configure ACTS with
and then build with
I have uploaded the full command log for review, but the relevant parts are...
during the configuration step, ACTS acknowledges that it will be built in single-threaded mode.
the build of the examples fails when trying to include a tbb header
I'm guessing this is simply an issue with not wrapping the relevant TBB parts in the Sequencer. For example,
https://github.com/acts-project/acts/blob/d250bbfaa33b47a873307a3d7c65e2553f442c3f/Examples/Framework/include/ActsExamples/Framework/Sequencer.hpp#L29-L31
https://github.com/acts-project/acts/blob/d250bbfaa33b47a873307a3d7c65e2553f442c3f/Examples/Framework/src/Framework/Sequencer.cpp#L106-L113
We are proceeding forward with simply commenting out the Sequencer compilation from the framework example since we are just trying to get to using the CSV writer (which depends on the writer interface within the framework example).