WIndows binaries does nothing

[mcff2]

Hello,

I compiled the windows binaries without any pb by corss-compiling on debian.

However, the resulting binaries (the client one) does... nothing : it silently exits without saying anything, whatever option I give it.

Did you already see that? Any idea?

[serpilliere]

Hi @mcff2 Can you run it from a cmd command prompt? can you add '-vv' option to the command line?

[mcff2]

It does... nothing at all :-(

There is certainly a major issue with the compilation, but I dont have a clue to investigate...

[serpilliere]

Hi @mcff2 In the file https://github.com/cea-sec/sanzu/blob/main/sanzu/src/bin/sanzu_client.rs you may remove the first line:

#![windows_subsystem = "windows"]

This will allow you to compile the client as a console application, which will force rust to output to stdout.

Can you try this? Can you confirm that you are running the very last version of sanzu?

[mcff2]

Willdo :-)Thanks for your help!Envoyé de mon iPadLe 8 juin 2023 à 19:14, serpilliere @.***> a écrit : Hi @mcff2 In the file https://github.com/cea-sec/sanzu/blob/main/sanzu/src/bin/sanzu_client.rs you may remove the first line:

![windows_subsystem = "windows"]

This will allow you to compile the client as a console application, which will force rust to output to stdout. Can you try this? Can you confirm that you are running the very last version of sanzu?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[mcff2]

Without this line (ie console application), it's way better & easier.

It works now, thanks !

[serpilliere]

Can you provide your windows os version ? Even if we compile in GUI app (with the first line), the log should appear in the console, if sanzu is run in command line. (We tested this on windows 10)

[mcff2]

Windows 10 22H2, build 19045.3086