-
Notifications
You must be signed in to change notification settings - Fork 85
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
[2.4] meson: Introduce a with-lockfile-path option #1404
[2.4] meson: Introduce a with-lockfile-path option #1404
Conversation
@VorpalBlade Would you be able to test if this works to set the lockfile path in your environment? |
I should be able to take a look on Friday evening (Europe time) |
7a947a8
to
28cad06
Compare
It almost works:
|
@VorpalBlade You just need to append one slash and it should work, i.e. You can observe the mechanism in: netatalk/include/atalk/paths.h Line 16 in 0484716
|
Of course, but it is inconsistent with how other path variables (such as I do sympathise though: doing this correctly (e.g. not just string concatenation) in C is a bit annoying. |
Fair point. This is the only spot where path string concatenation is done directly in C, rather than through the build system, IINM. It's using this macro |
Quality Gate passedIssues Measures |
This should work, I haven't had time to test it (and I will be out hiking today). |
Enjoy your hike! I'll go ahead and merge then, and we can roll another patch later if needed. |
Use with-lockfile-path to set a lockfile path that is not defined in paths.h
This leverages the special
-D_PATH_LOCKDIR
compiler flag that is only in 2.x (refactored away in 3.x and later)