Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add PTY node support for Windows #25

Open
lihop opened this issue Nov 21, 2020 · 0 comments
Open

Add PTY node support for Windows #25

lihop opened this issue Nov 21, 2020 · 0 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@lihop
Copy link
Owner

lihop commented Nov 21, 2020

Currently, the Pseudoterminal node is only supported on Linux and MacOS. Using winpty or conpty it should be possible to support this node on Windows also.

See https://github.com/microsoft/node-pty/tree/master/src/win for an example of how these libraries are used to open a pseudoterminal on windows.

@lihop lihop added the enhancement New feature or request label Nov 21, 2020
@lihop lihop changed the title Add Pseudoterminal node support for Windows Add PTY node support for Windows Jul 3, 2021
@lihop lihop added the help wanted Extra attention is needed label Jul 3, 2021
lihop added a commit that referenced this issue Jul 18, 2021
lihop added a commit that referenced this issue Jul 18, 2021
lihop added a commit that referenced this issue Jul 18, 2021
lihop added a commit that referenced this issue Jul 18, 2021
lihop added a commit that referenced this issue Jul 18, 2021
lihop added a commit that referenced this issue Jul 18, 2021
Currently only works when building with debug target. On GitHub actions
target release results in linking errors.

Part of #25.
lihop added a commit that referenced this issue Jul 18, 2021
Currently only works when building with debug target. On GitHub actions
target release results in linking errors. So disable PTY for release
builds.

Part of #25.
lihop added a commit that referenced this issue Jul 25, 2021
Makes for pretty paths when extending scripts:
`extends "res://addons/godot_xterm/terminal.gd"`
vs.
`extends "res://addons/godot_xterm/nodes/terminal/terminal.gd"`

Currently "res://addons/godot_xterm/pty.gd" is acutally `pty_unix.gd`.
This is okay for now as the PTY node is only supported on Unix
platforms. However, we will need to sort it out when adding Windows
support as part of #25.

Also remove the GDXterm namespace.
lihop added a commit that referenced this issue Jul 25, 2021
Makes for pretty paths when extending scripts:
`extends "res://addons/godot_xterm/terminal.gd"`
vs.
`extends "res://addons/godot_xterm/nodes/terminal/terminal.gd"`

Currently "res://addons/godot_xterm/pty.gd" is acutally `pty_unix.gd`.
This is okay for now as the PTY node is only supported on Unix
platforms. However, we will need to sort it out when adding Windows
support as part of #25.

Also remove the GDXterm namespace.
lihop added a commit that referenced this issue Jul 25, 2021
Makes for pretty paths when extending scripts:
`extends "res://addons/godot_xterm/terminal.gd"`
vs.
`extends "res://addons/godot_xterm/nodes/terminal/terminal.gd"`

Currently "res://addons/godot_xterm/pty.gd" is acutally `pty_unix.gd`.
This is okay for now as the PTY node is only supported on Unix
platforms. However, we will need to sort it out when adding Windows
support as part of #25.

Also remove the GDXterm namespace.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant