Develop eepp applications with ecode

[bxijt4]

I need code completion by clangd. This requires compile_commands.json. But premake can't generate this file for me. I don't want to use Bear. I'm on Windows 7 (an outdated Windows that support has been dropped by the MSYS2 project). Add more tools to the stack will only causing more problems.

My setup is simple: llvm-mingw (includes clangd) + eepp + ecode. No other external dependencies. It seems you need to add a CMakeLists.txt for this example so I could use it as the foundation for my projects:

https://github.com/SpartanJ/eepp/tree/develop/src/examples/empty_window

CMake is the most portable and the easiest to get on Windows that can generate compile_commands.json.

p/s: I'm stuck with cmake 3.28.6 as it is the last version supports Windows 7.

[SpartanJ]

Casually last night I was exposing the export compile commands functionality in eepp repository (commited here). Premake5 does support this but you need to install a module, now the module will be integrated in eepp, so you only need to run:
premake5 export-compile-commands and it will generate the compile_commands.json file in the root directory of the project.
Premake5 is quite flexible, there are modules for generating cmake and ninja projects. Here there is a list of some of the modules available.

If you need to add your own projects by extending the premake5 configuration of eepp it's really easy since i did that to easily compile eeiv. premake5.lua file will also include (if exists) an external_projects.lua file to generate external project applications (like what you're requiring).

For example my local external_projects.lua looks like:

	project "eeiv"
		kind "WindowedApp"
		language "C++"
		files { "../eeiv/src/*.cpp" }
		build_link_configuration( "eeiv", true )

This will link the project against eepp, build the project in the and bin folder. To build that particular project you just need to make the name of the project, for example:
mingw32-make -C make\\windows eeiv

And that's all you need.

[bxijt4]

https://github.com/tarruda/premake-export-compile-commands

This project has not been updated for 9 years. And clangd looks for a file named compile_commands.json. This file is expected to be in the root source tree or in the build directory. It will not see and load the json files in compile_commands directory.

I found this project on the Premake modules page:

https://github.com/MattBystrin/premake-ecc

Maybe it's a better candidate.

[2vidb51h]

@Jarod42 has a fork with some improvements regarding this.

[bxijt4]

In his fork, he renamed the json files to the correct name, compile_commands.json, and also changed the locations of them. But clangd still can't find the compile_commands.json file. As I said, clangd expects this file to be in the root source tree or in the build directory.

[Jarod42]

From https://clangd.llvm.org/installation.html

If your build directory is $SRC or $SRC/build, clangd will find it. Otherwise, symlink or copy it to $SRC, the root of your source tree.

ln -s ~/myproject-build/compile_commands.json ~/myproject/

[SpartanJ]

@bxijt4 I don't think you tried to use what comes with eepp. I forked @Jarod42 version and made a small modification: my version will just check your arch an copy the file to the root of the repository, check it here, it's only useful for eepp since it's getting the release version following the project convention.