[
https://issues.apache.org/jira/browse/ARROW-11192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17285617#comment-17285617
]
Ian Cook commented on ARROW-11192:
----------------------------------
I believe the way to do this is to initialize Visual Studio by running the
{{vcvarsall.bat}} or {{VsDevCmd.bat}} command, e.g. for VS 2019 Community:
{code:java}
"C:\Program Files (x86)\Microsoft Visual
Studio\2019\Community\Common7\Tools\VsDevCmd.bat" -arch=amd64
{code}
then activate the conda environment, then in the same command prompt, start the
VS IDE by running the command
{code:java}
devenv.exe
{code}
possibly with
[switches|https://docs.microsoft.com/en-us/visualstudio/ide/reference/devenv-command-line-switches?view=vs-2019].
> [Documentation] Describe opening Visual Studio so it inherits a working env
> ---------------------------------------------------------------------------
>
> Key: ARROW-11192
> URL: https://issues.apache.org/jira/browse/ARROW-11192
> Project: Apache Arrow
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 2.0.0
> Reporter: Ben Kietzman
> Assignee: Ian Cook
> Priority: Major
> Fix For: 4.0.0
>
>
> [https://arrow.apache.org/docs/developers/cpp/windows.html#building-using-visual-studio-msvc-solution-files]
> describes setting up the conda development environment but if VS is opened
> normally then it will not inherit those env vars, conda will not be
> activated, etc. So building will fail. The documentation should help new
> developers go from zero to debugging in VS
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
