[cfe-commits] r67204 - in /cfe/trunk/lib/Driver: Driver.cpp Makefile

Daniel Dunbar daniel at zuster.org
Wed Mar 18 12:53:56 PDT 2009


Ok; one more request. :)

Can the .ver-svn temporary file go in the build products directory, not the
source dir?

 - Daniel

On Wed, Mar 18, 2009 at 12:05 PM, Daniel Dunbar <daniel at zuster.org> wrote:

> Nice! Two minor requests:
>
> 1. Can tools/driver/driver.cpp pass this in instead of having inside the
> lib. The version should be particular to the client not the library.
>
> 2. Not sure about this; but do you have enough Makefile foo that we could
> automatically do this every time the clang-driver executable was linked (but
> only then)?
>
>  - Daniel
>
>
> On Wed, Mar 18, 2009 at 11:51 AM, Mike Stump <mrs at apple.com> wrote:
>
>> On Mar 18, 2009, at 10:39 AM, Daniel Dunbar wrote:
>>
>>> ccc version 1.0 (http://llvm.org/svn/llvm-project/cfe/trunk)
>>>
>>> which I think is fine.  If someone tags clang, say for an llvm release,
>>> it will have the release tag.  If we want to add the svn revision
>>> information, a la gcc, we could do that, but it is a harder to get at and
>>> isn't always available (svn export say).
>>>
>>> Yes, this is what I meant.
>>>
>>
>> Ah, fixed:
>>
>> $ clang-driver  -v
>> ccc version 1.0 (https://mrs@llvm.org/svn/llvm-project/cfe/trunk67214:67220)
>> $ cvn ci
>> $ make
>> $ clang-driver  -v
>> ccc version 1.0 (https://mrs@llvm.org/svn/llvm-project/cfe/trunk 67220)
>>
>> :-)
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20090318/1efaf592/attachment.html>


More information about the cfe-commits mailing list