[release/9.0] fix browser-wasm debug build

[srxqds]

Backport of #108185

[pavelsavara]

This PR adds the profiler-log component into default build (which people ship when they don't use wasm workload). I'm not sure we want to merge this.

@srxqds what's your intention here ?

[dotnet-policy-service]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

[srxqds]

This PR adds the profiler-log component into default build (which people ship when they don't use wasm workload). I'm not sure we want to merge this.

@srxqds what's your intention here ?

we build debug local, it will hit undefined symbol mono_profiler_log_init when build drive.c

I found the main branch have fixed from this pr #108185

[pavelsavara]

This PR adds the profiler-log component into default build (which people ship when they don't use wasm workload). I'm not sure we want to merge this.
@srxqds what's your intention here ?

we build debug local, it will hit undefined symbol mono_profiler_log_init when build drive.c

I found the main branch have fixed from this pr #108185

Thank you for explanation.

@lewing do you think this meets servicing bar ?

cc @maraf

[lewing]

This PR adds the profiler-log component into default build (which people ship when they don't use wasm workload). I'm not sure we want to merge this.
@srxqds what's your intention here ?

we build debug local, it will hit undefined symbol mono_profiler_log_init when build drive.c
I found the main branch have fixed from this pr #108185

Thank you for explanation.

@lewing do you think this meets servicing bar ?

cc @maraf

I think it is ok for what is effectively an infra fix for the debug build

[carlossanlop]

@pavelsavara @lewing friendly reminder that today's code complete for the Feb 2025 Release. Please merge this change by 4pm PT if you'd like it included in that release version. Otherwise, it will have to wait until next month.