Closed aviumcaravan closed 4 months ago
To make sure this isn't a CMake issue... If you build another CMake project, does it generate fine?
no, no projects are generated inside of Darling. this quite literally broke across a commit or two, same CMake binary.
no, no projects are generated inside of Darling
What about a non-Darling projects that use CMake?
this quite literally broke across a commit or two, same CMake binary.
So if you revert back to the older commit, CMake works fine? Can you identify the exact commit that works for you.
i think you misunderstood me. to clarify, what i mean is that CMake doesn't work inside of the container. the commit that worked is c28e63693
i think you misunderstood me. to clarify, what i mean is that CMake doesn't work inside of the container.
Oh! I see what you mean now.
Hey @Fancy2209, I'm thinking of reverting your 882fec31025fc56dc5ce0a1310bbeebc1453847e commit, since I think these stubs need to be implemented (and I won't have time to implement them). Just want to give you a heads up.
@aviumcaravan Can you test the revert_SemaphoreStubs
branch. Let me know if it fixes your issue.
Hey @Fancy2209, I'm thinking of reverting your 882fec3 commit, since I think these stubs need to be implemented (and I won't have time to implement them). Just want to give you a heads up.
If it's needed I'm completely fine with that, thanks for letting me know
@aviumcaravan Can you test the
revert_SemaphoreStubs
branch. Let me know if it fixes your issue.
yeah, gimme a shortie
it doesn't build. welp.
fixed as of the latest commit. :3
closing the issue
Expected Result CMake either finishing making a Makefile/build.ninja file or throwing an error.
Actual Result CMake throws deprecation warnings (if necessary) and then straight up freezes. no log is generated.
Steps To Reproduce
System Information What system are you using?