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 on Windows 10 via WSL
- Subject: [Frama-c-discuss] Frama-C on Windows 10 via WSL
- From: Patrick.Baudin at cea.fr (BAUDIN Patrick)
- Date: Fri, 19 Jul 2019 14:21:06 +0200
- In-reply-to: <8c6794c5-fbbb-0597-1ddc-eec34e682c70@proteancode.com>
- References: <2e187c1a-d6d6-3738-df66-1ed684eaea4d@proteancode.com> <8c6794c5-fbbb-0597-1ddc-eec34e682c70@proteancode.com>
Hello, Next to the article "Habemus Frama-C in Fenestris (Frama-C on Windows, with WSL)" authored by André at Frama-C's blog, Allan has done some more investigations and suggests to use VcXsrv as X server instead of Cygwing/X. An update of the installation process for "Frama-C 19 (Potassium)" on "Windows 10" has been issued at https://github.com/Frama-C/Frama-C-snapshot/blob/5eb3bf11f6d7ca4c2bb074cca7a1a428874a96d9/INSTALL.md Do not hesitate to give us your feedback or suggestions, either via comments to the pull request   https://github.com/Frama-C/Frama-C-snapshot/pull/25 or a message to frama-c-discuss. Thank's to them, -- Patrick.
- References:
- [Frama-c-discuss] Warnings for call to memcpy()... why?
- From: rod at proteancode.com (Roderick Chapman)
- [Frama-c-discuss] Warnings for call to memcpy()... why?
- Prev by Date: [Frama-c-discuss] Warnings for call to memcpy()... why?
- Next by Date: [Frama-c-discuss] Warnings for call to memcpy()... why?
- Previous by thread: [Frama-c-discuss] Warnings for call to memcpy()... why?
- Next by thread: [Frama-c-discuss] problem with frama-c to Coq inductive type definition
- Index(es):