Repository navigation
Guide for build and installation #489
Description
Tools needed
- VS2017 or higher with the following packages ("Workloads" tab in Visual Studio Installer) :
1.1Desktop Development with C++.
1.2Universal Windows Platform Development.
1.3Windows 10 SDK (10.0.18362.0).
1.4 If you're running VS2019, you'll also need to install eitherv141 Toolsetorv142 Toolset. - Git command-line tool.
- Nuget.exe (Needed in build step 3, can be found in
Terminal/dep/nuget).
Build Steps
git clonethis repository, not download .zip file.- Run
git submodule update --init --recursivein Terminal folder. - Run
nuget restore OpenConsole.sln(This step can be skipped, then Visual Studio should warn you that there are packages to restore - then restore). - Open
OpenConsole.slnwith Visual Studio. - Build whole solution(F7) with your platform(
x86/x64) andreleasemode, you may need to fix some build errors:
5.1 C2220 and code page warnings: All errors and warnings are encoding error of unicode characters, a helpful workaround is to modify corresponding file encoding toUTF-8 BOM(Notepad++ is recommended).
5.2 Errors insrc/tools/vtpipeterm/main.cpp: In addtion, you should also addu8prefix before string literals with unicode characters, e.g. line395,398,401and404.
Workaround
Try build with PR 458 or PR 549, both of them can build successfully.
Installation
Unfortunately, the generated .appx doesn't have any certificates, so it cannot be installed via double-click or powershell, the only way to install is to deploy the solution in VS.
- Open
Windows Settings-Upgrade & Security-For Developers, switchApp sourcestoDeveloper mode. - Right click on
CascadiaPackageproject (underSolution/Terminal), selectDeploy Solutionto install, then you'll findWindows Terminal (Preview)in start menu.
Settings
After open the terminal, you can't see any menu buttons.
Just press Ctrl + T to open a new tab, and you'll see a drop-down button in the tab bar.
Click it and select Settings, then you can modify the configuration via opened profiles.json.
Add WSL
- Create a new session in
profiles, with content copied fromprofiles/cmd. - Give it a new
guid. - Give it a new
name, such asWSL. - Specify its
commandlinetowsl.exe.
Then you'll find WSL in the drop-down menu of tab bar.
Here're sample codes:
{
"guid": "{09dc5eef-6840-4050-ae69-21e55e6a2e62}",
"name": "WSL",
"colorscheme": "Campbell",
"historySize": 9001,
"snapOnInput": true,
"cursorColor": "#FFFFFF",
"cursorShape": "bar",
"commandline": "wsl.exe",
"fontFace": "Consolas",
"fontSize": 12,
"acrylicOpacity": 0.75,
"useAcrylic": true,
"closeOnExit": false,
"padding": "0, 0, 0, 0"
}Reacted by Dmitry Smolyakov, Fei Chong, Khie Biggs, Navee, Prince B. A., Max Buschner, a458442068, tian, fanzhihang, ShrinkWrapper and 411 more
Reacted by Alex Stepankov, Mohd Arif Khan, Renato Burton and Mayank Chauhan
Reacted by Ankit Sinha, Sasidhar Kasturi, Robert Gebhardt de Oliveira Junior, invisiblearts, Kashyap Patel, Jorge Ferreira, Đào Văn Đức, David Refoua, Delete-Button, leesue and 14 more
Reacted by Matt Bengston, Kecai Liu, Songtronix, Aleksandr Kostin, Lakr, Nizar Selander, Sebastian Knackstedt, Muta, Kevin M. Harrington MCDST, Poy Chang and 25 more
Reacted by invertedburger, Uwe Keim, cepiec000 and fengzhao
Reacted by iKlsR, Muta, Kasper Laursen, Hayden, Ederson Fuzinato, whc2001, Junghun Kim, Kashyap Patel, Jorge Ferreira, David Refoua and 31 more
Reacted by Vincenzo Mauro, Kecai Liu, Songtronix, Aleksandr Kostin, Lakr, driver1998, Muta, Hayden, Jay Wang, Kutsuzawa Ryo and 28 more
Reacted by Lakr, Muta, behamann, HelloWorDomain, Kashyap Patel, Matt Bengston, Christian Parpart, chromedays, cyh-ustc, Eric and 5 more
Activity
[-]Instruction for build new Terminal[/-][+]Guide for build new Terminal[/+]kev-landry commentedon May 7, 2019
Thank you.
yanke1311 commentedon May 7, 2019
thanks!
ShrinkWrapper commentedon May 7, 2019
Thanks a bunch!
ecampidoglio commentedon May 7, 2019
This information should be included in the
Building the Codesection of the README file.pavelovcharov commentedon May 7, 2019
Windows 1903 is required to deploy Windows Terminal
#437 (comment)
AregevDev commentedon May 7, 2019
Can I build it with VS 2019?
NikolausWeiss commentedon May 7, 2019
I've been trying for a few hours with no success. I have given up and am currently installing VS 2017
AregevDev commentedon May 7, 2019
Same as you
HowBoring commentedon May 7, 2019
I'm afraid you can't, I have got 23 FAILED to build with VS2019...
AregevDev commentedon May 7, 2019
Thanks! I am installing VS2017, can't wait to try the new Terminal out!
clearcodecn commentedon May 7, 2019
hello. can I download the binary file of you build ? I don`t want to build it . no environment . 😆
DarryNobi commentedon May 7, 2019
Me, neither. Better try on VS2017 directly. \cry
NikolausWeiss commentedon May 7, 2019
There is a pull request for a branch that fixes the VS 2019 errors: #449
Berrysoft commentedon May 7, 2019
Yes, with hours of patience, and fixing many bugs.
256 remaining items
DHowett-MSFT commentedon Jun 20, 2019
ihdavids The "WSL Background Host" processes are kept around for some time to support WSL background scenarios. This is not exactly a Terminal issue.
simkessy commentedon Jun 20, 2019
I tried to build and I just got this instead:
musm commentedon Jun 20, 2019
I get the same errors. Can anyone help
yzlnew commentedon Jun 21, 2019
It seems that we can get a preview build in mid-June. Is this still on track for a pre-release?
Edit: You can download it form the Microsoft Store now.
adeloyedeji commentedon Jun 22, 2019
And I still get a blank screen?
tahasamar commentedon Jun 23, 2019
Hey can I install it on Windows 7 ??
MartinJohns commentedon Jun 23, 2019
Mohammad Taha Samarghandi (@tahasamar) You can not. Windows 7 is not a supported platform. You need Windows 10.
DHowett-MSFT commentedon Jul 11, 2019
Many of our build and installation issues have been resolved since we moved to Visual Studio 2019 and the newest SDK. This bug is a great archive of our old build problems, but I'm going to close it because I think it's served its purpose. Thanks everyone for the reports!
xpwn3rx commentedon Aug 22, 2019
I can no longer open the program. I have been running builds since a couple days after the source was released. I tried uninstalling and deleting the profile.json files, and the entire folder for the dev version. I also uninstalled the released version (from the store). I am on 18963.1000 insider preview build. I've tried updating source and rebuilding multiple times. The program crashes with this information in the event viewer.
Fault bucket 1289599514809151433, type 5
Event Name: MoBEX
Response: Not available
Cab Id: 0
Problem signature:
P1: WindowsTerminalDev_0.0.1.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 0.0.0.0
P4: 5d5ed050
P5: ucrtbase.dll
P6: 10.0.18963.1000
P7: afa25d02
P8: 00000000000714ae
P9: c0000409
P10: 0000000000000007
Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4461.tmp.mdmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46B4.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46C5.tmp.xml
WPR_initiated_DiagTrackMiniLogger_OneTrace User Logger 20190808 1 Event Collector_0_inject.etl
\?\C:\Users\username\AppData\Local\Temp\WER4704.tmp.etl
WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\?\C:\Users\username\AppData\Local\Temp\WER4715.tmp.etl
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4711.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER477F.tmp.txt
These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_WindowsTerminalD_3c51dde5976618279e5030b5b28a6694657054_a3463a88_ca0aacc6-5135-4050-9eef-60ec5d5348b5
Analysis symbol:
Rechecking for solution: 0
Report Id: 58849b5b-6947-47e5-a83f-e0488d271f72
Report Status: 268435456
Hashed bucket: f6539afacf462710c1e593ed16b72fc9
Cab Guid: 0
I have also tried deleting my source directory and running through the steps to grab it from GIT and init the submodules.
justingoldberg commentedon Oct 11, 2019
Can / will it be ported to windows 7? Or should we stick with ConEmu/CMDer?
KindDragon commentedon Oct 11, 2019
Justin Goldberg (@justingoldberg) Terminal depend on new Windows 10 API
jackluo923 commentedon Oct 11, 2019
Justin Goldberg (@justingoldberg) Use fluent terminal, since it supports pretty much all the MS terminal's functionality (i.e. supports Bash, PowerShell, WSL, cmder and any other ConEMU stuff all at the same time). You won't get WSL though because that's a Win10 feature, but connecting cygwin, docker, ubuntu VM, remote ssh terminals shouldn't be a problem. A the current state, it looks prettier than MS terminal and is based on the same "xterm.js" framework.