cannot find valid Visual Code Studio install

[Erik Joelsson]

Filed https://bugs.openjdk.java.net/browse/JDK-8249255

/Erik

On 2020-07-13 11:04, Erik Joelsson wrote:
> There seems to be something with the absolute path elimination that 
> doesn't work when the workspace is located inside the c:/cygwin64 dir. 
> As a workaround, you can either try moving the source to a directory 
> outside of c:/cygwin64 or run configure with 
> --enable-absolute-paths-in-output.
>
> I'm still investigating the exact cause.
>
> /Erik
>
> On 2020-07-12 00:46, Ty Young wrote:
>>
>> On 7/10/20 7:43 AM, Erik Joelsson wrote:
>>>
>>> On 2020-07-09 15:04, Ty Young wrote:
>>>>
>>>> On 7/9/20 3:20 PM, Erik Joelsson wrote:
>>>>>
>>>>> On 2020-07-09 12:56, Ty Young wrote:
>>>>>>
>>>>>> On 7/9/20 9:22 AM, Erik Joelsson wrote:
>>>>>>> Could you post the full configure command and log please. This 
>>>>>>> sounds weird. You should not be needing clang on Windows.
>>>>>>>
>>>>>>> Also, what source did you clone?
>>>>>>
>>>>>>
>>>>>> On linux right now, but I think it's because I'm using the 
>>>>>> jextract branch of panama-foreign:
>>>>>>
>>>>>>
>>>>>> https://github.com/openjdk/panama-foreign
>>>>>>
>>>>> This was a very crucial piece of information that you left out 
>>>>> initially. Panama uses libclang for specific new features in that 
>>>>> project. I don't know the details on how to build that project. 
>>>>> You will need to ask people working on Panama for details on any 
>>>>> special needs they have.
>>>>>
>>>>> I would recommend you clone the mainline jdk and get that to work 
>>>>> first as a baseline.
>>>>
>>>>
>>>> Just did, as well as a version of panama-foreign that should work 
>>>> but doesn't need clang(foreign-abi).
>>>>
>>>>
>>>> It configures now, but fails to build with errors like:
>>>>
>>>>
>>>> c1xx: fatal error C1083: Cannot open source file: 
>>>> '../../../..c:/cygwin64/home/young/jdk-master/jdk-master/build/windows-x86_64-server-release/hotspot/variant-server/libjvm/objs/BUILD_LIBJVM_pch.cpp': 
>>>> No such file or directory
>>>>
>>>>
>>> Could you send your configure.log, spec.gmk and the exact command 
>>> lines you used?
>>>
>>> /Erik
>>
>>
>> Attached.
>>
>>
>>>
>>>> Basically every file within the objs file is missing... but it 
>>>> isn't actually. I can see them in Windows explorer just fine and 
>>>> configure doesn't throw any errors.
>>>>
>>>>
>>>> Thinking that this was an issue with file depth, I moved the cloned 
>>>> source code to root as "jdk-build". It still fails in the same 
>>>> spot. Both of them.
>>>>
>>>>
>>>>>
>>>>> /Erik
>>>>>
>>>>>>
>>>>>> I remember there being a commit some time ago that requires clang 
>>>>>> to be specified on panama-dev, but I've never had to do that 
>>>>>> under Linux. This is my first time compiling on Windows so I have 
>>>>>> no idea what's going on.
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> /Erik
>>>>>>>
>>>>>>> On 2020-07-09 07:04, Ty Young wrote:
>>>>>>>>
>>>>>>>> On 7/9/20 7:37 AM, Erik Joelsson wrote:
>>>>>>>>> Hello Ty,
>>>>>>>>>
>>>>>>>>> Microsoft Visual Studio 2019 or 2017, any edition, should 
>>>>>>>>> work. My best guess is that you skipped installing the 
>>>>>>>>> necessary parts of it. Run the installer again, click "Modify" 
>>>>>>>>> and make sure you have "Desktop development with C++" ticked in.
>>>>>>>>
>>>>>>>>
>>>>>>>> That worked, thanks!
>>>>>>>>
>>>>>>>>
>>>>>>>> It still didn't configure though. Now it's complaining about 
>>>>>>>> not having clang installed. Once I installed clang and 
>>>>>>>> clang-devel, it then complained about not having version 9 
>>>>>>>> installed. The latest version from cygdrive was 8<something>, 9 
>>>>>>>> is not an option. If I try to trick it by copying and renaming 
>>>>>>>> the older 8<something> version, it then complains about Index.h 
>>>>>>>> being found but not being compileable and to report it here.
>>>>>>>>
>>>>>>>>
>>>>>>>> Any advice here? I tried installing more extra stuff from 
>>>>>>>> Visual Code Studio to see if it'd help, but it doesn't or I'm 
>>>>>>>> not installing the right things.
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> /ERik
>>>>>>>>>
>>>>>>>>> On 2020-07-09 01:29, Ty Young wrote:
>>>>>>>>>> Hopefully this is the right place. Don't shoot me if it 
>>>>>>>>>> isn't, please.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I'm trying to build the JDK from Windows 10. I got so far as 
>>>>>>>>>> to configure failing on finding what it needs from the Visual 
>>>>>>>>>> Code Studio install via command line:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> configure: Found Visual Studio installation at 
>>>>>>>>>> /cygdrive/c/Program Files (x86)/Microsoft Visual 
>>>>>>>>>> Studio/2019/Community using well-known name
>>>>>>>>>> configure: Warning: None of vc/bin/amd64/vcvars64.bat 
>>>>>>>>>> vc/bin/x86_amd64/vcvarsx86_amd64.bat 
>>>>>>>>>> VC/Auxiliary/Build/vcvarsx86_amd64.bat 
>>>>>>>>>> VC/Auxiliary/Build/vcvars64.bat were found, Visual Studio 
>>>>>>>>>> installation not recognized. Ignoring
>>>>>>>>>> configure: Found Visual Studio installation at 
>>>>>>>>>> /cygdrive/c/Program Files (x86)/Microsoft Visual 
>>>>>>>>>> Studio/2019/Community using well-known name
>>>>>>>>>> configure: Warning: None of vc/bin/amd64/vcvars64.bat 
>>>>>>>>>> vc/bin/x86_amd64/vcvarsx86_amd64.bat 
>>>>>>>>>> VC/Auxiliary/Build/vcvarsx86_amd64.bat 
>>>>>>>>>> VC/Auxiliary/Build/vcvars64.bat were found, Visual Studio 
>>>>>>>>>> installation not recognized. Ignoring
>>>>>>>>>> configure: Cannot locate a valid Visual Studio installation, 
>>>>>>>>>> checking current environment
>>>>>>>>>> checking for Visual Studio variables... not found
>>>>>>>>>> configure: Cannot locate a valid Visual Studio or Windows SDK 
>>>>>>>>>> installation on disk,
>>>>>>>>>> configure: nor is this script run from a Visual Studio 
>>>>>>>>>> command prompt.
>>>>>>>>>> configure: Try setting --with-tools-dir to the VC/bin 
>>>>>>>>>> directory within the VS installation
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> However there is no "bin" directory in this installation, at 
>>>>>>>>>> least not one that contains any of the specified files. This 
>>>>>>>>>> is Visual Code 2019 Community, but I've tried the 
>>>>>>>>>> Professional version too. The building document doesn't 
>>>>>>>>>> specify which version, nor does it tell me how to fix this.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> How do I get this to work via command line?
>>>>>>>>>>