Unneeded data in executable?

[Piero]

Why does this also work in executable?!?!?!?

Code: Select all

MessageRequester("compiler file",#PB_Compiler_File)

PS: Found trying to answer this rndrei thread

[infratec]

Why not

To build the executable, the file is compiled and during this, the constant is replaced by the filename.

You can use this and #PB_Compiler_Line for writing better log files.
So ... this constants are needed in an executable if they are used.

What do you expect? An empty string? Not showing the MessageRequester?

[Piero]

Why not
To build the executable, the file is compiled and during this, the constant is replaced by the filename.
You can use this and #PB_Compiler_Line for writing better log files.

Wait; I must being misunderstanding something: why does the executable need to contain that info?
Also, I cannot find it searching the binary!

Edit: "I must being misunderstanding something"

[BarryG]

why does the executable need to contain that info?

Because you told it to. The constant is replaced by its name, as expected.

The real question is why a single MessageRequester compiles an executable of 487 KB. So much added extra info. Surely PureBasic can go back to the good old days where a MessageRequester executable was only 6 KB (using PureBasic 5.73). That's the version I use for my own little tools now.

[Piero]

why does the executable need to contain that info?

Because you told it to. The constant is replaced by its name, as expected.

The real question is why a single MessageRequester compiles an executable of 487 KB. So much added extra info. Surely PureBasic can go back to the good old days where a MessageRequester executable was only 6 KB (using PureBasic 5.73). That's the version I use for my own little tools now.

Thank you!
My Fault

PS: I was alarmed because I couldn't find it into the binary (probably because of unicode)

[infratec]

The real question is why a single MessageRequester compiles an executable of 487 KB. So much added extra info. Surely PureBasic can go back to the good old days where a MessageRequester executable was only 6 KB (using PureBasic 5.73). That's the version I use for my own little tools now.

Hm...

with PB 6.21b5 x86 asm backend on Win 10 x64 it generates an exe with 119.808 bytes
And if I check the compiler option 'Use shared UCRT' the exe is 17.920 bytes.

[BarryG]

I'm on 6.10 still.

[Quin]

I'm on 6.10 still.

When 6.20 stable drops I highly recommend checking it out, as long as you're okay with your apps being stuck to Windows 10 and above when you check this box, the UCRT will give you binaries like the days of PB before the new toolchain. And, if you want to support older OSs, just uncheck it and rebuild! PureBasic is beautiful.

[Piero]

When 6.20 stable drops

6.21

[Mindphazer]

The real question is why a single MessageRequester compiles an executable of 487 KB. So much added extra info. Surely PureBasic can go back to the good old days where a MessageRequester executable was only 6 KB (using PureBasic 5.73). That's the version I use for my own little tools now.

It also depends on the platform : on my Mac, the compiled app's size is 119 Kb

[Quin]

When 6.20 stable drops

6.21

One of these days I'll learn to not post before having my coffee

[NicTheQuick]

With PureBasic 6.20 (x64) the size is

• 31288 bytes with the C backend
• 39432 with the ASM backend

Created on Ubuntu 24.04 LTS.

[DeanH]

I found the UCRT option on 6.21 Beta 6 in the Compiler Options. It reduced the little MessageRequester program from 150k to 24.6k. That's still a fair bit more than the 6k the PB5.3 and 5.7 and even 6.04 generated. I tried it on my own programs. One module went from 8053k to 7729k, another from 9016k to 8692k. It felt as if the exe's seemed to fire up more quickly, too.

I am old school. Efficient programs only contain the code they need.

[Piero]

I was alarmed because I couldn't find it into the binary

To show unicode strings on binaries you can use stringsext (multi platform)

Example search for the unicode string "Pure" (using grep) into a Mac binary:

Code: Select all

stringsext -e UTF-16le -- /pb.app/Contents/MacOS/pb | grep Pure

[Quin]

I was alarmed because I couldn't find it into the binary

To show unicode strings on binaries you can use stringsext (multi platform)

Example search for the unicode string "Pure" (using grep) into a Mac binary:

Code: Select all

stringsext -e UTF-16le -- /pb.app/Contents/MacOS/pb | grep Pure

Is there not strings for Mac?
https://github.com/robpike/strings