[M3devel] Compile Options

[Olaf Wagner]

Quoting Jay K <jay.krell at cornell.edu>:

> -O is the config files
> It gets passed on to them and they may or may not pay attention.
>
> Turning off symbol generation not something I'm very sympathetic too.
> I realize it cuts I/O, build time, resulting binary size (possibly   
> load/runtime,
> depending on the load behavior of symbols). Though on Windows
> the symbols go into separate files, greatly reducing any negative affect.
> On one hand, you don't want to inhibit debugging,

Of course you may want to strip symbols for programs delivered to
customers.

> but on the other, we don't have a good debugger story anyway.

m3gdb works well on certain platforms.

> Again, check the config files.
>
> -c I don't know. Is it important?

The front end just includes some quake calls in the generated
m3make file for the options:

% less AMD64_FREEBSD/m3make.args
set_config_options ()
readonly _all = TRUE % cm3 -build
m3_optimize (TRUE)                  <----
m3_debug (TRUE)                     <----
M3_KEEP_FILES = TRUE
m3_compile_only ()                  <----
M3_MODE = "build"
include_dir ("../src")

At least optimize and debug used to work some time ago; I'm not
sure about compile-only.

Was something lost during the great config refactoring?
Can you please check that, Jay?

I think we shold implement the CLI as documented. We _might_ discuss
the value-add of -c (I've never used it).

We're probably missing regression tests for these simple command line
arguments, too.

Olaf
-- 
Olaf Wagner -- elego Software Solutions GmbH
                Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
phone: +49 30 23 45 86 96  mobile: +49 177 2345 869  fax: +49 30 23 45 86 95
    http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194