Topic: [ANN] AEON [2019-09-27: Upgrade to version 0.13.0.0 ASAP HF@1146200 Oct 25] - page 134. (Read 625666 times)

It's built with CUDA Toolkit 8.0.
The binary was compiled on AppVeyor which is a very handy and self-contained build system.
It downloads all dependencies including CUDA and uses CMake to generate a vcxproj file and uses msbuild to compile.
Citing my own comment on Reddit:

https://www.reddit.com/r/Aeon/comments/67lk6m/aeonstaknvidia_windows/dgrkpt6/

The dev donation is set to 1% and sent to donate-aeon.mooo.com which is owned by shyba who originally ported XMR-Stak-CPU/AMD to Aeon.
https://github.com/stoffu/aeon-stak-nvidia/commit/0d81cd7ab6d3ab85b169ca8ac050097428655288

good manual but in my case two last command didn't work in the Git Shell, so I have to run it in ordinary cmd window.
seems Git Shell doesn't use PATH variables...

Building Aeon on Windows (Guide v2017.04.26)

- Download and install latest Git
  https://github.com/git-for-windows/git/releases/download/v2.12.2.windows.2/Git-2.12.2.2-64-bit.exe

- To compile aeond.exe and simplewallet.exe you will need to install vs2015 Community RTM
 
  (iso available to download here https://xinyustudio.wordpress.com/2015/07/21/visual-studio-2015-iso-download-links-official-directoffline-links/)
  http://download.microsoft.com/download/0/B/C/0BC321A4-013F-479C-84E6-4A2F90B11269/vs2015.com_enu.iso

  take care to uncheck box "visual studio 2015 update 3" else update 3 will be downloaded automatically.
  Important note: after installation you should be asked to reboot the OS. Do NOT forget this step, asked or not !
  In addition to this, after rebooting you'll need to start Visual Studio Community 2015 GUI, as other components will be set up.
  
  

  FYI, all version numbers can be found here https://omwtm.blog/2014/12/03/visual-studio-2013-version-numbers-and-updates/
  https://omwtm.blog/2014/12/03/visual-studio-2013-version-numbers-and-updates/
  

- Download and install CMake version 3.8, win 32 installer. If you have a previous version uninstall it first.
  https://cmake.org/files/v3.8/cmake-3.8.0-rc4-win32-x86.msi

- Download and install Python x86-64 executable installer, which is needed by CMake. If you have version 3.4 or lower uninstall it first.
  https://www.python.org/ftp/python/3.6.1/python-3.6.1-amd64.exe
  Pay attention when installation asks if you want to add to system path and do so.

- Download ad install the pre-compiled Boost libraries v 1_63_00 for MSVC-14.0 64bit version (take note of their install path):
  https://sourceforge.net/projects/boost/files/boost-binaries/1.63.0/boost_1_63_0-msvc-14.0-64.exe/download
  Note: to build a distributable Aeon package you'll need to build Boost libraries from source, which it is indeed included in the download.
  Yet please bear in mind that the aim of my guide is to enable common Aeon users in Windows environment to be readily up to date with the latest Aeon release.

  The following directory should be added to compiler include paths (following my own installation path):

    D:\local\boost_1_63_0

  The following directory should be added to linker library paths:

    D:\local\boost_1_63_0\lib64-msvc-14.0

  This will be done by means of cmake arguments, below.


- Now let's start the AEON compiling procedure (16GB RAM is the minimum I would recommend in order to proceed successfully):

  Open the Git Shell (or Git bash) depending what you downloaded previously and do:
     
   After some time you'll find your .exe files in the path_to_your_aeon_repository\Build\Src\Release directory.

   Alternative building procedure, using VS Community 2015 GUI:
  
    It is assumed that the cmake step has been done successfully.
  
    Close GIT Shell if still open.

    Open VS Community 2015 GUI  

    File->Open-> Solution->path to aeon local repository/Project.sln

    VS 2015 will then make a check of all includes. This will take some time, until in the lower-left corner you'll see "Ready". Patience!

    Be sure that up above Release and x64 are selected

    Build-> Build Solution
  
    You'll see a message when the building process is ended.
    You'll find your .exe files in the path_to_your_aeon_repository\Build\Src\Release directory.
  
In any case, after the exe files have been bult and copied in the position of your likings, always remember to clean the content inside the .../build directory to leave it ready for the very next build.
This will obviously require Git Shell or MSVC 2015 GUI to be closed.


Huge thanks to Smooth and Arux for their hard work  

What Cuda SDK does it support?
Building instructions under Win? (I mean the Cmake complete command)
Is it a "fee" like software? Thanks

You're welcome
Just a nuance: after the exe files have been bult and copied in the position of your likings, always remember to clean the content inside the .../build directory to leave it ready for the very next build.

Thanks for your help, I managed to build apps finally.

I've ported fireice_uk's XMR-Stak-NVIDIA to AEON:
https://github.com/stoffu/aeon-stak-nvidia/releases/tag/v1.1.0-1.4.0

It seems to achieve performance on par with or slightly better than ccminer:
https://github.com/tpruvot/ccminer

I just barely managed to port the mining code (like halving the memory size etc), and there may be rooms for further optimization.

Hope you like it!

Did you download and install the recommended version per my guide?
How did you install from the ISO?
OS?
A screenshot?

---

Looks like the proper compiling toolchain has not been triggered.
So, you could try opening the file Project.sln which is in your...../build dir directly from Visual Studio
double cliking on it from Explorer window will do the trick.
Then be sure that up above Release and x64 are triggered.
MSVC will scan for includes and this will take time.
At the end menu Build->Build Solution

Bedtime now

seems MSVC Community 2015 was not installed properly.

Command not found

You don't have to.
If MSVC Community 2015 has been been installed properly, always from the GIT Shell issue the MSBuild line provided with my guide, assuming you did not close it.

Otherwise open it again then
cd Aeon
Git checkout v0.9.12.0
cd build
MSBuild Project.sln /p:Configuration=release /m


Worth knowing your operating system, please

cmake did its job, perfect.

so have to find MSBuild to continue

Yes. try
X:\Ass\aeon\build>cmake -G "Visual Studio 14 2015 Win64" -DBOOST_ROOT=X:/boost_1_63_0 -DBOOST_LIBRARYDIR=X:/boost_1_63_0/lib64-msvc-14.0 ..

Note the / instead of \

Edit: living in Italy, so please bear in mind the timeshift

So any ideas?

Yeah, please let me know

EDIT:
Community members can read the content of the .exe WinRar archive by means of downloading WinRar 5.40 from here:
http://rarlabs.com/
Then opening the .exe archive with WinRar to give it a good look inside its contents.

Hi @daberti

Community members may find this helpful. They will have to assess the risk of using your binaries.

Meanwhile, I have official binaries from @Arux but I haven't been able to upload them yet, as I need access to a different computer. Will get that done within the next day.

Thanks for your help in advance

I just installed all of software from scratch and use installers you wrote above.
When I tried to build a release I got error after cmake step...

X:\Ass\aeon\build>cmake -G "Visual Studio 14 2015 Win64" -DBOOST_ROOT=X:\boost_1_63_0 -DBOOST_LIBRARYDIR=X:\boost_1_63_0\lib64-msvc-14.0 ..

-- The C compiler identification is MSVC 19.0.23026.0
-- The CXX compiler identification is MSVC 19.0.23026.0
-- Check for working C compiler: X:/VS15/VC/bin/x86_amd64/cl.exe
-- Check for working C compiler: X:/VS15/VC/bin/x86_amd64/cl.exe -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: X:/VS15/VC/bin/x86_amd64/cl.exe
-- Check for working CXX compiler: X:/VS15/VC/bin/x86_amd64/cl.exe -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done

CMake Error at X:/CMake/share/cmake-3.8/Modules/FindBoost.cmake:906 (list):
  Syntax error in cmake code at

    X:/CMake/share/cmake-3.8/Modules/FindBoost.cmake:906

  when parsing string

    X:\boost_1_63_0/lib${_arch_suffix}-msvc-14.0

  Invalid escape sequence \b
Call Stack (most recent call first):
  X:/CMake/share/cmake-3.8/Modules/FindBoost.cmake:1380 (_Boost_UPDATE_WINDOWS_LIBRARY_SEARCH_DIRS_WITH_PREBUILT_PATHS)
  CMakeLists.txt:106 (find_package)

-- Configuring incomplete, errors occurred!
See also "X:/Ass/aeon/build/CMakeFiles/CMakeOutput.log".

I'm working on a C# GUI wrapper with built in mining.

Next step, Android mobile wallet with built in mining.

Building Boost should not be as climbing K2, yet things are somehow different:


In addition to this the proper subset of compiling tools of MSVS Comm. 2015 has to be triggered (x86_amd64), otherwise 64bit memory addressing directive alone won't  necessarily do the job.
I'm a huge fan of static compiling for a number of reasons, yet, in this case, I would opt for Boost binaries, just in order to have not a steady flow of complaints of Win people....


cmake topic
Here it is my command and output, right from Git bash:

As you can see the Cmake parser  itself has correctly turned the slashes in the proper way.
It must be noted however that I'm building on a W10 64bit environment, thus the Git shell could potentially behave differently than if installed on i.e. W7.

---

QT is the Devil.
Memory inefficient in first place. Sloooooow.
A VB GUI wrapper would do the task faster and better, in Win environment.
Linux users -count me in-  will almost certainly stick like glue to command-line interface.

Wanna see QT at its best? Go and download a certain anti-malware (which I won't mention here) and stopwatch at the ready count the seconds between double clicking its desktop icon and the GUI to appear

boost pre-compiled libraries are shared versions (useful if you don't want to compile boost and you don't plan to use your binaries on another computer)
although compiling static boost libraries is not a great task
boost static lib have a "s" in their name http://www.boost.org/doc/libs/1_42_0/more/getting_started/unix-variants.html#library-naming
libraries are built in stage/lib folder

btw, when i updated cmake to 3.8 (from 3.4.3), i guess findboost has changed because i must now type
with forward slash instead of
previously (and with backslash)