[LLVMdev] Embed LLVM/Clang in our project
daniel.dunbar at gmail.com
Tue Jan 22 00:15:14 PST 2013
This is just standard behavior of the Python interpreter. The files
are just a cache (it is not the sources being modified) and also won't
be written if the source tree is made read only, and shouldn't cause a
problem in practice.
On Jan 22, 2013, at 0:02, Duncan Sands <baldrick at free.fr> wrote:
> I would have expected the .pyc files to go in the objects directory. Maybe
> Daniel knows why that's not happening.
> Ciao, Duncan.
> On 22/01/13 00:48, Ashok Nalkund wrote:
>> On 1/21/2013 10:25 AM, Ashok Nalkund wrote:
>>> On 1/21/2013 2:01 AM, Óscar Fuentes wrote:
>>>> Ashok Nalkund <ashoknn at qti.qualcomm.com> writes:
>>>>> I was using the find_package(LLVM llvm/share/llvm/cmake) and
>>>>> llvm_map_components_to_libraries(REQ_LLVM_LIBRARIES jit native) to get
>>>>> the libraries to link against. This works well for the libLLVM*
>>>>> libraries, but how do I implement similar find stuff for clang
>>>> AFAIK, there is no such feature for Clang.
>> I noticed that the following files are modified even though I'm compiling
>> outside the source tree (using cmake):
>>> # modified: src/utils/llvm-build/llvmbuild/__init__.pyc
>>> # modified: src/utils/llvm-build/llvmbuild/componentinfo.pyc
>>> # modified: src/utils/llvm-build/llvmbuild/configutil.pyc
>>> # modified: src/utils/llvm-build/llvmbuild/main.pyc
>>> # modified: src/utils/llvm-build/llvmbuild/util.pyc
>> Does anybody know why the sources are being modified?
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
More information about the llvm-dev