From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Toolchain Version
Date: Wed, 24 May 2017 14:40:50 +0100 [thread overview]
Message-ID: <59258D62.9010903@codethink.co.uk> (raw)
In-Reply-To: <HK2PR0601MB1329C7E4934B2DCDD0D5947AB7FE0@HK2PR0601MB1329.apcprd06.prod.outlook.com>
Hi,
On 24/05/17 13:34, Chris Paterson wrote:
> Hello,
>
>> From: cip-dev-bounces at lists.cip-project.org [mailto:cip-dev-
>> bounces at lists.cip-project.org] On Behalf Of Agustin Benito Bethencourt
>> Sent: 24 May 2017 11:25
>> Hi,
>>
>> On 24/05/17 09:16, Chris Paterson wrote:
>>> Hello all,
>>>
>>> Has the project decided upon the compiler/toolchain (and version) that
>>> will be used?
>>
>> No.
>
> Should it?
Yes we should.
> I would have thought that as part of CIPs reproducible build/test environment we should be aiming to standardise all tools?
We should.
>
> What toolchain is everyone using at the moment?
Good question to start.
>
> Kind regards, Chris
>
>>
>>>
>>> Thanks, Chris
>>>
>>>
>>>
>>> _______________________________________________
>>> cip-dev mailing list
>>> cip-dev at lists.cip-project.org
>>> https://lists.cip-project.org/mailman/listinfo/cip-dev
>>>
>>
>> --
>> Agustin Benito Bethencourt
>> Principal Consultant - FOSS at Codethink agustin.benito at codethink.co.uk
>> _______________________________________________
>> cip-dev mailing list
>> cip-dev at lists.cip-project.org
>> https://lists.cip-project.org/mailman/listinfo/cip-dev
>
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk
next prev parent reply other threads:[~2017-05-24 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 8:16 [cip-dev] Toolchain Version Chris Paterson
2017-05-24 10:24 ` Agustin Benito Bethencourt
2017-05-24 12:34 ` Chris Paterson
2017-05-24 13:40 ` Agustin Benito Bethencourt [this message]
2017-05-24 14:02 ` Noriaki Fukuyasu
2017-05-24 14:04 ` Chris Paterson
2017-05-24 15:06 ` Noriaki Fukuyasu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=59258D62.9010903@codethink.co.uk \
--to=agustin.benito@codethink.co.uk \
--cc=cip-dev@lists.cip-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.