Displaying 3 results from an estimated 3 matches for "llvmtooldirslash".
2005 Feb 10
0
[LLVMdev] Add ability for external projects use for buildinstalled version LLVM [PATCH]
Vladimir,
I took a *very quick* look at your patch. I won't be able to look at it in more
detail until this weekend, but perhaps you can address a couple of concerns:
1. I don't understand the need for LLVMToolDirSlash. This seems like a
gratuitous change to me.
2. I don't think the change to CPP.Flags is right. It won't find the LLVM
header files
3. Removing the .PRECIOUS line will interfere with correct operation of
parallel (make -j N) builds.
4. I don't understand why LLVMUsedLibs and...
2005 Feb 09
2
[LLVMdev] Add ability for external projects use for buildinstalled version LLVM [PATCH]
>> Patch attached.
>>
>> This patch with header installation patch (
>> http://mail.cs.uiuc.edu/pipermail/llvmdev/2005-February/003300.html )
>> let external project (I am test it at my YAFL frontend for LLVM) build
>> using installed LLVM version instead using LLVM obj/src dirs.
>
> I think the patch looks basically sane. The one wierd thing I notice
2005 Feb 10
2
[LLVMdev] Add ability for external projects use for build installed version LLVM [PATCH]
> Vladimir,
>
> I took a *very quick* look at your patch. I won't be able to look at it in
> more detail until this weekend, but perhaps you can address a couple of
> concerns:
>
> 1. I don't understand the need for LLVMToolDirSlash. This seems like a
> gratuitous change to me.
If LLVM_OBJ_ROOT (with LLVM_SRC_ROOT) and LLVM_ROOT both not set
without LLVMToolDirSlash we will have "/gccas$(EXEEXT)", for example.
This is not problem for project that not use LLVM tools and libs.
But this not permite one useful case...