librelist archives

« back to archive

Command Line Tools for XCode

Command Line Tools for XCode

From:
Kenneth Reitz
Date:
2012-02-16 @ 18:54
Hey guys — I've been working with Apple since the release of my 
osx-gcc-installer.  

I helped them come up with the requirements and 
command_line_tools_for_xcode is the result of that effort. Apple should be
putting a link to it on their open source page soon.

I know there were some reservations about hombrew supporting 
osx-gcc-installer, but since this is a real Apple product now, made 
*specifically* with Hombrew users in mind, we need to do our best to 
support it. Apple's doing their best to support us.

The only applications that will have trouble are ones that need the 
proprietary headers (CoreAudio, CoreData, OpenGL, etc).  MacVim obviously 
needs these things, but most software doesn't. There are a few surprises, 
though: Node, for example, binds to CoreData for some reason.

I think the best approach here is to give formula the ability to say if 
they need those special headers, and give hombrew the ability to say "hey 
you need full xcode for this formula".  

--  
Kenneth Reitz

Re: Command Line Tools for XCode

From:
Kenneth Reitz
Date:
2012-02-16 @ 19:38
Update: Much to my surprise, they *did* include the proprietary headers. 
This is huge.  

Cheers to all :)  

--  
Kenneth Reitz


On Thursday, February 16, 2012 at 1:54 PM, Kenneth Reitz wrote:

> Hey guys — I've been working with Apple since the release of my 
osx-gcc-installer.  
>  
> I helped them come up with the requirements and 
command_line_tools_for_xcode is the result of that effort. Apple should be
putting a link to it on their open source page soon.
>  
> I know there were some reservations about hombrew supporting 
osx-gcc-installer, but since this is a real Apple product now, made 
*specifically* with Hombrew users in mind, we need to do our best to 
support it. Apple's doing their best to support us.
>  
> The only applications that will have trouble are ones that need the 
proprietary headers (CoreAudio, CoreData, OpenGL, etc).  MacVim obviously 
needs these things, but most software doesn't. There are a few surprises, 
though: Node, for example, binds to CoreData for some reason.
>  
> I think the best approach here is to give formula the ability to say if 
they need those special headers, and give hombrew the ability to say "hey 
you need full xcode for this formula".  
>  
> --  
> Kenneth Reitz
>  

Re: [homebrew] Re: Command Line Tools for XCode

From:
Date:
2012-02-16 @ 19:59
If you choose to install command_line_tools_for_xcode.dmg, be aware that 
there is no uninstaller. Hopefully, Apple will add one.

I welcome the retirement of osx-gcc-installer and gcc-without-xcode.

--
Sorin Ionescu

On 16 Feb 2012, at 14:38, Kenneth Reitz wrote:

> Update: Much to my surprise, they *did* include the proprietary headers.
This is huge.
> 
> Cheers to all :)
> 
> -- 
> Kenneth Reitz
> 
> On Thursday, February 16, 2012 at 1:54 PM, Kenneth Reitz wrote:
> 
>> Hey guys — I've been working with Apple since the release of my 
osx-gcc-installer. 
>> 
>> I helped them come up with the requirements and 
command_line_tools_for_xcode is the result of that effort. Apple should be
putting a link to it on their open source page soon.
>> 
>> I know there were some reservations about hombrew supporting 
osx-gcc-installer, but since this is a real Apple product now, made 
*specifically* with Hombrew users in mind, we need to do our best to 
support it. Apple's doing their best to support us.
>> 
>> The only applications that will have trouble are ones that need the 
proprietary headers (CoreAudio, CoreData, OpenGL, etc).  MacVim obviously 
needs these things, but most software doesn't. There are a few surprises, 
though: Node, for example, binds to CoreData for some reason.
>> 
>> I think the best approach here is to give formula the ability to say if
they need those special headers, and give hombrew the ability to say "hey 
you need full xcode for this formula".
>> 
>> -- 
>> Kenneth Reitz
>> 
> 

Re: [homebrew] Re: Command Line Tools for XCode

From:
Charlie Sharpsteen
Date:
2012-02-16 @ 19:47
On Thu, Feb 16, 2012 at 11:38 AM, Kenneth Reitz <me@kennethreitz.com> wrote:

> Update: Much to my surprise, they *did* include the proprietary headers.
> This is huge.
>
> Cheers to all :)
>
> --
> Kenneth Reitz
>

So, let me get this straight---the command_line_tools_for_xcode.dmg
contains all the compilers and headers needed for development. In short,
all of the Xcode components necessary to compile software but without the
bloat of the GUI and the iOS SDKs?

And this will be posted at opensource.apple.com where people can access it
without creating an Apple ID?

Excuse my incredulity, but my brain is doing a double take at the moment.


-Charlie

Re: [homebrew] Re: Command Line Tools for XCode

From:
Peter Aronoff
Date:
2012-02-16 @ 19:59
On Thu Feb 16 2012 @ 11:47, Charlie Sharpsteen wrote:
> On Thu, Feb 16, 2012 at 11:38 AM, Kenneth Reitz <me@kennethreitz.com> wrote:
> 
> > Update: Much to my surprise, they *did* include the proprietary headers.
> > This is huge.
> >
> > Cheers to all :)
> >
> > --
> > Kenneth Reitz
> >
> 
> So, let me get this straight---the command_line_tools_for_xcode.dmg
> contains all the compilers and headers needed for development. In short,
> all of the Xcode components necessary to compile software but without the
> bloat of the GUI and the iOS SDKs?

Yes. I thikn so.

> And this will be posted at opensource.apple.com where people can access it
> without creating an Apple ID?

Sort of, but not exactly. When I went to download it, I still needed to
enter my "developer" username and password. Having said that, it's a free
developer account, so I imagine most people can live with it.
-- 
[D]igital information lasts forever--or five years, whichever comes first.
    "Ensuring the Longevity of Digital Information", Jeff Rothenberg

Re: [homebrew] Re: Command Line Tools for XCode

From:
Peter Aronoff
Date:
2012-02-16 @ 20:02
On Thu Feb 16 2012 @ 11:47, Charlie Sharpsteen wrote:
> And this will be posted at opensource.apple.com where people can access it
> without creating an Apple ID?

Apologies: I replied too quickly. The package is available _now_ at
https://developer.apple.com/downloads - where you do need an id. I have no
idea if they will eventually place it on opensource.apple.com.

Sorry, P
-- 
[D]igital information lasts forever--or five years, whichever comes first.
    "Ensuring the Longevity of Digital Information", Jeff Rothenberg

Re: [homebrew] Re: Command Line Tools for XCode

From:
Kenneth Reitz
Date:
2012-02-16 @ 20:03
They will link to it from opensource.apple.com soon.

-- 
Kenneth Reitz


On Thursday, February 16, 2012 at 3:02 PM, Peter Aronoff wrote:

> On Thu Feb 16 2012 @ 11:47, Charlie Sharpsteen wrote:
> > And this will be posted at opensource.apple.com 
(http://opensource.apple.com) where people can access it
> > without creating an Apple ID?
> > 
> 
> 
> Apologies: I replied too quickly. The package is available _now_ at
> https://developer.apple.com/downloads - where you do need an id. I have no
> idea if they will eventually place it on opensource.apple.com 
(http://opensource.apple.com).
> 
> Sorry, P
> -- 
> [D]igital information lasts forever--or five years, whichever comes first.
> "Ensuring the Longevity of Digital Information", Jeff Rothenberg
> 
> 

Re: [homebrew] Command Line Tools for XCode

From:
Mike McQuaid
Date:
2012-02-16 @ 20:10
On 16 Feb 2012, at 20:03, Kenneth Reitz wrote:

> They will link to it from opensource.apple.com soon.

Fantastic. Thanks so much for your work here.

In my experience trying to build things just from Xcode (without 
installing these) breaks things like QMake and CMake horribly so I expect 
this will become the requirement for Homebrew rather than Xcode 4.3.

Any idea whether this will install on 10.6 or 10.5 too?

--
Mike McQuaid
http://mikemcquaid.com

Re: [homebrew] Command Line Tools for XCode

From:
Viktor Haag
Date:
2012-02-16 @ 20:42
On 16 February 2012 15:10, Mike McQuaid <mike@mikemcquaid.com> wrote:
>
> In my experience trying to build things just from Xcode (without 
installing these) breaks things like QMake and CMake horribly so I expect 
this will become the requirement for Homebrew rather than Xcode 4.3.

As a new user of Homebrew, I came to it because it was even more easy
and straightforward to use (or seemed so) than Fink, which I had been
using for years.

I fall firmly into that class of users that got a new Mac, put the
XCode developer tools on it, and then started using Homebrew -- I'm
hoping that your comment doesn't mean that future users of Homebrew
will find the XCode dev tools "application" from Apple is an
anti-requisite? That would be most unfortunate... Perhaps I just
didn't full understand your comment?

--
V.

Re: [homebrew] Command Line Tools for XCode

From:
Mike McQuaid
Date:
2012-02-16 @ 21:01
On 16 Feb 2012, at 20:42, Viktor Haag wrote:

> As a new user of Homebrew, I came to it because it was even more easy
> and straightforward to use (or seemed so) than Fink, which I had been
> using for years.
> 
> I fall firmly into that class of users that got a new Mac, put the
> XCode developer tools on it, and then started using Homebrew -- I'm
> hoping that your comment doesn't mean that future users of Homebrew
> will find the XCode dev tools "application" from Apple is an
> anti-requisite? That would be most unfortunate... Perhaps I just
> didn't full understand your comment?

This just means we will recommend you don't use Xcode from the App Store 
but instead the command-line-tools package (which can also be installed 
from inside of Xcode and lives happily alongside it).

--
Mike McQuaid
http://mikemcquaid.com

Re: [homebrew] Command Line Tools for XCode

From:
Charlie Sharpsteen
Date:
2012-02-16 @ 20:13
On Thu, Feb 16, 2012 at 12:10 PM, Mike McQuaid <mike@mikemcquaid.com> wrote:

> Any idea whether this will install on 10.6 or 10.5 too?
>

The package entry on connect.apple.com currently lists OS X 10.7.3 as a
requirement.

-Charlie

Re: [homebrew] Re: Command Line Tools for XCode

From:
Charlie Sharpsteen
Date:
2012-02-16 @ 20:11
On Thu, Feb 16, 2012 at 12:03 PM, Kenneth Reitz <me@kennethreitz.com> wrote:

> They will link to it from opensource.apple.com soon.
>
> --
> Kenneth Reitz
>

Kenneth,

Thanks a bunch for running the flag up the hill on this one. I have been
hoping for something like this to come out of Apple for a long time.

I have been steadily loosing faith in Apple's position on Open Source for a
while now and the release of nicely packaged command line tools and
proprietary headers definitely turns my feelings around.

-Charlie

Re: [homebrew] Re: Command Line Tools for XCode

From:
Kenneth Reitz
Date:
2012-02-16 @ 20:00
You will still need an Apple ID, but only the free one.

-- 
Kenneth Reitz


On Thursday, February 16, 2012 at 2:47 PM, Charlie Sharpsteen wrote:

> On Thu, Feb 16, 2012 at 11:38 AM, Kenneth Reitz <me@kennethreitz.com 
(mailto:me@kennethreitz.com)> wrote:
> > Update: Much to my surprise, they *did* include the proprietary 
headers. This is huge. 
> > 
> > Cheers to all :) 
> > 
> > -- 
> > Kenneth Reitz
> > 
> > 
> 
> 
> So, let me get this straight---the command_line_tools_for_xcode.dmg 
contains all the compilers and headers needed for development. In short, 
all of the Xcode components necessary to compile software but without the 
bloat of the GUI and the iOS SDKs? 
> 
> And this will be posted at opensource.apple.com 
(http://opensource.apple.com) where people can access it without creating 
an Apple ID?
> 
> Excuse my incredulity, but my brain is doing a double take at the moment.
> 
> 
> -Charlie 

Re: [homebrew] Re: Command Line Tools for XCode

From:
Nicolas Desprès
Date:
2012-02-26 @ 18:25
Thanks for these information Kenneth. It is really nice. However I still
have a problem building ruby 1.8.7 which require gcc-4.2 osx-gcc-installer
did also install it. The command_line_tools_for_xcode does not bring it.
Anybody as a solution for that except to install osx-gcc-installer again ?

Thanks,
-Nico

On Thu, Feb 16, 2012 at 8:38 PM, Kenneth Reitz <me@kennethreitz.com> wrote:

> Update: Much to my surprise, they *did* include the proprietary headers.
> This is huge.
>
> Cheers to all :)
>
> --
> Kenneth Reitz
>
> On Thursday, February 16, 2012 at 1:54 PM, Kenneth Reitz wrote:
>
>  Hey guys — I've been working with Apple since the release of my
> osx-gcc-installer.
>
> I helped them come up with the requirements and
> command_line_tools_for_xcode is the result of that effort. Apple should be
> putting a link to it on their open source page soon.
>
> I know there were some reservations about hombrew supporting
> osx-gcc-installer, but since this is a real Apple product now, made
> *specifically* with Hombrew users in mind, we need to do our best to
> support it. Apple's doing their best to support us.
>
> The only applications that will have trouble are ones that need the
> proprietary headers (CoreAudio, CoreData, OpenGL, etc).  MacVim obviously
> needs these things, but most software doesn't. There are a few surprises,
> though: Node, for example, binds to CoreData for some reason.
>
> I think the best approach here is to give formula the ability to say if
> they need those special headers, and give hombrew the ability to say "hey
> you need full xcode for this formula".
>
> --
> Kenneth Reitz
>
>
>


-- 
Nicolas Desprès

Re: [homebrew] Re: Command Line Tools for XCode

From:
Misty De Meo
Date:
2012-02-26 @ 18:45
gcc-4.2 is available from the homebrew-alt repository (
https://github.com/adamv/homebrew-alt) as apple-gcc42.

On Sun, Feb 26, 2012 at 12:25 PM, Nicolas Desprès <nicolas.despres@gmail.com
> wrote:

> Thanks for these information Kenneth. It is really nice. However I still
> have a problem building ruby 1.8.7 which require gcc-4.2 osx-gcc-installer
> did also install it. The command_line_tools_for_xcode does not bring it.
> Anybody as a solution for that except to install osx-gcc-installer again ?
>
> Thanks,
> -Nico
>
>
> On Thu, Feb 16, 2012 at 8:38 PM, Kenneth Reitz <me@kennethreitz.com>wrote:
>
>> Update: Much to my surprise, they *did* include the proprietary headers.
>> This is huge.
>>
>> Cheers to all :)
>>
>> --
>> Kenneth Reitz
>>
>> On Thursday, February 16, 2012 at 1:54 PM, Kenneth Reitz wrote:
>>
>>  Hey guys — I've been working with Apple since the release of my
>> osx-gcc-installer.
>>
>> I helped them come up with the requirements and
>> command_line_tools_for_xcode is the result of that effort. Apple should be
>> putting a link to it on their open source page soon.
>>
>> I know there were some reservations about hombrew supporting
>> osx-gcc-installer, but since this is a real Apple product now, made
>> *specifically* with Hombrew users in mind, we need to do our best to
>> support it. Apple's doing their best to support us.
>>
>> The only applications that will have trouble are ones that need the
>> proprietary headers (CoreAudio, CoreData, OpenGL, etc).  MacVim obviously
>> needs these things, but most software doesn't. There are a few surprises,
>> though: Node, for example, binds to CoreData for some reason.
>>
>> I think the best approach here is to give formula the ability to say if
>> they need those special headers, and give hombrew the ability to say "hey
>> you need full xcode for this formula".
>>
>> --
>> Kenneth Reitz
>>
>>
>>
>
>
> --
> Nicolas Desprès
>
>

Re: [homebrew] Re: Command Line Tools for XCode

From:
Nicolas Desprès
Date:
2012-03-03 @ 18:13
On Sun, Feb 26, 2012 at 7:45 PM, Misty De Meo <mistydemeo@gmail.com> wrote:

> gcc-4.2 is available from the homebrew-alt repository (
> https://github.com/adamv/homebrew-alt) as apple-gcc42.
>
>
Thanks for the tips! I did not think about looking in there. Now it works
perfectly.

Also I have tried to reinstall most of my formula without installing
gcc-4.2 and many just don't work. It seems that it is mandatory for many
program to have this compiler installed since they don't build with the
compiler provided by the command line tools for xcode.

Cheers,
-Nico

>
> On Sun, Feb 26, 2012 at 12:25 PM, Nicolas Desprès <
> nicolas.despres@gmail.com> wrote:
>
>> Thanks for these information Kenneth. It is really nice. However I still
>> have a problem building ruby 1.8.7 which require gcc-4.2 osx-gcc-installer
>> did also install it. The command_line_tools_for_xcode does not bring it.
>> Anybody as a solution for that except to install osx-gcc-installer again ?
>>
>> Thanks,
>> -Nico
>>
>>
>> On Thu, Feb 16, 2012 at 8:38 PM, Kenneth Reitz <me@kennethreitz.com>wrote:
>>
>>> Update: Much to my surprise, they *did* include the proprietary headers.
>>> This is huge.
>>>
>>> Cheers to all :)
>>>
>>> --
>>> Kenneth Reitz
>>>
>>> On Thursday, February 16, 2012 at 1:54 PM, Kenneth Reitz wrote:
>>>
>>>  Hey guys — I've been working with Apple since the release of my
>>> osx-gcc-installer.
>>>
>>> I helped them come up with the requirements and
>>> command_line_tools_for_xcode is the result of that effort. Apple should be
>>> putting a link to it on their open source page soon.
>>>
>>> I know there were some reservations about hombrew supporting
>>> osx-gcc-installer, but since this is a real Apple product now, made
>>> *specifically* with Hombrew users in mind, we need to do our best to
>>> support it. Apple's doing their best to support us.
>>>
>>> The only applications that will have trouble are ones that need the
>>> proprietary headers (CoreAudio, CoreData, OpenGL, etc).  MacVim obviously
>>> needs these things, but most software doesn't. There are a few surprises,
>>> though: Node, for example, binds to CoreData for some reason.
>>>
>>> I think the best approach here is to give formula the ability to say if
>>> they need those special headers, and give hombrew the ability to say "hey
>>> you need full xcode for this formula".
>>>
>>> --
>>> Kenneth Reitz
>>>
>>>
>>>
>>
>>
>> --
>> Nicolas Desprès
>>
>>
>


-- 
Nicolas Desprès

Re: [homebrew] Re: Command Line Tools for XCode

From:
Nicolas Desprès
Date:
2012-03-03 @ 18:33
2012/3/3 Nicolas Desprès <nicolas.despres@gmail.com>

>
>
> On Sun, Feb 26, 2012 at 7:45 PM, Misty De Meo <mistydemeo@gmail.com>wrote:
>
>> gcc-4.2 is available from the homebrew-alt repository (
>> https://github.com/adamv/homebrew-alt) as apple-gcc42.
>>
>>
> Thanks for the tips! I did not think about looking in there. Now it works
> perfectly.
>
> Also I have tried to reinstall most of my formula without installing
> gcc-4.2 and many just don't work. It seems that it is mandatory for many
> program to have this compiler installed since they don't build with the
> compiler provided by the command line tools for xcode.
>

My bad, the autotools were missing on my system. clang works great :-)


>>
>> On Sun, Feb 26, 2012 at 12:25 PM, Nicolas Desprès <
>> nicolas.despres@gmail.com> wrote:
>>
>>> Thanks for these information Kenneth. It is really nice. However I still
>>> have a problem building ruby 1.8.7 which require gcc-4.2 osx-gcc-installer
>>> did also install it. The command_line_tools_for_xcode does not bring it.
>>> Anybody as a solution for that except to install osx-gcc-installer again ?
>>>
>>> Thanks,
>>> -Nico
>>>
>>>
>>> On Thu, Feb 16, 2012 at 8:38 PM, Kenneth Reitz <me@kennethreitz.com>wrote:
>>>
>>>> Update: Much to my surprise, they *did* include the proprietary
>>>> headers. This is huge.
>>>>
>>>> Cheers to all :)
>>>>
>>>> --
>>>> Kenneth Reitz
>>>>
>>>> On Thursday, February 16, 2012 at 1:54 PM, Kenneth Reitz wrote:
>>>>
>>>>  Hey guys — I've been working with Apple since the release of my
>>>> osx-gcc-installer.
>>>>
>>>> I helped them come up with the requirements and
>>>> command_line_tools_for_xcode is the result of that effort. Apple should be
>>>> putting a link to it on their open source page soon.
>>>>
>>>> I know there were some reservations about hombrew supporting
>>>> osx-gcc-installer, but since this is a real Apple product now, made
>>>> *specifically* with Hombrew users in mind, we need to do our best to
>>>> support it. Apple's doing their best to support us.
>>>>
>>>> The only applications that will have trouble are ones that need the
>>>> proprietary headers (CoreAudio, CoreData, OpenGL, etc).  MacVim obviously
>>>> needs these things, but most software doesn't. There are a few surprises,
>>>> though: Node, for example, binds to CoreData for some reason.
>>>>
>>>> I think the best approach here is to give formula the ability to say if
>>>> they need those special headers, and give hombrew the ability to say "hey
>>>> you need full xcode for this formula".
>>>>
>>>> --
>>>> Kenneth Reitz
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Nicolas Desprès
>>>
>>>
>>
>
>
> --
> Nicolas Desprès
>
>


-- 
Nicolas Desprès

Re: [homebrew] Re: Command Line Tools for XCode

From:
Terin Stock
Date:
2012-03-03 @ 18:40
I was about to say, I have 42 formulas installed and 0 of them were 
installed with GCC.  

--  
#Terin Stock


On Saturday, March 3, 2012 at 1:33 PM, Nicolas Desprès wrote:

>  
>  
> 2012/3/3 Nicolas Desprès <nicolas.despres@gmail.com 
(mailto:nicolas.despres@gmail.com)>
> >  
> >  
> > On Sun, Feb 26, 2012 at 7:45 PM, Misty De Meo <mistydemeo@gmail.com 
(mailto:mistydemeo@gmail.com)> wrote:
> > > gcc-4.2 is available from the homebrew-alt repository 
(https://github.com/adamv/homebrew-alt) as apple-gcc42.
> > >  
> >  
> > Thanks for the tips! I did not think about looking in there. Now it 
works perfectly.
> >  
> > Also I have tried to reinstall most of my formula without installing 
gcc-4.2 and many just don't work. It seems that it is mandatory for many 
program to have this compiler installed since they don't build with the 
compiler provided by the command line tools for xcode.  
>  
> My bad, the autotools were missing on my system. clang works great :-)
>  
> > >  
> > >  
> > > On Sun, Feb 26, 2012 at 12:25 PM, Nicolas Desprès 
<nicolas.despres@gmail.com (mailto:nicolas.despres@gmail.com)> wrote:
> > > > Thanks for these information Kenneth. It is really nice. However I
still have a problem building ruby 1.8.7 which require gcc-4.2 
osx-gcc-installer did also install it. The command_line_tools_for_xcode 
does not bring it. Anybody as a solution for that except to install 
osx-gcc-installer again ?
> > > >  
> > > > Thanks,
> > > > -Nico
> > > >  
> > > >  
> > > > On Thu, Feb 16, 2012 at 8:38 PM, Kenneth Reitz 
<me@kennethreitz.com (mailto:me@kennethreitz.com)> wrote:
> > > > > Update: Much to my surprise, they *did* include the proprietary 
headers. This is huge.  
> > > > >  
> > > > > Cheers to all :)  
> > > > >  
> > > > > --  
> > > > > Kenneth Reitz
> > > > >  
> > > > >  
> > > > > On Thursday, February 16, 2012 at 1:54 PM, Kenneth Reitz wrote:
> > > > >  
> > > > > > Hey guys — I've been working with Apple since the release of 
my osx-gcc-installer.  
> > > > > >  
> > > > > > I helped them come up with the requirements and 
command_line_tools_for_xcode is the result of that effort. Apple should be
putting a link to it on their open source page soon.  
> > > > > >  
> > > > > > I know there were some reservations about hombrew supporting 
osx-gcc-installer, but since this is a real Apple product now, made 
*specifically* with Hombrew users in mind, we need to do our best to 
support it. Apple's doing their best to support us.  
> > > > > >  
> > > > > > The only applications that will have trouble are ones that 
need the proprietary headers (CoreAudio, CoreData, OpenGL, etc).  MacVim 
obviously needs these things, but most software doesn't. There are a few 
surprises, though: Node, for example, binds to CoreData for some reason.  
> > > > > >  
> > > > > > I think the best approach here is to give formula the ability 
to say if they need those special headers, and give hombrew the ability to
say "hey you need full xcode for this formula".  
> > > > > >  
> > > > > > --  
> > > > > > Kenneth Reitz
> > > > > >  
> > > > >  
> > > >  
> > > >  
> > > >  
> > > > --  
> > > > Nicolas Desprès
> > > >  
> > >  
> >  
> >  
> >  
> > --  
> > Nicolas Desprès
> >  
>  
>  
>  
> --  
> Nicolas Desprès
>