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

issue in building and deploying #6252

Closed
shivam284 opened this issue May 29, 2020 · 4 comments
Closed

issue in building and deploying #6252

shivam284 opened this issue May 29, 2020 · 4 comments
Labels
Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@shivam284
Copy link
Contributor

Need help with two issues:

  1. While building the terminal, I got 38 errors in file U8U16Test.cpp.
    errors like this one:
    syntax error: identifier 'length_error'
    'length_error': is not a member of 'std'

I corrected these errors and the build was successful. Does this need to be added to documentation?

  1. I faced some linking errors while deploying the Cascadia Package. The reason(I suppose) was this:
    Build path is:
    terminal\x64\Release
    while deploying, it searches for some libs at this path:
    terminal\bin\x64\Release
    I copied and pasted the content of terminal\x64\Release to terminal\bin\x64\Release and it worked. But I am looking for a permanent solution. Can anyone help?
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels May 29, 2020
@shivam284
Copy link
Contributor Author

@DHowett Please help!!

@zadjii-msft
Copy link
Member

Please search before filing new issues. This is already fixed in master, in #6226

@shivam284
Copy link
Contributor Author

@zadjii-msft #6226 is also fixing the second issue I am facing?

@zadjii-msft
Copy link
Member

I don't really think the second one is a real issue - our build definitely intentionally places some things in both bin\x64\ and x64\, so I'd bet that the error from the first was causing the second error as well. If you apply the patch from #6226 and you're still getting build errors, share them here and I can (try) to help diagnose them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

2 participants