C:\Windows\System32\cpp-ethereum\build> cmake -G "Visual Studio 14 2015 Win64" .. CMAKE Error at CMakeLists.txt:44 (project): Failed to run MSBuild command: C:/Program Files (x86)/MSBuild/14.0/bin/MSBuild.exe to get the value of VCTargetsPath: Microsoft (R) Build ENgine version 14.0.25420.1 Copyright (C) Microsoft Corporation. All rights reserved. MSBUILD : error MSB1009: Project file does not exist. Switch: VCTargetsPath.vcxproj Exit code: 1 -- Configuring incomplete, errors occurred! See also "C:/Windows/System32/cpp-ethereum/build/CMakeFiles/CMakeOutput.log".
The afformentioned log only has this:
The system is: Windows - 10.0.15063 - AMD64
I have VS2015 installed as well as cmake and git, I'm not sure what I'm doing wrong. Does anyone know what I can do to get around this problem? Thanks! Included in the build directory is a CMakeCache.txt, which seems to hold the settings for the build, and reads as follow:
# This is the CMakeCache file. # For build in directory: c:/Windows/System32/cpp-ethereum/build # It was generated by CMake: C:/Program Files/CMake/bin/cmake.exe # You can edit this file to change values found and used by cmake. # If you do not want to change any of the values, simply exit the editor. # If you do want to change a value, simply edit, save, and exit the editor. # The syntax for the file is as follows: # KEY:TYPE=VALUE # KEY is the name of a variable in the cache. # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. # VALUE is the current value for the KEY. ######################## # EXTERNAL cache entries ######################## //Semicolon separated list of supported configuration types, only // supports Debug, Release, MinSizeRel, and RelWithDebInfo, anything // else will be ignored. CMAKE_CONFIGURATION_TYPES:STRING=Debug;Release;MinSizeRel;RelWithDebInfo //Value Computed by CMake CMAKE_PROJECT_NAME:STATIC=cpp-ethereum //The CMake toolchain file CMAKE_TOOLCHAIN_FILE:FILEPATH=C:/Windows/System32/cpp-ethereum/cmake/toolchain.cmake //Path to the root directory for cpp-ethereum CPP_ETHEREUM_DIR:PATH=C:/Windows/System32/cpp-ethereum //The path to the cmake directory ETH_CMAKE_DIR:PATH=C:/Windows/System32/cpp-ethereum/cmake //Value Computed by CMake cpp-ethereum_BINARY_DIR:STATIC=C:/Windows/System32/cpp-ethereum/build //Value Computed by CMake cpp-ethereum_SOURCE_DIR:STATIC=C:/Windows/System32/cpp-ethereum ######################## # INTERNAL cache entries ######################## //This is the directory where this CMakeCache.txt was created CMAKE_CACHEFILE_DIR:INTERNAL=c:/Windows/System32/cpp-ethereum/build //Major version of cmake used to create the current loaded cache CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3 //Minor version of cmake used to create the current loaded cache CMAKE_CACHE_MINOR_VERSION:INTERNAL=9 //Patch version of cmake used to create the current loaded cache CMAKE_CACHE_PATCH_VERSION:INTERNAL=0 //Path to CMake executable. CMAKE_COMMAND:INTERNAL=C:/Program Files/CMake/bin/cmake.exe //Path to cpack program executable. CMAKE_CPACK_COMMAND:INTERNAL=C:/Program Files/CMake/bin/cpack.exe //Path to ctest program executable. CMAKE_CTEST_COMMAND:INTERNAL=C:/Program Files/CMake/bin/ctest.exe //Name of external makefile project generator. CMAKE_EXTRA_GENERATOR:INTERNAL= //Name of generator. CMAKE_GENERATOR:INTERNAL=Visual Studio 14 2015 Win64 //Name of generator platform. CMAKE_GENERATOR_PLATFORM:INTERNAL= //Name of generator toolset. CMAKE_GENERATOR_TOOLSET:INTERNAL= //Source directory with the top level CMakeLists.txt file for this // project CMAKE_HOME_DIRECTORY:INTERNAL=C:/Windows/System32/cpp-ethereum //number of local generators CMAKE_NUMBER_OF_MAKEFILES:INTERNAL=1 //Platform information initialized CMAKE_PLATFORM_INFO_INITIALIZED:INTERNAL=1 //Path to CMake installation. CMAKE_ROOT:INTERNAL=C:/Program Files/CMake/share/cmake-3.9
Other than that there really isn't much else... no error logs as far as I can see either
I'm designing a private Ethereum blockchain. Now, I'm choosing which technology is suitable for the project. My customer has concerns with GPLs licenses and I reach this 2 projects which have MIT license. Does anyone use them? I would like to know your experience with them and recommendations.
Why is cpp-ethereum now calling their projects webthree?
Hey, so I've been mining for the past two weeks almost with no problems. I am using cpp-ethereum and I haven't encountered any problems until today. I went ahead and launched cmd, changed the directory so it could find the executable file, and ran the command line to start the process. But after 3 lines, it crashed. Do you know what could possibly be causing this and how to fix it? Thanks for your help Edit: Thanks for trying to help guys but I fixed it. Just had to delete the dag files in Ethash folder
We just released cpp-ethereum version 1.2.3. release page. This change further simplifies the codebase and removes some components of eth which were unstable or not well maintainable. These include:
AlethOne (the "one-click GUI miner") - the idea behind such a project is nice, but the wide range of different GPU hardware and many other factors resulted in AlethOne just not delivering the experience. Please use ethminer on the commandline.
fixed issues where blockchain sync got stuck
moved lll and libevmasm into solidity repository
implemented eth_pendingTransactions rpc call
removed compiler rpc calls to simplify dependencies
improved commandline interface of EVM benchmarking tool (use JIT even when requesting stats)
We just released version 1.2.4 of cpp-ethereum including version 1.0.3 of mix and version 0.3.2 of solidity. In this release we mainly focused on the build system and changes not visible to the end-user. The aim is to decouple the various binaries so that they can be built in isolation. For Solidity, some quite important bugs were fixed, so please upgrade. Important: The Mix binary was renamed to mix-ide in order to avoid name conflicts with elixir's build tool. Changelog eth (1.2.4):
removed browser plugin in AlethZero
support for the Intel compiler on Ubuntu
support for xcode 7.3 on OS X
largely decoupled from cpp-ethereum
bugfix: Dynamic arrays of structs were not deleted correctly.
bugfix: Static arrays in constructor parameter list were not decoded correctly.
bugfix: Inline assembly parser: byte opcode was unusable
bugfix: Error reporting: tokens for variably-sized types were not converted to string properly
rename to mix-ide to avoid conflict with elixir build tools
bugfix: transaction arguments for unnamed parameters were not saved correctly
Why it is impossible to verify contracts compiled with solc from cpp-ethereum (It is the most frequently updated binary version for Windows).
The newest binary version of solc for windows I could find is one available in cpp-ethereum release. I compiled a contract with it (the version of solc is 0.3.5-5f97274a/RelWithDebInfo-Windows/msvc/Interpreter, but this version is not available on Etherscan to verify a contract with :(. Can it be made available? Or is there any other binary version that can be easily downloaded that is on Etherscan?
Hey there, trying to install the solidity compiler and get started, but I've been running into issues downloading the dependencies from homebrew. Anyone run into this before?
==> Cloning https://github.com/ethereum/cpp-ethereum.git Updating /Users/ryan/Library/Caches/Homebrew/cpp-ethereum--git ==> Checking out branch develop warning: unable to rmdir deps: Directory not empty ==> cmake -DCMAKE_C_FLAGS_RELEASE=-DNDEBUG -DCMAKE_CXX_FLAGS_RELEASE=-DNDEBUG -DCMAKE_INSTALL_PREFIX=/uslocal/Cellacpp-ethereum/1.3.0 -DCMAKE_BUILD_TYPE=Release -DCMAKE_FIND_FRAMEWORK=LAST -DCMAKE_VER Last 15 lines from /Users/ryan/Library/Logs/Homebrew/cpp-ethereum/01.cmake: -- Check for working CXX compiler: /uslocal/Homebrew/Library/Homebrew/shims/supeclang++ -- Check for working CXX compiler: /uslocal/Homebrew/Library/Homebrew/shims/supeclang++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done CMake Error at cmake/EthCompilerSettings.cmake:68 (message): This compiler AppleClang 126.96.36.19920042 is not able to compile required libff. Install clang 4+ from Homebrew. Call Stack (most recent call first): CMakeLists.txt:94 (include) -- Configuring incomplete, errors occurred! See also "/tmp/cpp-ethereum-20170904-66078-15y3sg0/CMakeFiles/CMakeOutput.log". If reporting this issue please do so at (not Homebrew/brew or Homebrew/core): https://github.com/ethereum/homebrew-ethereum/issues
Ethereum code optimized for some nvidian cards davilizhdavilizh Posts: 1Member ✭
The code is optimized for GTX1060, can improve GTX1060 with 2 GPC performance by 15%, and GTX1060 with 1 GPC performance by more than 30%. Meanwhile, it also increases performance on GTX1070 by 3%, on Telsla M60 by 2%, and should also benefit other chips. When executing the code, please do remember to add "-U" to your argument. Two locations to download the code:
dagger_shuffle.cuh 1) We moved around and reduced variable definitions to the minimum required. The compiler should have been able to do this analysis, but it never hurts to help out the compiler. The state in compute_hash of dagger_shuffle.cuh is modified. 2) We simplify the nested if/else blocks into a switch statement. 3) We simplify control flow. Remove the conditional from the inner loop so all threads calculate the value, and then all threads use a __shfl to read thread t's value (throwing away the rest of the threads' calculated value). 4) We increase the total number of LDGs to increase occupancy. We define PARALLEL_HASH to let each warp have PARALLEL_HASH LDGs in-flight at a time, not 1 at a time, which is the original case.
keccak.cuh Since the input argument uint2 *s is changed in dagger_shuffle.cuh, we have to modify keccak_f1600_init and keccak_f1600_final in keccak.cuh accordingly.
kybarnet kindly joined the call (starting at 9:29) to discuss the issuance reduction and to argue for a further reduction.
There are others in the community, notably DeviateFish_, who argue that there should be no issuance reduction, but unfortunately they were unable to join the call.
The conclusion we came to in the call was to keep the issuance reduction for the Byzantium hard fork to 3 ETH in accordance with EIP 649.
It is unfortunate that certain parties in the discussion (particularly TheCryptoMines) felt left out and I want to find ways in the future to include everyone in the conversation around EIPs and network changes.
I address this specifically at 1:04:43 and Martin H.S provides good commentary at the end of the discussion.
It should be noted that changes like this can be reversed or modified in future hard forks with enough community and developer consensus.
Other posts and opinions from DeviateFish_ and TheCryptoMines can be found here.
The testing team has grown significantly from 3 people to 7 people (starts at 37:05).
Big shout out to Dimitry, Casey D., Yoichi, Martin H.S, Tim S., Jared W., Matthew E. who have contributed to the testing efforts!
Testing is proceeding more smoothly and major clients, including Parity and geth, have implemented most or all of the EIPs that are going into Byzantium.
Within the next 7-10 days we should have benchmarks for gas costs completed.
Once the gas costs benchmarks are finalized and the clients complete implementation of the Byzantium EIPs, we will launch a hard fork on the Ropsten testnet that would run for 2-4 weeks.
Ropsten is hard to sync, so we will look into finding creative ways for people to more easily sync Ropsten. Example: Use lightsync, fastsync, or warpsync, depending on client.
Block number for the mainnet hard fork will be decided soonish. Ballpark block numbers are : block 4.3 million on Sept. 22nd and worst case is block 4.4 million Oct. 27th, so the hardfork will likely be between those two times. We are aiming for sometime late September.
Clients represented in the meeting
The meeting agenda can be found here and a video of the meeting is here.
Does this work with cpp and aleth or would I have to work with Solidity? Andrei Maiboroda. @gumb0. ... Hi, I apologize as I'm a beginner working with Ethereum/Blockchain - is there any documentation on how to work with transaction input data from the aleth ethereum codebase? This is to store a csv file (also could hard-code a map object to ... cpp-ethereum - Ethereum C++ client. This repository contains cpp-ethereum, the Ethereum C++ client.. It is the third most popular of the Ethereum clients, behind geth (the go client) and Parity (the rust client). The code is exceptionally portable and has been used successfully on a very broad range of operating systems and hardware. We are in the process of re-licensing the codebase from the ... cpp-ethereum latest versions: 1.3.0. cpp-ethereum architectures: x86_64. cpp-ethereum linux packages: rpm Aleth – Ethereum C++ client, tools and libraries. The collection of C++ libraries and tools for Ethereum, formerly known as cpp-ethereum project. This includes the full Ethereum client aleth. Contact. Chat in aleth channel on Gitter. Report bugs, issues or feature requests using GitHub issues. Usage Cpp-ethereum安装. 主要记录了c++版本的ethereum在linux环境下的安装，官方的依赖库安装脚本没有CentOS环境下的；在此手动的安装了依赖环境，并在其脚本install_deps.sh添加centos的支持；详细步骤如下：
Ethereum clients allow you to setup an Ethereum node on your computer. An Ethereum client is like a Java Virtual Machine (JVM) and allows you to run Ethereum programs. With an Ethereum client, you ... I made this video showing how I'm mining Ethereum using my home computer. Recommended best Ethereum mining GPU for Price / Performance / Efficiency - AMD R7 ... How to mine Ethereum (ETH) on any pool Explained in details how to mine Ethereum (ETH) coin on any pool. Useful Links: Ethereum Website: https://ethereum.org... How to mine Ethereum Classic (ETC) on pool Explained in details how to mine Ethereum Classic (ETC) coin on pool. Useful Links: Official Website: https://ethereumclassic.github.io/ Bitcointalk ... How to Use Ethermine - Ethereum Mining Pool. In this video I explain how to use ethermine. I talk about how to monitor your mining progress and how to set up...