Closed xet7 closed 5 years ago
For the future, could a log this long go on a pastebin site instead, and just the trimmed logs with errors be posted here? Makes it a bit easier to navigate.
At a glance, this seems to be due to the "native" path backing type on Windows being a wstring, and it's passed to places that expect standard strings. I'm guessing calling .string()
instead of .native()
might fix it...
For the future, could a log this long go on a pastebin site instead, and just the trimmed logs with errors be posted here? Makes it a bit easier to navigate.
Indeed.
At a glance, this seems to be due to the "native" path backing type on Windows being a wstring, and it's passed to places that expect standard strings.
That's probably the problem, yes.
@xet7 I replaced .native()
with .string()
as suggested by refi. Does it compile now?
@Quintus
Yes it does work now. I uploaded alpha package exe here: https://ftp.secretchronicles.org/alpha/
It does install and start, but because I did build it in KVM VM, it did stop because non-existing sound in KVM VM. I will test it on my local Win10 desktop computer later today.
I will also try later does building 32bit Windows exe work, because some do use 32bit Windows.
I did test TSC on my Win10 desktop computer.
Works:
Minor problems were:
Very nice. Thank you.
When downloading TSC installer exe, MS Chromium Edge blocked download saying it's dangerous, so I did click allow to keep file.
I have no idea.
When double clicking TSC installer exe, Windows did ask yellow box confirmation that should this exe be allowed to run, so I did allow it.
There's nothing we can do against that. You need to pay for a specifically crafted TLS certificate to resolve this, and TSC does not have any money one could use for that. The official variant costs about 400$ per year (see the link), but there's a cheaper, inofficial variant for OSS projects (see link again). Anyway, we can't use anything that isn't free.
Once happened that Windows Defender complained that some device had stopped working, so I clicked at Windows Defender to ignore that, so then I could start TSC again.
I have no idea either.
@xet7 If no further problems appear, you probably can close this issue. I'll document the problems you outlined later on somewhere.
Hi, I tried building TSC with MSYS2 on Windows 10.
@Quintus Do you have any ideas about these errors?