On Tue, 2012-04-03 at 12:03 +0200, Richard Guenther wrote:
> On Mon, Apr 2, 2012 at 7:21 PM, David Malcolm <[email protected]> wrote:
> > I wrote a script and ported my proposed API for GCC plugins from my
> > CamelCase naming convention to an underscore_based_convention (and
> > manually fixed up things in a few places also).
> >
> > The result compiles and passes the full test suite for the Python
> > plugin; that said, I'm still breaking the encapsulation in quite a few
> > places (hey, this is an experimental prototype).
> >
> > You can see the latest version of it within the "proposed-plugin-api"
> > branch of the Python plugin here:
> > http://git.fedorahosted.org/git/?p=gcc-python-plugin.git;a=shortlog;h=refs/heads/proposed-plugin-api
> >
> > within the "proposed-plugin-api" subdirectory.
>
> Hmm, how do I get it? I did
>
> git clone http://git.fedorahosted.org/git/proposed-plugin-api
>
> but there is nothing in gcc-python-plugin/. And
>
> git checkout proposed-plugin-api
>
> says I'm already there ...?
I'm sorry that this was unclear.
To checkout the source, on the "proposed-plugin-api" branch:
$ git clone git://git.fedorahosted.org/gcc-python-plugin.git -b
proposed-plugin-api
Cloning into gcc-python-plugin...
remote: Counting objects: 8375, done.
[...snip...]
Resolving deltas: 100% (5774/5774), done.
Go into the new working copy:
$ cd gcc-python-plugin/
Verify that you're on the experimental branch:
$ git branch
* proposed-plugin-api
The code in the root directory is specific to my Python plugin. The
proposed generic plugin API is in a subdirectory which confusingly has
the same name as the branch (sorry):
$ cd proposed-plugin-api
(If you're interested in the python plugin, detailed instructions on
building from source can be seen at [1])
Sorry about the confusion
Dave
[1]
http://gcc-python-plugin.readthedocs.org/en/latest/basics.html#building-the-plugin-from-source
