This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: plugins & howto & generators

From: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
To: Manuel López-Ibáñez <lopezibanez at gmail dot com>
Cc: Basile STARYNKEVITCH <basile at starynkevitch dot net>, GCC Mailing List <gcc at gcc dot gnu dot org>
Date: Wed, 27 May 2009 19:10:13 +0100
Subject: Re: plugins & howto & generators
References: <4A1D5CAB.1080004@starynkevitch.net> <6c33472e0905270930p2239b6f8u91916f4beb934804@mail.gmail.com>

Manuel López-Ibáñez wrote:
> 2009/5/27 Basile STARYNKEVITCH <basile@starynkevitch.net>:

>> Should we tell them (the other users using the future gcc-4.5-dev Debian
>> package) in our documentation how to build a plugin (I mean what are the
>> actual commands to run, what kind of Makefile for them, what are the
>> required CFLAGS or -I... path, etc..), or should that be left to e.g. linux
>> distribution packagers?
> 
> A complete tutorial on how to create and build a generic plugin is
> perhaps more suited for the wiki than for the internals documentation.

  But something along the lines of this:

http://gcc.gnu.org/onlinedocs/gccint/Front-End.html
http://gcc.gnu.org/onlinedocs/gccint/Front-End-Directory.html

... level of detail might be appropriate, no?  A simple checklist to get
people started.

    cheers,
      DaveK

References:
- plugins & howto & generators
  - From: Basile STARYNKEVITCH
- Re: plugins & howto & generators
  - From: Manuel López-Ibáñez

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]