+ open.mp forum (https://forum.open.mp)
-- Forum: open.mp (https://forum.open.mp/forumdisplay.php?fid=40)
--- Forum: Questions and Suggestions (https://forum.open.mp/forumdisplay.php?fid=42)
--- Thread: [Question] The size of the output amx file (/showthread.php?tid=3692)
The size of the output amx file - scandalfive - 2025-12-01
Hello everyone. I've encountered a situation where, when compiling an empty mod (containing only #include <open.mp> and main(){}) using qawno and a custom bat file, the output amx files have different sizes.
bat.amx - 1389 bytes
qawno.amx - 1420 bytes
Is this difference normal, or have I made a mistake in configuring the compiler command for the bat file?
bat:
Code:
compiler\pawncc.exe -;+ -(+ -\ -Z- "-isource/%name%" "-rsource/%name%" "-icompiler/include" -d3 -t4 "-orelease/gamemodes/%name%" "source/%name%.pwn"qawno:
Code:
./pawncc -;+ -(+ -\ -Z- "-i%p/%o" "-r%p/%o" "-i%q/include" -d3 -t4 "-o%p/%o" "%p/%i"May the experts forgive me, because this question may be very easy, but I'm new to this and I want to understand everything.
Thank you.
RE: The size of the output amx file - wartacho - 2026-01-11
Yes, this size difference is normal and doesn't indicate any error in your configuration. The 31-byte difference (1420 - 1389) occurs due to metadata in the AMX file header, specifically related to file paths and debug information.
Why the Difference Occurs:
- Source paths: Qawno stores paths differently than your bat file
- Debug info: -d3 flag includes symbols and line numbers
- Timestamps/metadata in header
What Really Matters:
Both files work identically because:
- Same compilation flags
- Same P-code/bytecode generated
- Only header metadata differs
How to Verify:
1. Test both AMX on server - should load fine
2. Runtime behavior identical
3. No version/corruption warnings
The ~2% difference is insignificant. Your bat config is correct!
Welcome to Pawn development!