Jump to content

Search the Community

Showing results for tags 'cygwin'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • Announcements and Site News
    • Administration
  • AutoIt v3
    • AutoIt Help and Support
    • AutoIt Technical Discussion
    • AutoIt Example Scripts
  • Scripting and Development
    • Developer General Discussion
    • Language Specific Discussion
  • IT Administration
    • Operating System Deployment
    • Windows Client
    • Windows Server
    • Office


  • AutoIt Team
    • Beta
    • MVP
  • AutoIt
    • Automation
    • Databases and web connections
    • Data compression
    • Encryption and hash
    • Games
    • GUI Additions
    • Hardware
    • Information gathering
    • Internet protocol suite
    • Maths
    • Media
    • PDF
    • Security
    • Social Media and other Website API
    • Windows
  • Scripting and Development
  • IT Administration
    • Operating System Deployment
    • Windows Client
    • Windows Server
    • Office

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start






Found 3 results

  1. Hi, I would like to read the output of my cygwin terminal if it is already up and running. I searched the forum, but I think, the samples were cmd/cygwin needs to be re-run or not yet running. The purpose of the script is to check if compiling is done. Func _JAE_Rebuild_Software ($sSoftwarePath) Local $iMinty = 0 ; Open cygwin process and check one instance only if ProcessExists("mintty.exe") Then $iMinty = ProcessExists("mintty.exe") Else ; Run cygwin if not yet running $iMinty = Run("C:\cygwin\bin\mintty.exe -i /Cygwin-Terminal.ico -", "", @SW_SHOW, $STDIN_CHILD + $STDOUT_CHILD) endif ; Loop to check if cygwin terminal is ready While 1 ; if -sh is not error cygwin is still opening Local $hWnd = WinGetHandle("-sh") If @error Then $hWnd = WinGetHandle("~") Else $hWnd = 0 EndIf ; If true cygwin is ready to be written if $hWnd <> '0x00000000' Then ExitLoop EndIf WEnd ; Change Directory $sSoftwarePath = StringReplace($sSoftwarePath,"\", "/") ClipPut($sSoftwarePath) Send('cd ' & $sSoftwarePath & "{ENTER}" ) ; Get New Class after Change Directory Local $sNewClass = WinGetTitle("[ACTIVE]") ; Sleep for 3 seconds. Sleep(3000) ; Change software path to access the makeFile $sSoftwarePath = StringReplace($sSoftwarePath,"/", "\") ; Open Makefile Local $hFileOpen = FileOpen($sSoftwarePath & "\makefile", $FO_READ) If $hFileOpen = -1 Then Return False EndIf Local $sFileRead = FileReadLine($hFileOpen, 12) Local $sSetSource = _StringBetween($sFileRead, "(", ")", $STR_ENDNOTSTART) Local $message Send('source ' & $sSetSource[0] & '.sh' & "{ENTER}") Send('make clean' & "{ENTER}") WinActivate($sNewClass, "") $hWnd = WinWait($sNewClass,"",1) Local $iPID = WinGetProcess($hWnd) While $iMinty $message &= StderrRead($iPID) If @error Then MsgBox(0,"","error") ExitLoop EndIf WEnd ; I only get blank output here since the while condition produces an error MsgBox(0, "Stdout Read:", $message) EndFunc ;==>_JAE_Rebuild_Software
  2. Before I dive into the specifics of my problem, are there known, fatal issues when running a compiled AutoIt script (.exe file) from a Cygwin Bash script? Am I wasting my time trying to get it to work? If not, then here's my problem: I have 2 compiled AU3 scripts that are normally executed in the background by a Windows service. The Start script is executed by the service with a directory path as a command-line argument, does some processing, and creates a database record. After an external (human) activity finishes, the Stop script is executed, does some more processing, and updates the database record for the directory. The Bash script emulates the service for purposes of re-processing directories that had errors during the "live" pass: it loops through a text file containing a list of failed directories and executes the Start and Stop scripts. If the AU3 script executions are commented-out (e.g., to test other logic in the loop), the Bash script reads through the entire directory-list file; the Start and Stop scripts are treated as if they had run successfully. But if the AU3 scripts are actually executed, the loop exits after the first full iteration (i.e., without skips caused by error-detection). Subsequent runs of the Bash script process one directory each and exit (the list file shrinks with each pass). It seems like something about the execution of the AU3 scripts is changing the Bash loop execution (e.g., causing it to see end-of-file for the directory list file). A puzzling aspect is that an earlier version of the Bash script executed successfully (all directories processed), but in that case the directory list was taken from a Bash array variable rather than a file. Since there could be hundreds (or more) directories requiring re-processing, I modified the Bash script to read from a file, with the intention of making it more robust. Any suggestions for troubleshooting this will be welcome. Outline of the script; the actual script is much longer: #!/bin/bash # Initialize variables... export START_EXEPATH="C:/mydir/StartScript.exe" export STOP_EXEPATH="C:/mydir/StopScript.exe" # Generate (unix) text file containing (unix) directory paths, one per line find C:/somedir -type d [some other criteria...] -print >/tmp/dir_list.out # Core code: let errcnt=0 while IFS='' read -r dpath do # Validate the last component of dpath... dpath_base="$(basename "$dpath")" regexp="some-extended-regexp" if [[ "$dpath_base" =~ $regexp ]]; then dpath_bad=0; else dpath_bad=1; fi if [ $dpath_bad -eq 1 ]; then let errcnt+=1; echo "error message"; continue; fi win_dpath="$(cygpath -a -w "$dpath")" # Run 1st AutoIt script "$START_EXEPATH" "$win_dpath" "another-argument" if [ $? -ne 0 ]; then let errcnt+=1; echo "error message"; continue; fi # Run 2nd AutoIt script "$STOP_EXEPATH" "$win_dpath" if [ $? -ne 0 ]; then let errcnt+=1; echo "error message"; fi done </tmp/dir_list.out echo "$errcnt errors" if [ $errcnt -ne 0 ]; then exit 2; fi exit 0
  3. Hi all ! I work on a tool for automating logon in a business software. This software is a Linux application, displayed in Windows with an EXPORT DISPLAY method, using a X-SERVER (Cygwin/Xterm). The problem is when I use Send or ControlSend, special keys like @ or # (or some other keys needing an AltGr combination), the characters sent are the non-AltGr keys (# become 3, @ become 3 - I use a French keyboard). I tried to send keys to the Linux-Firefox (instead of the business software), but I had the same result. Does anyone has already try to make something like this, with the same issue ? Thanks for help
  • Create New...