Experimental build nag screen for own builds
Started by ddscentral




2 posts in this topic
ddscentral
Member


0
10 posts 2 threads Joined: May 2018
03-27-2020, 06:01 PM -
#1
After the latest pull, I'm getting a nag screen every time I launch RPCS3 which is annoying. 
I prefer doing my own builds from the latest source (with no modifications) over downloading pre-built binaries.
Tried re-downloading the entire source and rebuilding, still getting this nag.
What triggers this nag and what's the intention behind this ?

This nag was added in the commit 70d6a128942569b533b18eb7c678f6f0e80eff83
This post was last modified: 03-27-2020, 06:09 PM by ddscentral. Edit Reason: Added commit hash
Ani
Administrator
*******


16
4,386 posts 106 threads Joined: Aug 2017
03-27-2020, 06:36 PM -
#2
Experimental build warning has been a thing for many years, not anything recent.
It's being triggered unintentionally from a recent CI bug though
    Desktop: Ryzen 7 5800X,   Radeon RX 6800 XT, 2x8G DDR4 3600MHz, Manjaro Linux
     Laptop: Ryzen 9 5900HX,  Radeon RX 6700M,   2x8G DDR4 3200MHz, Manjaro Linux
Old Desktop: AMD FX-8350,     Radeon R9 280X,    2x4G DDR3 1600MHz, Manjaro Linux
ddscentral
Member


0
10 posts 2 threads Joined: May 2018
03-27-2020, 07:26 PM -
#3
Not really a big deal, just wanted to ask because I don't know if this was added intentionally or not.
I've changed my build scripts and wrote a small program to patch git-version.h until this is fixed.


Forum Jump:


Users browsing this thread: 1 Guest(s)