Issue compiling a new project on Windows

[jgranduel]

I have tried the new Windows version (perry-windows-x86_64.zip version 0.4.14), unzipped, put on PATH.
Perry folder comes like so:

perry_runtime.lib
perry_stdlib.lib
perry.exe

but, can't compile yet :

> perry compile .\src\main.ts -o myapp.exe
Collecting modules...
Found 1 module(s): 1 native, 0 JavaScript
Generating code...

Module init order (0 modules):

Wrote object file: main_ts.o
Linking (runtime-only)...
main_ts.o : error LNK2001: symbole externe non résolu perry_ui_app_create
main_ts.o : error LNK2001: symbole externe non résolu perry_ui_app_set_body
main_ts.o : error LNK2001: symbole externe non résolu perry_ui_app_run
...
main_ts.o : error LNK2001: symbole externe non résolu perry_get_orientation
main_ts.o : error LNK2001: symbole externe non résolu perry_get_device_idiom
myapp.exe : fatal error LNK1120: 216 externes non résolus
Error: Linking failed

A sructure error or real dependencies missing (or me missing documentation ?). Haven't tried winget yet, too cumbersome for a single test.

[proggeramlug]

Hey @jgranduel, this is fixed in v0.4.15 — you can grab the updated zip from the release page.

What was happening: The compiler was unconditionally declaring ~200 UI function symbols (perry_ui_*, perry_system_*, etc.) in every compiled object file, even for programs that don't use perry/ui. On Windows, the linker couldn't resolve them since the UI library wasn't linked.

The fix: UI function declarations are now guarded behind a needs_ui flag — they're only emitted when your code actually imports perry/ui. Non-UI programs produce zero UI symbols in the object file.

We also now ship the platform UI library (perry_ui_windows.lib) in the Windows zip, so when you do want to build a UI app, it should just work too.

Let us know if you run into anything else!

[jgranduel]

You are just too fast for me 😅! I will give a try as soon as possible!

[proggeramlug]

I highly appreciate all your feedback! :)

[jgranduel]

But sorry, negative feedback for version 0.4.15, kind of a come back of a previous WSL issue?

>perry init my-project
Creating new perry project 'my-project'...

  Created perry.toml
  Created src/main.ts
  Created .gitignore

Done! Next steps:
  cd my-project
  perry compile src/main.ts
  ./main

>cd my-project
>perry compile .\src\main.ts -o myapp.exe --verbose
Collecting modules...
Found 1 module(s): 1 native, 0 JavaScript
Generating code...

Module init order (0 modules):

Wrote object file: main_ts.o
Linking (runtime-only)...
main_ts.o : error LNK2001: symbole externe non résolu js_runtime_init
main_ts.o : error LNK2001: symbole externe non résolu js_load_module
main_ts.o : error LNK2001: symbole externe non résolu js_get_export
main_ts.o : error LNK2001: symbole externe non résolu js_call_function
main_ts.o : error LNK2001: symbole externe non résolu js_await_js_promise
main_ts.o : error LNK2001: symbole externe non résolu js_set_property
main_ts.o : error LNK2001: symbole externe non résolu js_new_instance
main_ts.o : error LNK2001: symbole externe non résolu js_new_from_handle
main_ts.o : error LNK2001: symbole externe non résolu js_create_callback
myapp.exe : fatal error LNK1120: 9 externes non résolus
Error: Linking failed

BTW, isn't command

perry init --name test

supposed to create a test directory? it doesn't create anything.

[jgranduel]

Trying out perry-0.4.19 on Windows:

> node .\src\main.ts
Hello from Perry!
> perry --version
perry 0.4.19
> perry compile .\src\main.ts
Collecting modules...
Found 1 module(s): 1 native, 0 JavaScript
Generating code...

Module init order (0 modules):

Wrote object file: main_ts.o
Linking (runtime-only)...
Wrote executable: main.exe
Binary size: 1.9MB

> ./main.exe
<nothing printed>

[proggeramlug]

@jgranduel I'll get back to this ticket asap. Underlying "issue" is that we have so many updates right now that I am hoping this will get resolved as a by-product, stay tuned. :D