You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Inside an implementation method, I'm using the symlink method from the repository context to "map" a set of files into an expected location, like this:
repo_ctx.symlink(location + "\\Lib\\x64", "lib")
The issue is that x64 is hardcoded and thus not desirable as I'm trying to cross build for x86 targets with the --cpu x64_x86_windows flag.
At first, I thought about using repo_ctx.os.arch but this is not working because it's returning the operating system architecture, not the one I'm targeting with the --cpu flag.
Is it something that I can find in the repo_ctx.attr field? If yes, would you have an example?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
Inside an implementation method, I'm using the
symlinkmethod from the repository context to "map" a set of files into an expected location, like this:The issue is that
x64is hardcoded and thus not desirable as I'm trying to cross build for x86 targets with the--cpu x64_x86_windowsflag.At first, I thought about using
repo_ctx.os.archbut this is not working because it's returning the operating system architecture, not the one I'm targeting with the--cpuflag.Is it something that I can find in the
repo_ctx.attrfield? If yes, would you have an example?Thanks for your help.
Beta Was this translation helpful? Give feedback.
All reactions