回复：Linux 构建
首次公开证据
打开首次公开证据查看 1 个交叉存档
来源说明
Published on GitHub in February 2024 as part of Martti Malmi's testimony in the COPA v. Wright trial
我采用的简单办法是查看 wxWidgets 源代码，看看他们是怎么做的。他们在非 MSW 平台上只是将它映射到 wxMutex，而 wxMutex 确实有 TryEnter，所以正好可以这样映射。
我已将积压的所有更改签入 SVN，其中包括彻底改造 util.h 中的 CCriticalSection，以及修改 util.cpp 中 OpenSSL 的互斥锁回调，使其在非 Windows 平台上全部通过 wxWidgets 来完成。
如果我们能让它在 Linux 上运行，我会先在这里断开网络，用我的测试套件对它进行测试，然后我们可以把一个未发布的构建版本交给 LibertyStandard 测试一段时间，再对外发布。
我会把 CriticalSection 代码转换为 wxCriticalSection 并上传到 SVN （这有点棘手）。不过我不知道 TryEnterCriticalSection 该怎么办。 我想我差不多准备好把所有东西签入了。
Boost 互斥锁在这里会有帮助吗？
英文原文
展开英文原文
The easy solution I took was to look at the wxWidgets source code and see how they did it. They just mapped it to wxMutex on non-MSW, which does have TryEnter, so that mapped in perfectly.
I checked in all my backlog of changes to SVN, including the overhaul of CCriticalSection in util.h and OpenSSL's mutex callback in util.cpp to do everything with wxWidgets when not on Windows.
If we get it working on Linux, I'll run my test suite against it here off-network first, then we can give an unreleased build to LibertyStandard to test for a while before going public.
I'll convert the CriticalSection code to wxCriticalSection and upload it to SVN (it's a little tricky). I don't know what to do for TryEnterCriticalSection though. I think I'm almost ready to check everything in.
Would the Boost mutex be of any help here?