You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since libtuv is integrated into dcurl, we can unify the use of thread synchronization with libtuv APIs. Specifically, all occurrence of mutex and semaphore can be replaced with the corresponding libtuv equivalents, which are implemented with cross-platform support in mind. It implies that we can concentrate on abstract computing and resource management without enumerating GNU/Linux, macOS, and even MS-Windows ports.
The text was updated successfully, but these errors were encountered:
Although replacing thread synchronization APIs with libtuv is trivial, it would have issue when compiling dcurl on other platform.
For example, the de10 nano hardware platform.
Check #105 for reference.
The libtuv needs to specify the supported hardware and OS, but the current detection method in mk/submodule.mk is quite simple.
Replace the thread synchronization functions with the portable
libtuv APIs and remove the unused code.
TODO:
Make mutex of src/compat-ccurl.c portable.
CloseDLTcollab#107.
Replace the thread synchronization functions with the portable
libtuv APIs and remove the unused code.
TODO:
Make mutex of src/compat-ccurl.c portable.
CloseDLTcollab#107.
Since
libtuv
is integrated intodcurl
, we can unify the use of thread synchronization with libtuv APIs. Specifically, all occurrence of mutex and semaphore can be replaced with the corresponding libtuv equivalents, which are implemented with cross-platform support in mind. It implies that we can concentrate on abstract computing and resource management without enumerating GNU/Linux, macOS, and even MS-Windows ports.The text was updated successfully, but these errors were encountered: