Differences between revisions 4 and 5
Revision 4 as of 2012-04-03 16:54:38
Size: 2719
Editor: ?ThibautGirka
Comment:
Revision 5 as of 2012-04-06 18:58:45
Size: 2945
Editor: ?ThibautGirka
Comment:
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:
      * Make sure the toolchain actually builds something, if not, fix it.       * Make sure the toolchain actually builds something, if not, fix it. “Something” should be some arch:all package available in Debian main, with few, common dependencies, and taking at most a few minutes to build. Something like nano sounds fine.
Line 20: Line 20:
      Add support for explicit cross-arch dependencies and build-dependencies to dpkg and related software.       Add support for explicit cross-arch dependencies and build-dependencies to dpkg and related software (probably apt, maybe things like devscripts).
  • Name: Thibaut Girka

  • Contact/Email: thib@sitedethib.com (preferred), thibaut.girka@gmail.com, xmpp:thib@sitedethib.com, ThibG on IRC

  • Background: I'm a third-year student at the Versailles Saint-Quentin-en-Yvelines University (UVSQ), Debian user since 2007 (I use it on my main computer, my personal server, and my Efika MX Smartbook). I have very good skills in Python, good skills in C, reasonable skills in C++ and shell scripting. I have experience in contributing to FLOSS projects and manage a few small-sized ones.

  • Project title: Multiarch Cross-Toolchains

  • Project details: See http://wiki.debian.org/SummerOfCode2012/Projects#Multiarch_Cross-Toolchains

  • Synopsis: Make sure existing cross-toolchains actually work on multi-arch systems and produce multiarch-compliant binaries, then switch from dpkg-cross dependencies to cross-arch dependencies.

  • Benefits to Debian: <TODO>

  • Deliverables:

    • Explicit cross-arch dependencies support for dpkg and related software
    • Cross-toolchain packages using cross-arch dependencies, building against multiarched libraries, and defaulting to doing cross-builds using multiarch paths.
    • Tools changes to support this in the archive
  • Project schedule:

    • [April - May 13]

      • Build and install a cross-toolchain (build: i386, host: armhf) as described at http://wiki.debian.org/BuildingCrossCompilers

      • Make sure the toolchain actually builds something, if not, fix it. “Something” should be some arch:all package available in Debian main, with few, common dependencies, and taking at most a few minutes to build. Something like nano sounds fine.
      • Make sure the produced binaries use multiarch pathes. If not, fix the toolchain.
      • Learn about toolchain packaging.

      [May 13 - June 24]

      • Add support for explicit cross-arch dependencies and build-dependencies to dpkg and related software (probably apt, maybe things like devscripts).

      [June 24 - July 1]

      • Change the toolchain packaging to switch from dpkg-cross dependencies to cross-arch dependencies.

      [July 1 - July 9]

      • Check, fix bugs, prepare for the midterm evaluation

      [July 9 - July 13]

      • Midterm evaluation

      [July 13 - August 20]

      • Address automated build and consider inclusion into the main archive.
  • Exams and other commitments: I have my final exams at the end of May, I won't have any commitment after that.

  • Other summer plans: Nothing special. No job nor long vacation.

  • Why Debian? Well, I've been a Debian user for a while, now, and I have always been happy with it. I admire how Debian focuses on quality, and considers FTBFS and non-compliance to DFSG as serious bugs. However, I rarely contribute back, and I think this project is a good opportunity.

  • I'm not applying for other projects in this SoC.