/[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.11 - (show annotations) (download) (as text)
Tue Jun 16 17:57:39 2015 UTC (3 years, 6 months ago) by creffett
Branch: MAIN
CVS Tags: HEAD
Changes since 1.10: +2 -1 lines
File MIME type: application/xml
Mark programming as migrated

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

  ViewVC Help
Powered by ViewVC 1.1.20