Hi team. Please ignore this query as I was checking for the binaries in the 
TEMP folder, which I now realize is only for storing files temporarily before 
the binaries(zip and exe) are generated in the Windows folder. I was able to 
find the zip generated in the brltty/Windows folder.

Thanks,
Vasundhara.
________________________________
From: Vasundhara Pant <[email protected]>
Sent: Saturday, May 25, 2024 2:03 PM
To: [email protected] <[email protected]>
Cc: Shivaramkrishna Ramalaxmaiah Tirumala 
<[email protected]>
Subject: Re: Issues while building BrailleTTY on Windows

Resending this as the previous mail was rejected as I had not subscribed to the 
mailing list.

Thanks,
Vasundhara
________________________________
From: Vasundhara Pant
Sent: Friday, May 24, 2024 4:33 PM
To: [email protected] <[email protected]>
Cc: Shivaramkrishna Ramalaxmaiah Tirumala 
<[email protected]>
Subject: Issues while building BrailleTTY on Windows

Hi team.
I am Vasundhara, a software developer at Microsoft working on Narrator team. We 
use the BrailleTTY Open source code in Narrator to interact with Braille 
devices. Currently, we are trying to migrate our build process to Onebranch 
(Azure DevOps build system for Windows components). For that, we have to build 
the BrailleTTY code using msys1 (as that is what it currently supports).
I was trying out the local build of BrailleTTY to understand the entire process 
and faced issues in the mkwin script. The steps I followed were:


  1.
 Install MINGW having latest GCC 9.2.0.
  2.
Install Python version 3.4 at the default location, (Note:It should be a 
version older than 3.5, problem here (Building on Windows 10 using mingw32 · 
Issue #2751 · statsmodels/statsmodels · 
GitHub<https://github.com/statsmodels/statsmodels/issues/2751>)). I have used 
Python 3.4.4 Windows x86 MSI installer to install python.
  3.
Checkout the brltty via git clone from here 
(https://github.com/brltty/brltty.git)
  4.
Run msys (Windows batch file) in admin mode from the location C:\MinGW\msys\1.0.
  5.
 Go to Windows directory in brltty (./brltty/Windows)
  6.
Run ./winSetup from Windows Directory
  7.
cd ..
  8.
Run ./autogen in the main root directory of the checked out code (brltty)
  9.
Again go back to Windows directory. (brltty/Windows)
  10.
mkwin -u libusb-1.0 -P /C/Python34 ..

In the last step, while running mkwin, I'm getting the following output:
[cid:b39fb307-a6c4-489d-9c17-27c67d994f9d]

which has the warnings:
brlapi.auto.c: In function '__Pyx_ImportType_3_0_10':
brlapi.auto.c:33110:13: warning: unknown conversion type character 'z' in 
format [-Wformat=]
33110 |             "%s.%s size changed, may indicate binary incompatibility. "
      |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
brlapi.auto.c:33111:24: note: format string is defined here
33111 |             "Expected %zd from C header, got %zd from PyObject",
      |                        ^
brlapi.auto.c:33110:13: warning: unknown conversion type character 'z' in 
format [-Wformat=]
33110 |             "%s.%s size changed, may indicate binary incompatibility. "
      |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
brlapi.auto.c:33111:47: note: format string is defined here
33111 |             "Expected %zd from C header, got %zd from PyObject",
      |                                               ^
brlapi.auto.c:33110:13: warning: too many arguments for format 
[-Wformat-extra-args]
33110 |             "%s.%s size changed, may indicate binary incompatibility. "


I checked the location C:\Users\<username>\AppData\Local\Temp but could not 
find any brltty-mkwin folder generated there. Can you please help me understand 
these warnings and point out if I'm doing anything wrong in the process? It'll 
be really helpful for us.

Thanks & Regards,
Vasundhara Pant
_______________________________________________
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: [email protected]
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Reply via email to