Calling `bear -- emmake make` from makefile has different output than without the makefile about bear HOT 3 CLOSED

Hey @lesleyrs , thanks for the report.

In order to help, could you give more context? I am not familiar with the emmake and emcc tools. Could you send a link to a getting started page? Or just highlight how they works? And what you want to achieve? Maybe give an example of a Makefile and what output you would like to see?

from bear.

Sure, I did some more digging and actually found a hack that works! But I still don't fully understand the problem. I have a conditional in my makefile that checks which compiler is being used and ignores the path besides the name because emmake (which is a make wrapper that sets up the variables) sets the full path to emcc. If I set CC=emcc instead of using bear with the "full path/emcc" it works!

I made a simplified example of my makefile that has the same behavior: https://github.com/lesleyrs/emscripten-issue

Compiling with bear -- emmake make emmake make db CC=emcc make db CC=emcc all work, but emmake make db doesn't which was my intention. You can tell it doesn't work because it has 2 argument arrays, one for emcc and one for clang. The emcc one stops clangd lsp from activating for emscripten related stuff, in a succesful db it only shows clang.

You can uncomment the line in makefile to make emmake make db work as intended, but of course that stops it from using the full path. I don't know why changing the path directly to emcc makes it work though...

emscripten + raylib resources here for building to wasm:
https://emscripten.org/docs/getting_started/downloads.html
https://github.com/raysan5/raylib/wiki/Working-for-Web-(HTML5)

from bear.

Closing this as it's not really an issue anymore with the workaround.

from bear.