[dart-misc] Dart SDK on Redhat (RHEL 6.x)

[Dana Irvin]

Hi, Dartisans. I wanted to pick your collective brains about how to build
the SDK on RHEL 6.x. It seems the instructions with regards to using
depot-tools, etc. don't currently work with RHEL. The gclient script seems
to crash because of some import error with argparse. This isn't the first
time I've had issues with merely getting the SDK source using gclient. I
actually don't think I've been able to get a version later than 1.5.1.
There is always something with depot-tools.

My question is this: is there a way to get the source and create whatever
makefiles are needed, without using depot_tools? I've tried merely cloning
the SDK repo, and trying to use the build.py script. It seems that
depot_tools do something regarding configuring things not accomplished
elsewhere. Am I missing something? Is there a build process that doesn't
use depot_tools documented somewhere?

Thanks,

-Dirv

[Eduardo Teixeira Dias]

I followed the instructions of
Niek Vlessert

In this discussion:
https://groups.google.com/forum/#!topic/sipxcom-dev/EeRsfbh32CA

Cheers

Post by Dana Irvin
Hi, Dartisans. I wanted to pick your collective brains about how to build
the SDK on RHEL 6.x. It seems the instructions with regards to using
depot-tools, etc. don't currently work with RHEL. The gclient script seems
to crash because of some import error with argparse. This isn't the first
time I've had issues with merely getting the SDK source using gclient. I
actually don't think I've been able to get a version later than 1.5.1.
There is always something with depot-tools.
My question is this: is there a way to get the source and create whatever
makefiles are needed, without using depot_tools? I've tried merely cloning
the SDK repo, and trying to use the build.py script. It seems that
depot_tools do something regarding configuring things not accomplished
elsewhere. Am I missing something? Is there a build process that doesn't
use depot_tools documented somewhere?
Thanks,
-Dirv
--
For other discussions, see https://groups.google.com/a/dartlang.org/
For HOWTO questions, visit http://stackoverflow.com/tags/dart
To file a bug report or feature request, go to http://www.dartbug.com/new
To unsubscribe from this group and stop receiving emails from it, send an

['Søren Gjesse' via Dart Misc]

I think parts of the tooling we have for building packages for Debian can
be used for building on Red Hat.

We have scripts in the repo that can build packages for Debian. This is all
based on a tarball containing all source and custom tools for building an
SDK. Creating Debian packages is done by running the following commands
(links to the source is provided):

$ tools/create_tarball.py
<https://github.com/dart-lang/sdk/blob/master/tools/create_tarball.py>
$ tools/create_debian_packages.py
<https://github.com/dart-lang/sdk/blob/master/tools/create_debian_packages.py>

The configuration for the Debian package is here:
https://github.com/dart-lang/sdk/tree/master/tools/linux_dist_support/debian
.

We build the Debian packages for each release, and as part of the source
package the original tarball is also available. For 1.12.2 it can be
downloaded here:
https://storage.googleapis.com/dart-archive/channels/stable/release/1.12.2/linux_packages/debian_wheezy/dart_1.12.2.orig.tar.gz
.

Hopefuly the tarball should be sufficient for building on Red Hat as well.
The rules
<https://github.com/dart-lang/sdk/blob/master/tools/linux_dist_support/debian/rules>
in the Debian package is just a makefile that only relies on the tarball,
python and gcc (and well for Debian the debhelper package is also required).

When we build the Debian images for distribution it is happening in a
Debian wheezy chroot, to make sure our glibc dependencies are so that the
package will work on wheezy and upwards. Therefore there should be no
hidden dependencies. The script for creating the chroot environment is
tools/create_debian_chroot.sh
<https://github.com/dart-lang/sdk/blob/master/tools/create_debian_chroot.sh>,
and the only additional packages installed in the chroot are python g++-4.6
git and subversion.

Regards,
SÞren

---
SÞren Gjesse
Software Engineer, Google Denmark
CVR nr. 28 86 69 84

On Thu, Oct 29, 2015 at 7:35 PM, Eduardo Teixeira Dias <

Post by Eduardo Teixeira Dias
I followed the instructions of
Niek Vlessert
https://groups.google.com/forum/#!topic/sipxcom-dev/EeRsfbh32CA
Cheers

Post by Dana Irvin
Hi, Dartisans. I wanted to pick your collective brains about how to build
the SDK on RHEL 6.x. It seems the instructions with regards to using
depot-tools, etc. don't currently work with RHEL. The gclient script seems
to crash because of some import error with argparse. This isn't the first
time I've had issues with merely getting the SDK source using gclient. I
actually don't think I've been able to get a version later than 1.5.1.
There is always something with depot-tools.
My question is this: is there a way to get the source and create whatever
makefiles are needed, without using depot_tools? I've tried merely cloning
the SDK repo, and trying to use the build.py script. It seems that
depot_tools do something regarding configuring things not accomplished
elsewhere. Am I missing something? Is there a build process that doesn't
use depot_tools documented somewhere?
Thanks,
-Dirv
--
For other discussions, see https://groups.google.com/a/dartlang.org/
For HOWTO questions, visit http://stackoverflow.com/tags/dart
To file a bug report or feature request, go to http://www.dartbug.com/new
To unsubscribe from this group and stop receiving emails from it, send an

--
For other discussions, see https://groups.google.com/a/dartlang.org/
For HOWTO questions, visit http://stackoverflow.com/tags/dart
To file a bug report or feature request, go to http://www.dartbug.com/new
To unsubscribe from this group and stop receiving emails from it, send an

[Kao peter]

Cent OS 6 Pre-build version: https://github.com/cjkao/dart-sdk-cent-os-6

On Fri, Oct 30, 2015 at 6:48 PM, 'SÞren Gjesse' via Dart Misc <

Post by 'Søren Gjesse' via Dart Misc
I think parts of the tooling we have for building packages for Debian can
be used for building on Red Hat.
We have scripts in the repo that can build packages for Debian. This is
all based on a tarball containing all source and custom tools for building
an SDK. Creating Debian packages is done by running the following commands
$ tools/create_tarball.py
<https://github.com/dart-lang/sdk/blob/master/tools/create_tarball.py>
$ tools/create_debian_packages.py
<https://github.com/dart-lang/sdk/blob/master/tools/create_debian_packages.py>
https://github.com/dart-lang/sdk/tree/master/tools/linux_dist_support/debian
.
We build the Debian packages for each release, and as part of the source
package the original tarball is also available. For 1.12.2 it can be
https://storage.googleapis.com/dart-archive/channels/stable/release/1.12.2/linux_packages/debian_wheezy/dart_1.12.2.orig.tar.gz
.
Hopefuly the tarball should be sufficient for building on Red Hat as well.
The rules
<https://github.com/dart-lang/sdk/blob/master/tools/linux_dist_support/debian/rules>
in the Debian package is just a makefile that only relies on the tarball,
python and gcc (and well for Debian the debhelper package is also required).
When we build the Debian images for distribution it is happening in a
Debian wheezy chroot, to make sure our glibc dependencies are so that the
package will work on wheezy and upwards. Therefore there should be no
hidden dependencies. The script for creating the chroot environment is
tools/create_debian_chroot.sh
<https://github.com/dart-lang/sdk/blob/master/tools/create_debian_chroot.sh>,
and the only additional packages installed in the chroot are python g++-4.6
git and subversion.
Regards,
SÞren
---
SÞren Gjesse
Software Engineer, Google Denmark
CVR nr. 28 86 69 84
On Thu, Oct 29, 2015 at 7:35 PM, Eduardo Teixeira Dias <

Post by Eduardo Teixeira Dias
I followed the instructions of
Niek Vlessert
https://groups.google.com/forum/#!topic/sipxcom-dev/EeRsfbh32CA
Cheers

Post by Dana Irvin
Hi, Dartisans. I wanted to pick your collective brains about how to
build the SDK on RHEL 6.x. It seems the instructions with regards to using
depot-tools, etc. don't currently work with RHEL. The gclient script seems
to crash because of some import error with argparse. This isn't the first
time I've had issues with merely getting the SDK source using gclient. I
actually don't think I've been able to get a version later than 1.5.1.
There is always something with depot-tools.
My question is this: is there a way to get the source and create
whatever makefiles are needed, without using depot_tools? I've tried merely
cloning the SDK repo, and trying to use the build.py script. It seems that
depot_tools do something regarding configuring things not accomplished
elsewhere. Am I missing something? Is there a build process that doesn't
use depot_tools documented somewhere?
Thanks,
-Dirv
--
For other discussions, see https://groups.google.com/a/dartlang.org/
For HOWTO questions, visit http://stackoverflow.com/tags/dart
To file a bug report or feature request, go to
http://www.dartbug.com/new
To unsubscribe from this group and stop receiving emails from it, send

--
For other discussions, see https://groups.google.com/a/dartlang.org/
For HOWTO questions, visit http://stackoverflow.com/tags/dart
To file a bug report or feature request, go to http://www.dartbug.com/new
To unsubscribe from this group and stop receiving emails from it, send an

--
For other discussions, see https://groups.google.com/a/dartlang.org/
For HOWTO questions, visit http://stackoverflow.com/tags/dart
To file a bug report or feature request, go to http://www.dartbug.com/new
To unsubscribe from this group and stop receiving emails from it, send an