Skip to content

README - Added Toolchain section #136

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 6 commits into from
Closed

README - Added Toolchain section #136

wants to merge 6 commits into from

Conversation

amraboelela
Copy link
Contributor

No description provided.

@@ -24,3 +24,29 @@ Our first tasks for this project are:
0. Incrementally add functionality back in.

Some C headers and sources (e.g. `Availability.h`, `Block.h`, and the libclosure `runtime.c`) are similar to ones embedded into the CoreFoundation part of [swift-corelibs-foundation](http://github.com/apple/swift-corelibs-foundation). We should figure out a mechanism to share these instead of duplicating them across projects.

## Toolchain
To add libdispatch to the toolchain in Linux, you need to add libdispatch and install-libdispatch lines to ./swift/utils/build-presets.ini under `[preset: buildbot_linux]` section. Also to make the build run faster, you can comment the test lines. After those updates the section would be as following:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

to the Swift toolchain in Linux (libdispatch can be built outside of swift too, so please be more precise).

@MadCoder
Copy link
Contributor

MadCoder commented Aug 5, 2016

@amraboelela
Copy link
Contributor Author

I actually got this info from @seabaylea page in github:
https://gist.github.com/seabaylea/cad7808615c52cfd2fc9d1debcad832f

@MadCoder
Copy link
Contributor

MadCoder commented Aug 5, 2016

I'm not disputing that, but since I never build for linux or almost, I'd rather have someone who does review, that's the point of the review process :)

@dgrove-oss
Copy link
Contributor

Got back from vacation today; will dryrun instructions by tomorrow. At first glance they look like they will work.

However, do we want this level of detail in README.md? The INSTALL file has similar (and more detailed) information about building a Swift toolchain that includes libdispatch using utils/build-script --libdispatch -- --install-dispatch. Perhaps README.md should have an explicit pointer to INSTALL for building/install instructions (since this PR suggests that it isn't obvious where to find the information).

@amraboelela
Copy link
Contributor Author

It is ok to have this info in INSTALL and point to it from README.md however can we change INSTALL file to be INSTALL.md (mark down format) just like README.md ?

Sent from my iPhone

On Aug 8, 2016, at 10:37 AM, David Grove notifications@github.com wrote:

Got back from vacation today; will dryrun instructions by tomorrow. At first glance they look like they will work.

However, do we want this level of detail in README.md? The INSTALL file has similar (and more detailed) information about building a Swift toolchain that includes libdispatch using utils/build-script --libdispatch -- --install-dispatch. Perhaps README.md should have an explicit pointer to INSTALL for building/install instructions (since this PR suggests that it isn't obvious where to find the information).


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@MadCoder
Copy link
Contributor

MadCoder commented Aug 8, 2016

I agree this should live in INSTALL

@dgrove-oss
Copy link
Contributor

@MadCoder: any objection to having @amraboelela include changing INSTALL to INSTALL.md when the pull request is updated?

@MadCoder
Copy link
Contributor

MadCoder commented Aug 8, 2016

nope, fine with me

@amraboelela
Copy link
Contributor Author

Does that mean I have to do the change and then make another pull request?

Sent from my iPhone

On Aug 8, 2016, at 1:47 PM, David Grove notifications@github.com wrote:

@MadCoder: any objection to having @amraboelela include changing INSTALL to INSTALL.md when the pull request is updated?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@seabaylea
Copy link
Contributor

Yeah, I agree that this fits better in INSTALL, which should become INSTALL.md. In fact, the whole document could do with refactoring/cleanup.

In terms of the content, I would remove the information on commenting out the tests, and just state that (currently) you have to add libdispatch and install-libdispatch to the build-presets.ini. That should go away shortly once there's libdispatch is fully integrated into the toolchain.

@amraboelela You can either do the work in your existing branch and squash your commits, or create a new PR.

@amraboelela
Copy link
Contributor Author

Done. Please check.

@MadCoder
Copy link
Contributor

MadCoder commented Aug 9, 2016

@seabaylea please review, and if it feels ok @amraboelela please squash in a single commit

@amraboelela
Copy link
Contributor Author

I was trying to do the squash but I failed :)
Any help is appreciated

@dgrove-oss
Copy link
Contributor

@amraboelela
Copy link
Contributor Author

amraboelela commented Aug 9, 2016

Created new pr #138

@amraboelela amraboelela closed this Aug 9, 2016
@amraboelela amraboelela deleted the README branch August 9, 2016 21:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants