Welcome, Guest.
Username: Password: Remember me

TOPIC: Compiling ReShade from GitHub

Compiling ReShade from GitHub 1 year 6 months ago #1

Would anyone be able to explain to me how to do this? I’m wanting a latest fix and was told to do it this way but have never attempted anything like this before. Do I just download and replace the source code in my current ReShade folder or do I have to download everything from GitHub and compile it all together somehow?
The administrator has disabled public write access.

Compiling ReShade from GitHub 1 year 6 months ago #2

Cheers, crosire =)
The administrator has disabled public write access.
The following user(s) said Thank You: IMeganElisabeth

Compiling ReShade from GitHub 1 year 6 months ago #3

Thank you SO much. So I wouldn’t be able to simply replace the source code files/folders I would need to build it completely from scratch this way?
The administrator has disabled public write access.

Compiling ReShade from GitHub 1 year 6 months ago #4

Sorry to say this, but you should have some basic knowledge of how computer programs work, are developed and what source code is before attempting to compile ReShade.
Cheers, crosire =)
The administrator has disabled public write access.
The following user(s) said Thank You: IMeganElisabeth

Compiling ReShade from GitHub 1 year 6 months ago #5

Hey Crosire,

1) I can't thank you enough for your ReShade framework. Been using it over the last two years, created a bunch of presets and released them over the last year. It's basically changed my life, not exaggerating.

2) Out of curiosity, is there a practical use/benefit for end users and preset creators to compile ReShade manually as described on that README you posted? Very low priority question, of course. Just if you have time one day. Thanks again!
Last Edit: 1 year 6 months ago by AssassinsDecree.
The administrator has disabled public write access.

Compiling ReShade from GitHub 1 year 6 months ago #6

AssassinsDecree wrote:
Out of curiosity, is there a practical use/benefit for end users and preset creators to compile ReShade manually as described on that README you posted?
No. You generally only do that if you want to contribute to ReShade development.
Cheers, crosire =)
The administrator has disabled public write access.
The following user(s) said Thank You: AssassinsDecree

Compiling ReShade from GitHub 1 year 6 months ago #7

I see, very good to know. Also, wow, thanks so much for such a fast response! Have a good one!
The administrator has disabled public write access.

Compiling ReShade from GitHub 8 months 2 weeks ago #8

Rather than starting another "Compiling" thread I thought I'd reply here.

I have ReShade building successfully in Visual Studio 2017. I'm not seeing any errors. However the release is not what I expected. There is a "ReShade64.dll" and some intermediary ".lib" files but that's about it. How do I build to a package/installer that is the same as that downloaded from the ReShade site ?
The administrator has disabled public write access.

Compiling ReShade from GitHub 8 months 2 weeks ago #9

You need to build the "Release Setup" configuration.
The administrator has disabled public write access.
The following user(s) said Thank You: MichaelZFreeman

Compiling ReShade from GitHub 8 months 2 weeks ago #10

Thanks. I have everything building now with all the dependencies. But there is something else.

I use the package manager to install "Fody" and "Costura.Fody" as Visual Studio shows that these packages are missing (as per github.com/Fody/Costura ) but then the build throws ...

Severity	Code	Description	Project	File	Line	Suppression State
Error		Fody: An unhandled exception occurred:
Exception:
Could not load file or assembly 'Mono.Cecil, Version=0.10.0.0, Culture=neutral, PublicKeyToken=1ca091877d12ca03' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
StackTrace:
   at ModuleWeaver..ctor()
   at lambda_method(Closure )
   at InnerWeaver.InitialiseWeavers()
   at InnerWeaver.Execute()
Source:
Costura.Fody
TargetSite:
Void .ctor()
The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)	ReShade Setup

If I try to install Mono.Cecil ( cecil.pe/ ) I get ...
PM> Install-Package Mono.Cecil -Version 0.10.0.0


Attempting to gather dependency information for package 'Mono.Cecil.0.10.0' with respect to project 'ReShade', targeting 'native,Version=v0.0'
Gathering dependency information took 5.12 ms
Attempting to resolve dependencies for package 'Mono.Cecil.0.10.0' with DependencyBehavior 'Lowest'
Resolving dependency information took 0 ms
Resolving actions to install package 'Mono.Cecil.0.10.0'
Resolved actions to install package 'Mono.Cecil.0.10.0'
Retrieving package 'Mono.Cecil 0.10.0' from 'nuget.org'.
Install failed. Rolling back...
Package 'Mono.Cecil.0.10.0' does not exist in project 'ReShade'
Package 'Mono.Cecil.0.10.0' does not exist in folder 'F:\Temp\reshade-4.1.1\packages'
Executing nuget actions took 91.85 ms
Install-Package : Could not install package 'Mono.Cecil 0.10.0'. You are trying to install this package into a project that targets 'native,Version=v0.0', but the package does not 
contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
At line:1 char:1
+ Install-Package Mono.Cecil -Version 0.10.0.0
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Install-Package], Exception
    + FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PackageManagement.PowerShellCmdlets.InstallPackageCommand

The rest of the project I understood such as "imggui" providing ReShade's overlay GUI, but this "Fody" stuff ?

What am I doing wrong at this part of the build ?

EDIT: OK I fixed it. I somehow had managed to miss the "restore" button that the package manager brings up to restore packages that are distributed with ReShade such as Fody/Costura. I had then manually installed them at the package manager command line. This causes endless problems ! Using the automatic way worked although at first VS can't find " ..\packages\Costura.Fody.1.6.2\build\dotnet\Costura.Fody.targets.". It does find it after a restart. So now I have the final .exe that brings up the usual installation Wizard.
Last Edit: 8 months 1 week ago by MichaelZFreeman. Reason: Fody.Costura problem solved.
The administrator has disabled public write access.