Contents of /xml/htdocs/proj/en/prog_lang/index.xml

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.10 - (hide annotations) (download) (as text)
Tue Jul 22 05:42:23 2008 UTC (10 years, 6 months ago) by graaff
Branch: MAIN
Changes since 1.9: +2 -1 lines
File MIME type: application/xml
Add ruby subproject as discussed with george in email

1 george 1.1 <?xml version="1.0" encoding="UTF-8"?>
2     <?xml-stylesheet href="/xsl/project.xsl" type="text/xsl"?>
3     <?xml-stylesheet href="/xsl/guide.xsl" type="text/xsl"?>
4     <!DOCTYPE project SYSTEM "/dtd/project.dtd">
5     <project>
6 nattfodd 1.5 <name>Gentoo Programming Resources</name>
7     <longname>Gentoo Resources for Programming Languages</longname>
8 george 1.1
9 graaff 1.10 <date>22 Jul 2008</date>
10 george 1.3
11 nattfodd 1.5 <author title="Developer">
12     <mail link="george@gentoo.org">George Shapovalov</mail>
13     </author>
16     <description>
17     Gentoo Specific Support for Programming Environments.
18     </description>
20 neysx 1.7 <longdescription><p>
21 nattfodd 1.5 The project provides coverage for Gentoo specific issues associated with
22     various programming languages that can be found in portage. Right now the
23     top level is mostly a placeholder for all the individual subprojects. However
24     common initiatives covering the topic are wellcome! Everybody interested is
25     invited to take a look at the
26     <uri link="https://bugs.gentoo.org/show_bug.cgi?id=151118">bug #151118</uri>
27     and take part in discussion.
28 neysx 1.7 </p></longdescription>
29 nattfodd 1.5
30     <goals>
31     <p>
32     The overal goal is to provide necessary resources supporting "The Gentoo
33     Way" of dealing with programming environments. That is, flexible setup
34     and, where it makes sense, coexisting multiple versions/realizations of
35     compilers with an easy way to switch between those, while automating
36     mundane tasks.
37     </p>
39     <p>
40     Often it happens that multiple compiler suits can be used to compile
41     existing libraries. However the resulting libs are usually ABI
42     incompatible, meaning that code utilizing these libs should be compiled
43     with the same compiler. This situation can be further complicated by
44     interdependencies between the provided libs. To address this situation it
45     is necessary to introduce some kind of "ABI tracking" ability. Ideally
46     this would be done by providing some extra dependency info and having
47     portage deal with it. However this requires support on the portage side
48     and as it is not going to happen soon. There is a discussion under way on
49     how this can be done now. Those interested please take a look at <uri
50     link="https://bugs.gentoo.org/show_bug.cgi?id=151343">bug
51     #151343</uri>.
52     </p>
54     <p>
55     Another issue common to multiple language implementations is that quite a
56     few of them have a compiler that is a gcc frontend. As such their build
57     procedure is quite similar and so it would make sense to work on a common
58     eclass, possibly even combining everything with toolchain.eclass. The
59     affected compilers that I had to deal with are: gpc (Pascal, in portage),
60     gdc (D, not in portage but has may interested users) and gnat (Ada). The
61     last one in fact is further subdivided into gnat-gcc for version produced
62     by FSF and gnat-gpl produced by AdaCore. These gnat versions have a
63     proper eclass common to all of them, and thus other compilers can be based
64     on that one.
65     </p>
66 george 1.1
67 nattfodd 1.5 </goals>
69     <dev role="Lead">george</dev>
70 george 1.1
71     <subproject ref="/proj/en/prog_lang/ada/index.xml"/>
72 dcoutts 1.6 <subproject ref="/proj/en/prog_lang/haskell/index.xml"/>
73 graaff 1.10 <subproject ref="/proj/en/prog_lang/ruby/index.xml" />
74 george 1.1
75     </project>

  ViewVC Help
Powered by ViewVC 1.1.20