Fix RTC_LOCKABLE RTC_EXPORT order for rtc::Thread.
The previous order of macros causes [1]. [1] - https://ci.chromium.org/p/chromium/builders/try/win_chromium_compile_dbg_ng/420871 Bug: webrtc:9419 Change-Id: If261e5c1d4bf058417be2bcc9a7cd26cc210f20b Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/158121 Reviewed-by: Steve Anton <steveanton@webrtc.org> Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org> Cr-Commit-Position: refs/heads/master@{#29592}
This commit is contained in:

committed by
Commit Bot

parent
d7bf5c56b6
commit
4ff1c87204
@ -133,7 +133,7 @@ struct _SendMessage {
|
||||
|
||||
// WARNING! SUBCLASSES MUST CALL Stop() IN THEIR DESTRUCTORS! See ~Thread().
|
||||
|
||||
class RTC_EXPORT RTC_LOCKABLE Thread : public MessageQueue {
|
||||
class RTC_LOCKABLE RTC_EXPORT Thread : public MessageQueue {
|
||||
public:
|
||||
explicit Thread(SocketServer* ss);
|
||||
explicit Thread(std::unique_ptr<SocketServer> ss);
|
||||
|
Reference in New Issue
Block a user