Frama-C-discuss mailing list archives

This page gathers the archives of the old Frama-C-discuss archives, that was hosted by Inria's gforge before its demise at the end of 2020. To search for mails newer than September 2020, please visit the page of the new mailing list on Renater.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Frama-c-discuss] Frama-C 15 Phosphorus is out

On Fri, Aug 11, 2017 at 10:19 PM, Mehdi Dogguy <mehdi at dogguy.org> wrote:

> Do you still support architecture w/o native dynlink? I didn't see this
> statement in the changelog whereas I get this build failure on (e.g. mips)
> when I try to compile Frama-C:
>
> [...]

> So it tests two things at once:
> - presence of a native compiler
> - native dynlink
>
> So bytecode architectures look like they are not supported anymore as well,
> which is a pity.
>
>
This was not intended. We only wanted to get rid of the platforms where
native dynlink does not work. When native compilation is not available, we
probably should not test for native dynlink at all. And better yet, when
native compilation is available, but not native dynlink, only compile the
bytecode version.


> > - Bash and Zsh completion for Frama-C options
>
> Can you please clarify where are the completion scripts? I didn't find them
> in the tarball, but maybe I was looking at the wrong place.
>
>
We apparently forgot to package the scripts... The frama-c -autocomplete
option is used to generate the autocompletion tables, but we have also
written scripts to parse this output and to feed it to bash and zsh. There
are two scripts available for zsh in the our dev tree, I will let someone
more familiar with them comment and/or post them here.

-- 
Boris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20170813/91898154/attachment.html>