-
Notifications
You must be signed in to change notification settings - Fork 94
production_debug
title: Client Debugging in Production description: Debugging the client on a production server published: true date: 2023-03-16T22:56:53.405Z tags: editor: markdown dateCreated: 2021-06-09T14:07:49.345Z
Replace
Y:\ryzomcore
with your root path in the following guide. {.is-info}
Ensure you have a fully patched production client. This technique will use its data.
Make sure your Y:\ryzomcore\code repository is checked out at the production revision, or a revision that is network and data compatible with the production build.
Open the Y:\ryzomcore\build\dev_x64\RyzomCore.sln project, and switch it to Debug mode.
Set the Ryzom, Client - Ryzom Core project as the Startup Project. (Right click, set as Startup Project.)
Go to the project Properties (Right click), select the Debugging properties and switch to All Configurations.
Change Working Directory to the folder where your production client is installed, for example Y:\ryzomclassic\pipeline\client_install_playing.
On Environment, hit the arrow down on the right, choose Edit, and enter the environment PATH for your extenal libraries. For example, the following environment.
PATH=C:\2019q4_external_v142_x64\zlib\bin;C:\2019q4_external_v142_x64\curl\bin;C:\2019q4_external_v142_x64\openssl\bin;C:\2019q4_external_v142_x64\libjpeg\bin;C:\2019q4_external_v142_x64\libpng\bin;C:\2019q4_external_v142_x64\libiconv\bin;C:\2019q4_external_v142_x64\libxml2\bin;C:\2019q4_external_v142_x64\freetype\bin;C:\2019q4_external_v142_x64\squish\bin;C:\2019q4_external_v142_x64\ogg;C:\2019q4_external_v142_x64\vorbis\bin;C:\2019q4_external_v142_x64\openal-soft\bin;C:\2019q4_external_v142_x64\lua\bin;C:\2019q4_external_v142_x64\luabind\bin;C:\2019q4_external_v142_x64\mariadb-connector-c\bin;C:\2019q4_external_v142_x64\assimp\bin;C:\2019q4_external_v142_x64\qt5\bin;C:\2019q4_external_v142_x64\qt5\plugins;%PATH%
QT_PLUGIN_PATH=C:\2019q4_external_v142_x64\qt5\plugins
Hit Start Debugging.