|
|
|
abdes / blocxxi Goto Github PK
View Code? Open in Web Editor NEWImplementation of Kademlia based DHT and a blockchain in C++
License: BSD 3-Clause "New" or "Revised" License
blocxxi's Introduction
blocxxi's People
Contributors
Stargazers
Watchers
blocxxi's Issues
How to force build system use already installed dependencies and not try building duplicates?
How do I force the build system to use already installs dependencies rather than doing something as crazy as trying to build it own Boost (that too, picking a broken version of it)?
-- [cryptopp] Build type: MacPorts
.. [1] back to [blocxxi]
=> [2] in module [blocxxi] > (boost_algorithm)
-- CPM: adding package boost_algorithm@ (boost-1.80.0)
.. [1] back to [blocxxi]
=> [2] in module [blocxxi] > (boost_align)
-- CPM: adding package boost_align@ (boost-1.80.0)
.. [1] back to [blocxxi]
=> [2] in module [blocxxi] > (boost_array)
-- CPM: adding package boost_array@ (boost-1.80.0)
.. [1] back to [blocxxi]
=> [2] in module [blocxxi] > (boost_asio)
-- CPM: adding package boost_asio@ (boost-1.80.0)
.. [1] back to [blocxxi]
=> [2] in module [blocxxi] > (boost_assert)
-- CPM: adding package boost_assert@ (boost-1.80.0)
.. [1] back to [blocxxi]
=> [2] in module [blocxxi] > (boost_bind)
-- CPM: adding package boost_bind@ (boost-1.80.0)
.. [1] back to [blocxxi]
=> [2] in module [blocxxi] > (boost_chrono)
-- CPM: adding package boost_chrono@ (boost-1.80.0)
.. [1] back to [blocxxi]
=> [2] in module [blocxxi] > (boost_concept_check)
-- CPM: adding package boost_concept_check@ (boost-1.80.0)
.. [1] back to [blocxxi]
=> [2] in module [blocxxi] > (boost_config)
-- CPM: adding package boost_config@ (boost-1.80.0)
.. [1] back to [blocxxi]
=> [2] in module [blocxxi] > (boost_container)
-- CPM: adding package boost_container@ (boost-1.80.0)
.. [1] back to [blocxxi]
=> [2] in module [blocxxi] > (boost_container_hash)
-- CPM: adding package boost_container_hash@ (boost-1.80.0)
.. [1] back to [blocxxi]
=> [2] in module [blocxxi] > (boost_context)
-- CPM: adding package boost_context@ (boost-1.80.0)
-- Boost.Context: architecture i386, binary format mach-o, ABI sysv, assembler gas, suffix .S, implementation fcontext
.. [1] back to [blocxxi]
=> [2] in module [blocxxi] > (boost_conversion)
-- CPM: adding package boost_conversion@ (boost-1.80.0)
.. [1] back to [blocxxi]
=> [2] in module [blocxxi] > (boost_core)
-- CPM: adding package boost_core@ (boost-1.80.0)
.. [1] back to [blocxxi]
=> [2] in module [blocxxi] > (boost_coroutine)
-- CPM: adding package boost_coroutine@ (boost-1.80.0)
.. [1] back to [blocxxi]
=> [2] in module [blocxxi] > (boost_date_time)
-- CPM: adding package boost_date_time@ (boost-1.80.0)
.. [1] back to [blocxxi]
=> [2] in module [blocxxi] > (boost_detail)
-- CPM: adding package boost_detail@ (boost-1.80.0)
A correct behavior would be to prioritize existing ports and try building dependencies only when something cannot be found. Even that, IMO, should be disablable, so that configure just errs out if cannot find something which is required. (So that I can find a port or write one for a needed dependency.)
merge method has not been implmented
AddPeer -> Split
void RoutingTable::RemovePeer(const Node &node)
{
//should checking node size of bucket,and .....
bool can_merge = false;
.............
}
Fix memory leak in UpnpPortMapper::Discover()
When a valid IGD is found, the UpnpPortMapper instance (mapper) is not deleted.
Implement stacking delegate logging sink
The issue with spdlog is that sinks(s) attached to loggers are set at logger creation time and stay like that forever. This is not flexible enough in two situations:
-
If the application starts logging early to console and then later needs to log to some different sink after the proper resources for that sink have been initialized (e.g. GUI)
-
If the application needs to temporarily switch logging output to a different sink (e.g. dumping diagnostic data) and then switch back to original sink after it's done. This requires two loggers in the current implementation.
Proposal is to implement a delegating sink for the application used with all created loggers. The Registry should allow an API to push/pop sinks dynamically. When a sink is pushed, it becomes the active sink for the delegating sink. When it is popped, the previously used sink comes back.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.