# Possible to build Posix blinky without configUSE\_TRACE\_FACILITY?

**URL:** <https://forums.freertos.org/t/possible-to-build-posix-blinky-without-configuse-trace-facility/19432>\
**Category:** Kernel\
**Tags:** tracealyzer, trace\
**Created:** [March 4, 2024, 1:32am UTC](https://forums.freertos.org/t/possible-to-build-posix-blinky-without-configuse-trace-facility/19432 "2024-03-04T01:32:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![PwnVerse](https://d3iykfbgfh8zhg.cloudfront.net/user_avatar/forums.freertos.org/pwnverse/32/4178_2.png) [@PwnVerse](https://forums.freertos.org/u/PwnVerse)\
**Post date:** [March 4, 2024, 1:32am UTC](https://forums.freertos.org/t/possible-to-build-posix-blinky-without-configuse-trace-facility/19432/1 "2024-03-04T01:32:56Z")

</div>

Hi, I want to compile FreeRTOS Posix Blinky without the configUSE\_TRACE\_FACILITY set, this is because I want to use the compiled object files for some dynamic instrumentation I’ve been meaning to do for one of my projects. Is there any workaround to compile blinky for Posix without configUSE\_TRACE\_FACILITY set?

---

<div class="post-metadata">

**Author:** ![aggarg](https://d3iykfbgfh8zhg.cloudfront.net/user_avatar/forums.freertos.org/aggarg/32/4245_2.png) [@aggarg](https://forums.freertos.org/u/aggarg)\
**Post date:** [March 4, 2024, 5:17am UTC](https://forums.freertos.org/t/possible-to-build-posix-blinky-without-configuse-trace-facility/19432/2 "2024-03-04T05:17:39Z")

</div>

> [@PwnVerse](#):
>
> Is there any workaround to compile blinky for Posix without configUSE\_TRACE\_FACILITY set?

It should be - do you see a problem when you do not define configUSE\_TRACE\_FACILITY ?

---

<div class="post-metadata">

**Author:** ![PwnVerse](https://d3iykfbgfh8zhg.cloudfront.net/user_avatar/forums.freertos.org/pwnverse/32/4178_2.png) [@PwnVerse](https://forums.freertos.org/u/PwnVerse)\
**Post date:** [March 4, 2024, 5:36am UTC](https://forums.freertos.org/t/possible-to-build-posix-blinky-without-configuse-trace-facility/19432/3 "2024-03-04T05:36:22Z")

</div>

Yes, when i set it to 0, compilation bails out saying RecordDataPtr is not declared. I feel like Posix port is tightly coupled with the tracer module, it should be made independent of it. As a naive workaround, I removed all trace specific files from the Makefile, commented out the tracer dump code from the main and somehow got it to work for my needs, I would truly appreciate if there’s a cleaner and better way of getting around the tracer module.

---

<div class="post-metadata">

**Author:** ![karahulx](https://d3iykfbgfh8zhg.cloudfront.net/user_avatar/forums.freertos.org/karahulx/32/4893_2.png) [@karahulx](https://forums.freertos.org/u/karahulx)\
**Post date:** [March 4, 2024, 9:19am UTC](https://forums.freertos.org/t/possible-to-build-posix-blinky-without-configuse-trace-facility/19432/4 "2024-03-04T09:19:19Z")

</div>

> [@PwnVerse](#):
>
> I feel like Posix port is tightly coupled with the tracer module

That is not correct as the POSIX port does not have a dependency on tracer. It is the POSIX demo that demonstrates the use of tracer.

> [@PwnVerse](#):
>
> As a naive workaround, I removed all trace specific files from the Makefile, commented out the tracer dump code from the main and somehow got it to work for my needs

That is actually not naive but the right thing to do - update the demo code as per your needs.

> [@PwnVerse](#):
>
> I would truly appreciate if there’s a cleaner and better way of getting around the tracer module.

I have added an option `NO_TRACING` to allow using the demo without tracing functionality in [this PR](https://github.com/FreeRTOS/FreeRTOS/pull/1189).

---

<div class="post-metadata">

**Author:** ![PwnVerse](https://d3iykfbgfh8zhg.cloudfront.net/user_avatar/forums.freertos.org/pwnverse/32/4178_2.png) [@PwnVerse](https://forums.freertos.org/u/PwnVerse)\
**Post date:** [March 4, 2024, 1:10pm UTC](https://forums.freertos.org/t/possible-to-build-posix-blinky-without-configuse-trace-facility/19432/5 "2024-03-04T13:10:29Z")

</div>

Hi Rahul,

Thanks alot for the PR, this addresses the issue I was facing.
