> On 14 Aug 2017, at 19:50, Michael Gottesman via swift-dev
> wrote:
>
>
>> On Aug 14, 2017, at 10:32 AM, David Zarzycki via swift-dev
>> wrote:
>>
>> Hi Slava,
>>
>> Ah. So “GitHub collaborator” status doesn’t imply commit access then?
>
> I think that only means that you have a commit i
Yes, exactly. Obviously you'd have to provide the necessary functionality
for your own platform (e.g. malloc, free, putc, etc.)
On Mon, 14 Aug 2017 at 6:54 pm, Slava Pestov wrote:
> On Aug 14, 2017, at 9:44 AM, Andy Best via swift-dev
> wrote:
>
> Hey,
>
> I'm currently looking at building a po
> On Aug 14, 2017, at 9:44 AM, Andy Best via swift-dev
> wrote:
>
> Hey,
>
> I'm currently looking at building a portable version of the standard library
> (for targeting microcontrollers, kernel dev, etc).
I’m a bit confused about your terminology. By “portable” do you mean no
dependencies
> On Aug 14, 2017, at 10:32 AM, David Zarzycki via swift-dev
> wrote:
>
> Hi Slava,
>
> Ah. So “GitHub collaborator” status doesn’t imply commit access then?
I think that only means that you have a commit in the repository, nothing more.
But my memory might be wrong.
>
> Dave
>
>> On Aug
Hi Slava,
Ah. So “GitHub collaborator” status doesn’t imply commit access then?
Dave
> On Aug 14, 2017, at 13:22, Slava Pestov wrote:
>
> I think it’s still up to date. You need commit access to trigger CI, and to
> merge PRs. Otherwise you’ll have to ask someone with commit access to do that
I think it’s still up to date. You need commit access to trigger CI, and to
merge PRs. Otherwise you’ll have to ask someone with commit access to do that
for you.
Slava
> On Aug 14, 2017, at 1:14 PM, David Zarzycki via swift-dev
> wrote:
>
> On the swift.org/contributing/ web page, under “Co
On the swift.org/contributing/ web page, under “Commit Access”, the section
talks about commit access in a way that suggests that it was written before
mandatory continuous integration testing was added. Is this true? Can somebody
update the page? If CI is not required, then is there something I
Hey,
I'm currently looking at building a portable version of the standard
library (for targeting microcontrollers, kernel dev, etc).
The easiest way to cross compile Swift at the moment (that I can find) is
to get swiftc to generate LLVM IR (-emit-ir), and use clang to build and
cross compile. Th
