Skip to content
This repository has been archived by the owner on Jun 24, 2022. It is now read-only.

unable to compile WebAssemblyStudio project locally on win10 - Illegal characters in file name #463

Closed
onelsonic opened this issue Jul 22, 2020 · 9 comments

Comments

@onelsonic
Copy link

I cannot compile a project locally on win10 it says : Illegal characters in file name
2020-07-18 02_03_10-WebAssembly Studio

@onelsonic onelsonic changed the title unable to run WebAssemblyStudio locally on win10 - Illegal characters in file name unable to compile WebAssemblyStudio project locally on win10 - Illegal characters in file name Jul 22, 2020
@MaxGraey
Copy link
Collaborator

MaxGraey commented Jul 22, 2020

I guess this field for filename (<name>.<ext>), not for full path

@onelsonic
Copy link
Author

either full path or just the file name without the path will not work on windows 10.

@MaxGraey
Copy link
Collaborator

it should works) WebAssembly Studio uses virtual file system which not relate on OS at all.

@onelsonic
Copy link
Author

onelsonic commented Jul 28, 2020

@MaxGraey can you replicate on win10?
From a clean install, a project is not working on win 10 - project will not compile. (when it does on macOS)

Seems like this one is the same issue :
#446

Any win10 users here?

@nokotan
Copy link

nokotan commented Sep 22, 2020

In my win10, there seems to be no problem with file path.

WasmStudioOnWin10

It is strange that main.c is shown as "src\main.c" in the project view, and is not in "/src" folder. The problem is probably caused inconsistent path separater, between project view ("") and WebAssembly Editor (expects "/").

You can manually create "/src" folder and move "main.c", "main.html", and "main.js" into that folder, then it will be compiled.

@onelsonic
Copy link
Author

onelsonic commented Sep 22, 2020

not ideal but your workaround works :
creating the directory /src and moving and renaming the files seems to works.
You found what is causing this issue. @nokotan

Your screenshot had me confused as it is the web version, but this workaround works locally.

@nokotan
Copy link

nokotan commented Sep 23, 2020

Your mention helped me understand this problem better, thanks.

I think this is build-time failure when processing templates projects.
This workaround does fix this problem?

@onelsonic
Copy link
Author

Hi @nokotan yes your code is fixing the windows build when running locally.
👍

@onelsonic
Copy link
Author

thanks @nokotan 👍
I'm closing this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants