Re: [swift-dev] Is swift.org/contributing/ stale?

[David Hart via swift-dev]

> 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 in the repository, nothing 
> more. But my memory might be wrong.

Yes, GitHub automatically attaches this tag to anybody who has at least one 
commit: it isn’t a tag assigned by the Swift Open Source project.

>> 
>> 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 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 “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 need to do before pushing a commit?
 
 Thanks!
 Dave
 ___
 swift-dev mailing list
 swift-dev@swift.org
 https://lists.swift.org/mailman/listinfo/swift-dev
>>> 
>> 
>> ___
>> swift-dev mailing list
>> swift-dev@swift.org
>> https://lists.swift.org/mailman/listinfo/swift-dev
> 
> ___
> swift-dev mailing list
> swift-dev@swift.org
> https://lists.swift.org/mailman/listinfo/swift-dev

___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

Re: [swift-dev] Portable stdlib

[Andy Best via swift-dev]

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 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 libc or POSIX?
>
>
> 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. This obviously leaves the problem that there won't be a
> standard lib to link against on the target.
>
>
> There’s a PR open to add cross-compilation support to the build system:
> https://github.com/apple/swift/pull/1398 It would be great if you or
> someone else would dust it off and get it merged in.
>
>
> I figured that the best way to accomplish this would probably be to
> implement whatever stubs are necessary for the target (e.g. all the libc
> calls).
>
> I am struggling to find the best way to build the standard library though.
> I've got a copy of the stdlib files, have run gyb over all of the
> templates, and am attempting to get swiftc to compile everything and output
> a giant IR file.
>
> I was wondering if there was an easier way to go about building a custom
> libswiftcore?
>
> It would obviously be great to be able to use Swift in this way without an
> OS, as it would open up a lot of opportunities for use of the language
> (embedded development, etc).
>
>
> Slava
>
>
>
> Thanks,
>
> Andy
> ___
> swift-dev mailing list
> swift-dev@swift.org
> https://lists.swift.org/mailman/listinfo/swift-dev
>
>
>
___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

Re: [swift-dev] Portable stdlib

[Slava Pestov via swift-dev]

> 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 libc or POSIX?

> 
> 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. This obviously leaves the problem that there won't be a standard lib 
> to link against on the target.

There’s a PR open to add cross-compilation support to the build system: 
https://github.com/apple/swift/pull/1398 
 It would be great if you or someone 
else would dust it off and get it merged in.

> 
> I figured that the best way to accomplish this would probably be to implement 
> whatever stubs are necessary for the target (e.g. all the libc calls).
> 
> I am struggling to find the best way to build the standard library though. 
> I've got a copy of the stdlib files, have run gyb over all of the templates, 
> and am attempting to get swiftc to compile everything and output a giant IR 
> file.
> 
> I was wondering if there was an easier way to go about building a custom 
> libswiftcore?
> 
> It would obviously be great to be able to use Swift in this way without an 
> OS, as it would open up a lot of opportunities for use of the language 
> (embedded development, etc).

Slava

> 
> 
> Thanks,
> 
> Andy
> ___
> swift-dev mailing list
> swift-dev@swift.org
> https://lists.swift.org/mailman/listinfo/swift-dev

___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

Re: [swift-dev] Is swift.org/contributing/ stale?

[Michael Gottesman via swift-dev]

> 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 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 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 “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 
>>> need to do before pushing a commit?
>>> 
>>> Thanks!
>>> Dave
>>> ___
>>> swift-dev mailing list
>>> swift-dev@swift.org
>>> https://lists.swift.org/mailman/listinfo/swift-dev
>> 
> 
> ___
> swift-dev mailing list
> swift-dev@swift.org
> https://lists.swift.org/mailman/listinfo/swift-dev

___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

Re: [swift-dev] Is swift.org/contributing/ stale?

[David Zarzycki via swift-dev]

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 
> 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 “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 
>> need to do before pushing a commit?
>> 
>> Thanks!
>> Dave
>> ___
>> swift-dev mailing list
>> swift-dev@swift.org
>> https://lists.swift.org/mailman/listinfo/swift-dev
> 

___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

Re: [swift-dev] Is swift.org/contributing/ stale?

[Slava Pestov via swift-dev]

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 “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 
> need to do before pushing a commit?
> 
> Thanks!
> Dave
> ___
> swift-dev mailing list
> swift-dev@swift.org
> https://lists.swift.org/mailman/listinfo/swift-dev

___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

[swift-dev] Is swift.org/contributing/ stale?

[David Zarzycki via swift-dev]

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 need to do 
before pushing a commit?

Thanks!
Dave
___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

[swift-dev] Portable stdlib

[Andy Best via swift-dev]

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. This obviously leaves the problem that there won't be a
standard lib to link against on the target.

I figured that the best way to accomplish this would probably be to
implement whatever stubs are necessary for the target (e.g. all the libc
calls).

I am struggling to find the best way to build the standard library though.
I've got a copy of the stdlib files, have run gyb over all of the
templates, and am attempting to get swiftc to compile everything and output
a giant IR file.

I was wondering if there was an easier way to go about building a custom
libswiftcore?

It would obviously be great to be able to use Swift in this way without an
OS, as it would open up a lot of opportunities for use of the language
(embedded development, etc).


Thanks,

Andy
___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev