Integrating vcpkg under system user with TeamCity #51485
Unanswered
naimkingston
asked this question in
Q&A
Replies: 2 comments
-
|
I also read something about creating a new user account for TeamCity to use instead of running it on the system account ... which I guess means that |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
There are known issues with running vcpkg as the system user, #35638. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I've successfully gotten vcpkg running (with builds working) on my dev machine using the standard instructions (clone git, build vcpkg.exe, run
vcpkg integrate install), and now I'm trying to get it running under a TeamCity build agent, which is running under the system user.The issue is that when I remote into the build agent and install vcpkg and run
vcpkg integrate install, the files (vcpkg.path.txt,vcpkg.user.propsandvcpkg.user.targets) are added to the%localappdata%\vcpkgfolder under the logged in user (i.e. me), but since the TeamCity build agent is running as the system user, these files aren't created in an appropriate location for an msbuild instance running under the build agent to find.I tried a suggestion to create a
VCPKG_ROOTsystem environment variable, but that didn't seem to do anything.The only other suggestion I've seen is to manually add the
vcpkg.user.propsandvcpkg.user.targetsfile to each *.vcxproj file and hardcode the path to thevcpkgfolder ...Am I missing something? Is there no other way to get integration for an agent running under the system user?
Beta Was this translation helpful? Give feedback.
All reactions