I believe I've sent a similar support post before. This is NOT just for TMS FNC Core installation.
Every time new TMS versions come out and I try to update TMS controls, I have the following problem. The installer fails because of the filename or extension being too long. I know it's because of the "path" being too long. This is a sample of the error I get:
C:\Program Files (x86)\Embarcadero\Studio\22.0\Bin\CodeGear.Delphi.Targets(412,5): error MSB6003: The specified task executable "dcc" could not be run. The filename or extension is too long [C:\Users\mike\AppData\Local\tmssoftware\registered\TMS FNC Core\TMSFNCCorePkgDXE14.dproj
Believe me, I don't have a lot of non-TMS third-party installations. Installations fail ONLY with TMS installations. All other third-parties install with no problem.
Furthermore, there is nothing I can delete from the "path" environment variable.
FYI, to tackle the problem, this is the ONLY thing that helps; which is what I do when an update comes out every single time:
go to the library path of EACH PLATFORM
use "Update all Using Environment Variables"
go to the browsing path of EACH PLATFORM
use "Update all Using Environment Variables"
I believe a solution CAN be found. If other third-party installations work OK, there should be a way to do it. This is too tedious for us with each update.
I downloaded the GUI version. I entered my credentials, but all of my products installed have a "not installed" status. Do I need to unistall everything from the "TMS Subscription Manager 2" and reinstall from the TMS Smart Setup GUI, or I can just reinstall everything one buy one and it will overwrite the ones installed by the "TMS Subscription Manager 2"?
You need to uninstall all products first, then configure TMS Smart Setup. TMS Smart Setup is a separate new installation that does not use the same techniques as subscription manager does. It for instance, does not add library paths unless necessary.
Smart Setup will help you a lot. Anyway, I'd like to share my solution when paths get too long.
I use SUBST drive letters, or define them directly in windows registry, so it'll be availabe to all users (sometimes you run things "as administrator", and subst letters are "per user" - must be run in administrador's user context too).
Which means the macOS SDK is not properly configured for the IDE you are using, please either ignore this error (if you have no intention of using macOS), or configure the macOS SDK properly by running an empy sample on the mac first.