-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Archive sources for integration builds #6929
Comments
cc @mkustermann. |
This comment was originally written by rod...@gmail.com Without source releases, it's increadibly akward to package dart as an official Arch Linux package. Please provide a source tarball per release. |
Removed Area-Build label. |
Issue #15459 has been merged into this issue. |
Supplying a tarball of the sources for building will be a lot of additional work. Besides the sources from the dart SVN repro there are the third_party directories, and on top of that additional platform specific dependencies are fetched form Google Cloud Storage. Also the third_party directory will contain stuff (like the d8 binaries) which should be filtered out when preparing a tarball. The next issueare the makefiles. These are generated from the gyp-files also using gclient. The makefiles generated are suitable for distribution - they may contain absolute paths and other specific details. There are no guarantees of portability. Last but not least we will need to test this additional distribution. This means additional build-bots for tracking this. We would very much like it to be easy for Linux distributions to include Dart, by making the build process as smooth as possible using the current build-tools. The depot_tools (containing gclient and additional tools) is available both as an SVN checkout and a tarball, and the following commands should build the 64-bit runtime target: svn co http://src.chromium.org/svn/trunk/tools/depot_tools Building the SDK and editor require installing Java (openjdk-6-jdk) as well. sudo install openjdk-6-jdk The above uses bleeding_edge, change accordingly for the other channels: gclient config http://dart.googlecode.com/svn/trunk/deps/all.deps Removed Type-Defect label. |
In comment#5 sudo install openjdk-6-jdk should be sudo apt-get install openjdk-6-jdk or sudo yum install java-1.6.0-openjdk-devel depending on the distribution. |
It is possible to get specific revisions by changing: |
This comment was originally written by beatg...@gmail.com Has there been any update on this? Dart has been in 1.x for over a year now, so perhaps external dependencies have settled down a bit, especially for just the Dart VM? Source releases with minimal (hopefully zero) dependencies on forked projects would make porting a lot easier. As I've mentioned in issue #10260, I'm interested in porting to FreeBSD, but working with gclient (and to some extent gyp) is painful, especially since the build process is so bizarre and complicated. |
Do the tarballs at, e.g., http://gsdview.appspot.com/dart-archive/channels/stable/raw/44672/src/ resolve this issue? The third party dependencies are included. |
This comment was originally written by @mulander #9 looks like it could. I've been waiting a long time for this. I'm attempting to do an OpenBSD port, starting The main question I have with your URL: The chromium project hosts a https://gsdview.appspot.com/chromium-browser-official/ which nicely lists all release tarballs in a single place. This makes it easy for port maintainers to find the proper download links and allows the port infrastructure to do most of the work. The URL you provided http://gsdview.appspot.com/dart-archive/channels/stable/raw/44672/src/ has an unpredictable path. How do I locate the proper release tarball for a dart version as you seem to include the revision in the URL and some of the other folders I looked at don't even contain the src folder? |
This comment was originally written by @mulander The biggest difference I see between the Chrome build & dart is the handling of makefiles. Doing the standard: Results in a source tree that's ready to build with: Using the provided download URL both on Linux & OpenBSD Linux: OpenBSD: I cross checked with the www/chromium build on OpenBSD and it seems that Chromium provides a great build/linux/unbundle/replace_gyp_files.py which gyp_chromium generates all the Makefiles from gypdo-configure: Is there a way to achieve the same with Dart? |
This comment was originally written by @mulander OK I managed to generate the Makefiles without using gclient. do-configure: $ make configure So the tarball indeed looks workable. I guess this issue can be closed though a more predictable path for downloads would be appreciated). |
This comment was originally written by @mulander OK one more issue. Why is third_party/clang not included? Are we forced to build with GCC? $ ls third_party/clang From a manual gclient checkout: |
First off, very nice that somebody is doing work the get us going on bsd. Regarding clang, we explicitly exclude some binary dependencies due to size, see tools/create_tarball.py in a regular dart checkout. If this is a major blocker we can add it to the tarball, but you should be able to easily pull it of svn (will be git soon) if needed: Regarding predictable paths for download: Added Fixed label. |
For easy access to the source code for a specific revision we should store a tarball of the sources for integration builds.
The text was updated successfully, but these errors were encountered: