[lttng-dev] Status of MinGW support for babeltrace (either 1.x or 2.x)

[Philippe Proulx]

On Tue, Aug 15, 2017 at 2:25 PM, Jonah Graham <jonah at kichwacoders.com> wrote:
>
>
> On 15 Aug 2017 19:10, "Philippe Proulx" <eeppeliteloop at gmail.com> wrote:
>
> On Tue, Aug 15, 2017 at 1:09 PM, Jonah Graham <jonah at kichwacoders.com>
> wrote:
>> Thank you both for the info. It looks like our timing is very good. I will
>> have a look at the staging branch too.
>>
>> Our interest is in writing ctf files from our custom tools and then
>> analysing the traces in tracecompass. We were trying to decide between
>> libbabeltrace, barectf or spinning our own. With your goal of supporting
>> mingw, it seems that libbabeltrace is the best idea.
>
> You want to actually trace, that is, produce CTF events from your
> application, or convert an existing trace format to CTF?
>
>
> We want to trace. We're producing a variety of plain text formats at the
> moment, and are losing information and scalability. They were designed to be
> human readable so they don't fit back into tracecompass that well.

Why can't you use LTTng?

The disclaimer with CTF writer (part of libbabeltrace) is that it is not
super fit for tracing purposes: its role is to help in the conversion
from a trace written in some non-CTF format (for example, your text
files) to CTF.

As for barectf, the project's target is bare metal embedded systems, and
you need to write your own barectf platform for each custom environment.

Phil

>
>
> Phil
>
>>
>> We'll do what we can to provide patches.
>>
>> Thanks,
>> Jonah
>>
>> On 15 Aug 2017 17:39, "Philippe Proulx" <eeppeliteloop at gmail.com> wrote:
>>>
>>> On Tue, Aug 15, 2017 at 12:12 PM, Jonah Graham <jonah at kichwacoders.com>
>>> wrote:
>>> >
>>> > Hello,
>>> >
>>> > Over the years I have seen some discussions and patches about getting
>>> > full MinGW support for babeltrace. I am interested in if someone can
>>> > provide an overview of the current state of MinGW.
>>> >
>>> > I have tried to build 1.5.3 and (probably as expected) there are
>>> > numerous compile issues (e.g. sys/mman.h)
>>> >
>>> > I have gotten further with current master (my primary interest is
>>> > libbabeltrace so the issues I have with cli/babeltrace.c and
>>> > tests/test_ctf_writer.c don't concern me too much yet). However when I
>>> > try to run a simple example (that works on Linux) it fails on
>>> > bt_ctf_stream_flush. I will debug further to identify the problem.
>>> > However If someone does have a mingw port working well any guidance on
>>> > building would be much appreciated.
>>>
>>> MinGW support is on its way for the Babeltrace 2.0 release, but I'm
>>> curious as to why your primary interest is libbabeltrace? Is it for CTF
>>> writer or for the trace reading API?
>>>
>>> Phil
>>>
>>> >
>>> > Thanks
>>> > Jonah
>>> >
>>> >
>>> > ~~~
>>> > Jonah Graham
>>> > Kichwa Coders Ltd.
>>> > www.kichwacoders.com
>>> > _______________________________________________
>>> > lttng-dev mailing list
>>> > lttng-dev at lists.lttng.org
>>> > https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>
>