Quietening Guile compilation output

Quietening Guile compilation output

[Peter TB Brett]

[-- Attachment #1: Type: text/plain, Size: 664 bytes --]

Hi folks,

As my Scheme codebase gets larger, when starting my application I get
screens full of debug spew about the Guile compilation process.  How can
I silence the following messages:

;;; note: source file /path/to/foo.scm
;;;       newer than compiled /path/to/foo.scm.go
;;; compiling /path/to/foo.scm
;;; compiled /path/to/foo.scm.go

...while still getting the actually useful compilation warnings?

Thanks,

                                        Peter

P.S. Bonus points if you can help me find an approach that can be used
without causing errors when the code is run under Guile 1.8...!

-- 
Dr Peter Brett <peter@peter-b.co.uk>

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: Quietening Guile compilation output

[Thien-Thi Nguyen]

[-- Attachment #1: Type: text/plain, Size: 855 bytes --]

() Peter TB Brett <peter@peter-b.co.uk>
() Fri, 27 Sep 2013 21:56:39 +0100

   As my Scheme codebase gets larger, when starting my application I get
   screens full of debug spew about the Guile compilation process.  How
   can I silence the following messages: [...]  ...while still getting
   the actually useful compilation warnings?

I don't know the answer to that question, but a related question comes
to mind: Have you considered moving the compilation from application
invocation time to "build" time?  I think such messages would not be so
annoying, then, and the (legitimate) warnings more welcome, too.

-- 
Thien-Thi Nguyen
   GPG key: 4C807502
   (if you're human and you know it)
      read my lisp: (responsep (questions 'technical)
                               (not (via 'mailing-list)))
                     => nil

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: Quietening Guile compilation output

[Peter TB Brett]

[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]

Thien-Thi Nguyen <ttn@gnu.org> writes:

> () Peter TB Brett <peter@peter-b.co.uk>
> () Fri, 27 Sep 2013 21:56:39 +0100
>
>    As my Scheme codebase gets larger, when starting my application I get
>    screens full of debug spew about the Guile compilation process.  How
>    can I silence the following messages: [...]  ...while still getting
>    the actually useful compilation warnings?
>
> I don't know the answer to that question, but a related question comes
> to mind: Have you considered moving the compilation from application
> invocation time to "build" time?  I think such messages would not be so
> annoying, then, and the (legitimate) warnings more welcome, too.

Hi Thien,

Yes, I have considered it!  However, the main reason I want to silence
the "noise" messages is so that I can more easily pick out the warnings,
not just for aesthetic reasons.  Shifting the compilation to build time
doesn't actually solve that problem, surely?

                              Peter

-- 
Dr Peter Brett <peter@peter-b.co.uk>

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: Quietening Guile compilation output

[Ludovic Courtès]

Peter TB Brett <peter@peter-b.co.uk> skribis:

> As my Scheme codebase gets larger, when starting my application I get
> screens full of debug spew about the Guile compilation process.  How can
> I silence the following messages:
>
> ;;; note: source file /path/to/foo.scm
> ;;;       newer than compiled /path/to/foo.scm.go
> ;;; compiling /path/to/foo.scm
> ;;; compiled /path/to/foo.scm.go
>
> ...while still getting the actually useful compilation warnings?

I would recommend changing your package’s build system so that it
compiles and installs .go file.  That way, users won’t see any such
messages.

The only exception is commands with a #!../guile shebang.  For those you
can really avoid auto-compilation warnings, but it’s often OK to use the
evaluator if the script itself is small and just an entry point for the
core of your package:

  #!/path/to/guile --no-auto-compile

HTH,
Ludo’.

Re: Quietening Guile compilation output

[Peter TB Brett]

[-- Attachment #1: Type: text/plain, Size: 742 bytes --]

ludo@gnu.org (Ludovic Courtès) writes:

> I would recommend changing your package’s build system so that it
> compiles and installs .go file.  That way, users won’t see any such
> messages.
>
> The only exception is commands with a #!../guile shebang.  For those you
> can really avoid auto-compilation warnings, but it’s often OK to use the
> evaluator if the script itself is small and just an entry point for the
> core of your package:
>
>   #!/path/to/guile --no-auto-compile
>

To save me reinventing the wheel, does anybody have a recipe for doing
build-time compilation that DTRT with both Guile 1.8 and Guile 2.0?

Thanks,

                               Peter

-- 
Dr Peter Brett <peter@peter-b.co.uk>

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: Quietening Guile compilation output

[Ludovic Courtès]

Peter TB Brett <peter@peter-b.co.uk> skribis:

> ludo@gnu.org (Ludovic Courtès) writes:
>
>> I would recommend changing your package’s build system so that it
>> compiles and installs .go file.  That way, users won’t see any such
>> messages.
>>
>> The only exception is commands with a #!../guile shebang.  For those you
>> can really avoid auto-compilation warnings, but it’s often OK to use the
>> evaluator if the script itself is small and just an entry point for the
>> core of your package:
>>
>>   #!/path/to/guile --no-auto-compile
>>
>
> To save me reinventing the wheel, does anybody have a recipe for doing
> build-time compilation that DTRT with both Guile 1.8 and Guile 2.0?

Yes, see <http://git.savannah.gnu.org/cgit/guile.git/tree/am/guilec>.

Ludo’.