/[gentoo]/xml/htdocs/proj/en/prog_lang/index.xml
Gentoo

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

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.3 - (show annotations) (download) (as text)
Sat Nov 11 19:36:48 2006 UTC (11 years, 7 months ago) by george
Branch: MAIN
Changes since 1.2: +7 -0 lines
File MIME type: application/xml
added date and author tags

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 <name>Gentoo Programming Resources</name>
7 <longname>Gentoo Resources for Programming Languages</longname>
8
9 <date>11 Nov 2006</date>
10
11 <author title="Developer">
12 <mail link="george@gentoo.org">George Shapovalov</mail>
13 </author>
14
15
16 <description>
17 "Gentoo Specific Support for Programming Environments."
18 </description>
19
20 <longdescription>
21 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 </longdescription>
29
30 <goals>
31 <p>
32 The overal goal is to provide necessary resources supporting "The Gentoo Way" of dealing
33 with programming environments. That is, flexible setup and, where it makes sense,
34 coexisting multiple versions/realizations of compilers with an easy way to switch between those,
35 while automating mundane tasks.
36 </p>
37
38 <p>
39 Often it happens that multiple compiler suits can be used to compile existing libraries.
40 However the resulting libs are usually ABI incompatible, meaning that code utilizing
41 these libs should be compiled with the same compiler. This situation can be further
42 complicated by interdependencies between the provided libs. To address this situation
43 it is necessary to introduce some kind of "ABI tracking" ability. Ideally this would be done
44 by providing some extra dependency info and having portage deal with it. However this
45 requires support on the portage side and as it is not going to happen soon.
46 There is a discussion under way on how this can be done now. Those interested please
47 take a look at <uri link="https://bugs.gentoo.org/show_bug.cgi?id=151343">bug #151343</uri>.
48 </p>
49
50 <p>
51 Another issue common to multiple language implementations is that quite a few of them
52 have a compiler that is a gcc frontend. As such their build procedure is quite similar and
53 so it would make sense to work on a common eclass, possibly even combining everything with
54 toolchain.eclass. The affected compilers that I had to deal with are: gpc (Pascal, in portage),
55 gdc (D, not in portage but has may interested users) and gnat (Ada). The last one in fact is
56 further subdivided into gnat-gcc for version produced by FSF and gnat-gpl produced by AdaCore.
57 These gnat versions have a proper eclass common to all of them, and thus other compilers
58 can be based on that one.
59 </p>
60
61 </goals>
62
63 <dev role="lead">george</dev>
64
65
66 <subproject ref="/proj/en/prog_lang/ada/index.xml"/>
67
68
69 </project>

  ViewVC Help
Powered by ViewVC 1.1.20