Thank you.
Yes, the vcvars file is present in that folder.

$ cygpath -d "C:\Program Files\Microsoft Visual
Studio\2022\Community\VC\Auxiliary\Build"
cygpath: cannot create short name of C:\Program Files\Microsoft
VisualStudio\2022\Community\VC\Auxiliary\Build



On Wed, Jul 3, 2024 at 2:57 AM Daniel Jeliński <djelins...@gmail.com> wrote:

> Hi Anil,
> Can you check what the following command prints on your machine?
> $ cygpath -d "C:\Program Files\Microsoft Visual
> Studio\2022\Community\VC\Auxiliary\Build"
>
> I assume you have this directory on your machine, and it contains a
> file named "vcvars64.bat"
>
> The above command should print a path without spaces. If the command
> fails or there are any spaces in the output, that's where you should
> focus your search.
>
> The other thing to check is if you have a case-sensitive file system.
> Configure looks for file named (note lowercase in the last 3
> directories):
> "C:\Program Files\Microsoft Visual
> Studio\2022\Community\vc\auxiliary\build\vcvars64.bat"
>
> and from the logs you provided it looks like that file can't be found.
>
> By the way, the above paths were used when I started configure with:
> $ bash configure --with-tools-dir="C:\Program Files\Microsoft Visual
> Studio\2022\Community\VC\Auxiliary\Build"
>
> ..and on my machine that configure command succeeded.
> Regards,
> Daniel
>
> wt., 2 lip 2024 o 23:16 Anil <1dropafl...@gmail.com> napisał(a):
> >
> > trimming earlier message as it was over 500Kb with attachment. Including
> configure.log
> >
> >
> > On Tue, Jul 2, 2024 at 2:00 PM Anil <1dropafl...@gmail.com> wrote:
> >>
> >> Thank you.
> >> I have attached both config.log and configure.log to this email.
> >> Anil
> >>>
> >>>
>

Reply via email to