https://github.com/hkneptune/CopyHandler

A Copy of Copy Handler Source Code. This repository is just a mirror of the Copy Handler source code. Please do not send pull requests.
https://github.com/hkneptune/CopyHandler

Last synced: 5 months ago
JSON representation

A Copy of Copy Handler Source Code. This repository is just a mirror of the Copy Handler source code. Please do not send pull requests.

• Host: GitHub
• URL: https://github.com/hkneptune/CopyHandler
• Owner: hkneptune
• License: gpl-2.0
• Created: 2020-03-15T17:05:56.000Z (about 5 years ago)
• Default Branch: master
• Last Pushed: 2022-10-10T13:26:16.000Z (over 2 years ago)
• Last Synced: 2024-08-03T22:16:14.723Z (8 months ago)
• Language: C
• Homepage: https://www.copyhandler.com/
• Size: 12.8 MB
• Stars: 3
• Watchers: 1
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: readme.build.txt
  • Changelog: changelog.html
  • License: License.txt

Awesome Lists containing this project

• jimsghstars - hkneptune/CopyHandler - A Copy of Copy Handler Source Code. This repository is just a mirror of the Copy Handler source code. Please do not send pull requests. (C)

README

        
To build Copy Handler from source code, you need to have:

- Visual Studio 2008 (at least standard edition, because of dependencies on MFC) + SP1 + newest Visual Studio updates

- Newest Windows SDK

- Debugging tools for Windows (needed for crash dump generation) - seems to be integrated with newer Windows SDKs

Copy Handler project depends on:

- Boost libraries (http://www.boost.org)

Common part:

    bootstrap.bat

	

1. Visual Studio 2008

     for x64 and x32 respectively

        bjam --toolset=msvc-9.0 address-model=64 define=_BIND_TO_CURRENT_VCLIBS_VERSION --build-type=complete --stagedir=lib-9.0\x64 stage

        bjam --toolset=msvc-9.0 address-model=32 define=_BIND_TO_CURRENT_VCLIBS_VERSION --build-type=complete --stagedir=lib-9.0\x32 stage

2. Visual Studio 2013

CH that is built with VS2013 uses the XP targeting to allow it to run with Windows XP.

Because of that, boost also needs to be built with this kind of targeting.

Based on MS article:

http://blogs.msdn.com/b/vcblog/archive/2012/10/08/10357555.aspx

The environment needs to be set up first, so

for x32:

    set INCLUDE=%ProgramFiles(x86)%\Microsoft SDKs\Windows\7.1A\Include;%INCLUDE%

    set PATH=%ProgramFiles(x86)%\Microsoft SDKs\Windows\7.1A\Bin;%PATH%

    set CL=/D_USING_V110_SDK71_;%CL%

    set LIB=%ProgramFiles(x86)%\Microsoft SDKs\Windows\7.1A\Lib;%LIB%

    set LINK=/SUBSYSTEM:CONSOLE,5.01 %LINK%

    bjam --toolset=msvc-12.0 address-model=32 define=_BIND_TO_CURRENT_VCLIBS_VERSION --build-type=complete --stagedir=lib-12.0\x32 stage

for x64:

    set INCLUDE=%ProgramFiles(x86)%\Microsoft SDKs\Windows\7.1A\Include;%INCLUDE%

    set PATH=%ProgramFiles(x86)%\Microsoft SDKs\Windows\7.1A\Bin;%PATH%

    set CL=/D_USING_V110_SDK71_;%CL%

    set LIB=%ProgramFiles(x86)%\Microsoft SDKs\Windows\7.1A\Lib\x64;%LIB%

    set LINK=/SUBSYSTEM:CONSOLE,5.02 %LINK%

    bjam --toolset=msvc-12.0 address-model=64 define=_BIND_TO_CURRENT_VCLIBS_VERSION --build-type=complete --stagedir=lib-12.0\x64 stage

This was tested on boost 1.57 with VS2013 Update 4 Community Edition.

There are also batch scripts prepared in tools/ to help with building boost for VS2013.