-
Notifications
You must be signed in to change notification settings - Fork 146
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
Only build necessary Sleigh components #613
Conversation
Tests are failing because the spec files aren't being compiled/installed. There are some spec targets you can un-exclude from all to make sure they're built |
I'll wait until we figure out lifting-bits/sleigh#105 (comment) since this appears to be the same issue. |
Hmm, the |
I'll debug this when I get the chance. But just confirming, @ekilmer, is this how the variables should be set? |
Hmmm. It doesn't look like the additional patches are being applied, so maybe that's what is causing failures?
https://github.com/lifting-bits/remill/runs/7832387939?check_suite_focus=true#step:4:574 |
Oh that's interesting. I'll look into that now. |
Ok, this issue is fixed in 75adcde. I think somehow the spot where we do: set(sleigh_ADDITIONAL_PATCHES "" CACHE STRING
"The accepted patch format is git patch files, to be applied via git am. The format of the list is a CMake semicolon separated list.") Is overwriting the user setting. When I did a rebuild, it seemed to apply the patches correctly. So perhaps it has something to do with the ordering of where the variable is defined and where we pull the Ghidra source? |
Ah. Yeah I didn't see that it was originally a normal variable for the patches. Mixing and matching still doesn't make sense to me, so it's always good to match the variable types. Usually for something like this, it will be a cache variable you are trying to modify.
Hmmm. That shouldn't happen. Whatever the first call to |
Yeah, I blew away the build each time. It's the same thing that was causing the failure in CI (which would have been a fresh build directory). Anyhow, specifying |
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.
LGTM!
No description provided.