Skip to content

build: Add optional in-build ACTS build#67

Open
paulgessinger wants to merge 2 commits into
key4hep:mainfrom
paulgessinger:acts-dev
Open

build: Add optional in-build ACTS build#67
paulgessinger wants to merge 2 commits into
key4hep:mainfrom
paulgessinger:acts-dev

Conversation

@paulgessinger

Copy link
Copy Markdown
Collaborator

BEGINRELEASENOTES

  • Add cmake helper to build ACTS integrated with the k4ActsTracking build

ENDRELEASENOTES

# The setup below allows optionally building ACTS directly with the k4ActsTracking build.
# This avoids having to run separate build and install steps, and also allows getting a
# combined compilation database out.
if(IS_DIRECTORY ${ACTS_SOURCE_DIR})

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Who sets ACTS_SOURCE_DIR?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The user!

@jmcarcell

Copy link
Copy Markdown
Member

Are you going to use it? I think people are used to building in two steps. Basically the same could be done with many combinations of 2 or more repositories or externals in Key4hep, but no one has asked to add something like this so far. master of ACTS is built in the stacks, so not that often one needs to build ACTS.

@paulgessinger

paulgessinger commented Jun 16, 2026

Copy link
Copy Markdown
Collaborator Author

I already used it last week to make changes to ACTS so that main becomes non-breaking.

If we don't merge this I'll have to maintain a patch.

This setup makes it much easier to update k4ActsTracking when ACTS changes and make changes to ACTS and test the impact.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants