CasparCG server 2.3 Edit Source Code

samir_assaad · November 29, 2021, 8:31pm

Hello All ,
any one can help me how can edit casparCG server like 2.3 because 2.0 can edit with visual studio .
Thanks

zcybercomputing · December 1, 2021, 3:59am

If you look at the source code on github, I think you will find build instructions for visual studio in building.md.

CasparCG/server/blob/master/BUILDING.md

Building the CasparCG Server
============================

The CasparCG Server source code uses the CMake build system in order to easily
generate build systems for multiple platforms. CMake is basically a build
system for generating build systems.

On Windows we can use CMake to generate a .sln file and .vcproj files. On
Linux CMake can generate make files or ninja files. Qt Creator has support for
loading CMakeLists.txt files directly.

Windows
=======

Development using Visual Studio
-------------------------------

1. Install Visual Studio 2017.

2. Install CMake (http://www.cmake.org/download/).

This file has been truncated. show original

Sidon · December 2, 2021, 10:25am

I have been trying to compile from the sln I created with Cmake and I also encountered some problems. I don’t have a lot of experience with Cmake or VS so

The Cmake process was apparently OK, but when creating the actual caspar.exe folder with VS, upon opening it, it complained about missing the “locale” folder, related to the CEF if I’m not mistaken. The good news is that it can be copied into the Caspar folder and that solves it, but how could I make it so it gets compiled into the appropiate folder automatically?

It also complained about the OpenGL .dlls, it was missing the “swiftshader” folder. Also solved when copying it manually, but ideally the project should handle this too? or am I mistaken?

Anyone has encountered this?

Thanks

zcybercomputing · December 2, 2021, 11:23pm

That sounds like dependency issues. The solution is to either change your build directory to a folder that has those dependencies, or copy the dependencies to your build folder.