[lldb-dev] Conditionally adding sources to the build
Pavel Labath via lldb-dev
lldb-dev at lists.llvm.org
Mon Dec 5 02:16:42 PST 2016
Hi,
I am not aware of anyone ever trying that. In theory it should work if you
copy the build and source folders to the other machine and run dotest.py
with the right arguments there, but I guess that is not what you meant by
"easy". The thing that I would try in this situation is to set it up so
that the build actually runs on the target device, but then use some distcc
tricks to offload the compilation to a more powerful machine. I am not sure
how easy would that be to setup though...
pl
On 2 December 2016 at 23:15, Dmitry Mikulin <dmitrym at juniper.net> wrote:
> I have a slightly unrelated question: is there an easy way to cross-build,
> say, an ARM lldb, and run native tests on an ARM board same as what
> check-lldb does? The lldb test page only talks about running remote tests.
> No info on cross testing.
>
> Thanks!
>
>
>
> On Dec 2, 2016, at 2:29 AM, Pavel Labath <labath at google.com> wrote:
>
> I am glad to see freebsd is making progress on this front. If you need any
> help with understanding how lldb-server works, feel free to shoot me a
> question.
>
> pl
>
> On 1 December 2016 at 23:00, Dmitry Mikulin <dmitrym at juniper.net> wrote:
>
>> Thanks for the suggestions.
>> I’m working on native support for FreeBSD lldb-server, and wanted to have
>> an option to build it both ways until it’s stable enough to replace current
>> implementation. I’ll have it in a separate directory.
>>
>>
>> On Dec 1, 2016, at 2:55 AM, Pavel Labath <labath at google.com> wrote:
>>
>> The way we have done this with Linux native register contexts was to
>> notionally leave the files in the build, but completely #ifdef out their
>> contents (see NativeRegisterConextLinux_arm.cpp).
>> It's not very nice, but I think it's better than having six subfolders,
>> each with a single cpp file. If you'll need to group more than one file
>> this way, then maybe a subfolder would make more sense though.
>>
>> pl
>>
>> On 1 December 2016 at 00:30, Zachary Turner via lldb-dev <
>> lldb-dev at lists.llvm.org> wrote:
>>
>>> Unfortunately you will need to separate them at the directory levels.
>>>
>>> On Wed, Nov 30, 2016 at 4:29 PM Dmitry Mikulin via lldb-dev <
>>> lldb-dev at lists.llvm.org> wrote:
>>>
>>>> Hi,
>>>>
>>>> I’m trying to conditionally add source files to the lldb build based on
>>>> a cmake configure time variable. I get the following type of errors for all
>>>> sources not included in the build:
>>>>
>>>> CMake Error at cmake/modules/LLVMProcessSources.cmake:83 (message):
>>>> Found unknown source file
>>>> /homes/dmitrym/buildspace/llvm-tot/llvm/tools/lldb/source/Pl
>>>> ugins/Process/FreeBSD/FreeBSDThread.cpp
>>>>
>>>> Please update
>>>> /homes/dmitrym/buildspace/llvm-tot/llvm/tools/lldb/source/Pl
>>>> ugins/Process/FreeBSD/CMakeLists.txt
>>>>
>>>> Is there a way to work around/fix it or do I need to separate the files
>>>> at the directory level?
>>>>
>>>> Thanks.
>>>> Dmitry.
>>>>
>>>> _______________________________________________
>>>> lldb-dev mailing list
>>>> lldb-dev at lists.llvm.org
>>>> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>>>>
>>>
>>> _______________________________________________
>>> lldb-dev mailing list
>>> lldb-dev at lists.llvm.org
>>> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>>>
>>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20161205/8e093ccb/attachment.html>
More information about the lldb-dev
mailing list