It says "Use XDG standard path instead of the standard PCSX2 path". XDG_STD switches around what paths pcsx2 uses. And yes most of those options are typically fine to leave as default.
Those settings are usually ones you want kept on the default anyways, though. With the other ones, the wrong variables were being set, and one of them isn't cooperating with me.
#Pcsx2 a file cannot be created code#
What happened with that one is that that option was just completely missing from the gtk version of the dialog box, so I added it, but forgot that it needed to be added to the ini code as well. Yeah, that's one of the two I already fixed locally. DXDG_STD=TRUE: Not sure what this does, can someone explain?Īny other options I'm missing that might be useful to support a release build on a modern proc/gpu for normal use-cases? DPACKAGE_MODE=TRUE: Uses "safe" default settings and is recommended for release builds
DGTK3_API=TRUE: Needed for experimental GTK3 support as pcsx2 defaults to GTK2 (I've noticed cases of the UI hanging if certain options such as speedhacks are changed ingame, not sure if this can be traced to the "experimental" status or not). DGSDX_LEGACY=TRUE: No longer used or needed built in, and is therefore recommended for modern processors. Compiling without this option builds a single "libGSdx.so" plugin which includes support for AVX2 etc. DDISABLE_ADVANCE_SIMD=TRUE: Builds three separate gsdx plugins (SSE2, SSE4.1 and AVX2). DCMAKE_BUILD_TYPE=Release: Recommended for release builds as name implies DCMAKE_BUILD_STRIP=FALSE: Helpful for debugging/stack trace analysis but not recommended for release builds for performance reasons I've put together some notes based on the helpful list provided in his first post above and thoughts others have shared, would appreciate any changes or additions that might help document a solid and well-understood list for release purposes. Getting back to my post above regarding cmake options before I close this issue.
0 kommentar(er)
