I have a simple application (Windows) that runs from a tray icon; it only has an HtmlViewer and a few controls. When compiled, it results in almost 125MB of files between the executable and the two folders (Libs and Resources), of which 123MB are in the Libs folder.
That seems like too much for such a simple app.
As you’re using an HTMLViewer and compiling for Windows, the Chromium Embedded Framework (CEF) must be included for your application to function. It’s quite large.
1 Like
That is why I disliked pcode…
YES, I know, these are called Libraries, and this is Xojo not Pascal.
What happened about
1 Like
The last time I looked, DesktopXAML for WebView2 had incompatibilities that made it so you could not build a usable window. If you’d like to check yourself, my work before giving up is on GitHub. All of the work I was doing was something Xojo should have been doing to live up to its cross-platform claim.
And to answer OPs question:
All of them.
Xojo doesn’t use pcode.
Read carefully before answering: I wrote that in the next sentence.
That said, what are the stuff in the Libs folder ? Code you need to run your application: remove the files and yur application stop working (at beast, else it crash).
The difference lies in a p-machine to read it.
Xojo do not use that.
I did read carefully. And still you talk about p-machines…
I switched from WebKit to Native and the Libs folder went down to 30MB. It’s not ideal, but it’s much better. I use it to load standard HTML format (tickets for a POS system) and I don’t need any special processing.
I understand that Xojo doesn’t want external dependencies, but if I’m compiling for Windows, I could have the option of using the .NET libraries (which are open source and free even for commercial use). That would dramatically decrease the size of Windows applications.
…then I compressed the libraries with UPX, and the whole project ended up being less than 10Mb.
No issues with code signing and av false positives?
No, everything is working perfectly.