[Spirit_12]

I've been using gcc to compile majority of my extensions for my variety of projects. Recently, some of the requests made me look into Windows binaries. I decided to give ambuild a shot to reduce the load of maintaining two compile procedures.

Projects work, but the python compiled projects (ambuild) have a larger size compared to gcc binaries. For referance, I compiled defib-fix extension for l4d2 on my Linux system and here are the sizes under both methods.

• Python - 758 kb
• gcc - 107 kb

My question would be that are there any drawbacks of using python compiler, as opposed to gcc?

[klippy]

Ambuild does an existing compiler, probably gcc (depending on how it's configured). The difference here depends on compiler options.

[asherkin]

Did you configure with --enable-optimize? By default the binaries also include debug symbols, there is another configure flag to strip it out to a separate file.

[Spirit_12]

Yes, I did configure it with --enable-optimize flag. I think my configure.py file has debug option, which was not enabled, but I'll give it a check.

[DJ Tsunami]

I have noticed the same thing with AMBuild and Clang 3.8. --enable-optimize adds the -O3 flag for GCC, but I believe Clang requires -g0. Also AMBuild always sets -g3 for Clang, which is not a valid option.

Edit: commenting out that line, rebuilding AMBuild and adding -g0 to my AMBuildScript indeed produces an extension without debugging symbols.

[Fyren]

Testing locally, my clang 3.9 understands -g0 through -g3. Passing -g4 errors. A quick Google doesn't find any documentation about it, but the obvious guess is it's at least attempting to mimic gcc's parameters.

[DJ Tsunami]

Interesting, indeed clang -O3 correctly strips debug symbols, but clang -O3 -g3 does not. In GCC -g can be used with -O, but apparently in Clang -g overrides -O?

[Spirit_12]

I'm using gcc, and not clang.

[Fyren]

If you can provide your complete project on GitHub or an archive (the source and your build scripts), someone can try to take a look.

[asherkin]

Just to be clear, it is intentional that AMBuild-built binaries contain debug symbols – there is no bug or unexpected behaviour here.