Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
VkCV Framework
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Terraform modules
Monitor
Service Desk
Analyze
Contributor analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Vulkan2021
VkCV Framework
Commits
c7490040
Commit
c7490040
authored
3 years ago
by
Tobias Frisch
Browse files
Options
Downloads
Patches
Plain Diff
[
#79
] Breaking some commandments for MinGW
Signed-off-by:
Tobias Frisch
<
tfrisch@uni-koblenz.de
>
parent
52fd6e51
Branches
Branches containing commit
Tags
Tags containing commit
1 merge request
!80
Resolve "MinGW corrections for the hacks"
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
include/vkcv/Event.hpp
+10
-0
10 additions, 0 deletions
include/vkcv/Event.hpp
with
10 additions
and
0 deletions
include/vkcv/Event.hpp
+
10
−
0
View file @
c7490040
#pragma once
#include
<functional>
#ifndef __MINGW32__
#include
<mutex>
#endif
namespace
vkcv
{
...
...
@@ -27,7 +30,10 @@ namespace vkcv {
private:
std
::
vector
<
event_function
<
T
...
>
>
m_functions
;
uint32_t
m_id_counter
;
#ifndef __MINGW32__
std
::
mutex
m_mutex
;
#endif
public:
...
...
@@ -75,14 +81,18 @@ namespace vkcv {
* locks the event so its function handles won't be called
*/
void
lock
()
{
#ifndef __MINGW32__
m_mutex
.
lock
();
#endif
}
/**
* unlocks the event so its function handles can be called after locking
*/
void
unlock
()
{
#ifndef __MINGW32__
m_mutex
.
unlock
();
#endif
}
explicit
event
(
bool
locked
=
false
)
{
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment