google / bazel-to-cmake Goto Github PK

unable to convert bazel to cmake in apollo source code:https://github.com/ApolloAuto/apollo
it has both files BUILD and Workspace.
user@B45:~/apollo$ python /home/user/bazel-to-cmake/bazel_to_cmake.py CMakeLists.txt
Traceback (most recent call last):
File "/home/user/bazel-to-cmake/bazel_to_cmake.py", line 266, in
execfile("WORKSPACE", GetDict(WorkspaceFileFunctions(converter)))
NameError: name 'execfile' is not defined

Yes，I want it, got any plan?

NameError: name 'execfile' is not defined

Python 2 had the builtin function execfile, which was removed in Python 3.0.

Hi, i do have a project layout like this:
~/prj/WORKSPACE
~/prj/a/b/BUILD
~/prj/a/b/main.cpp
cmake_to_bazel is not able to provide a valid CMakeLists.txt because it assumes a BUILD file in ~/prj/
And even if there was a BUILD file in ~/prj/, the other files deep down the directory are not accessed at all, i.e. only one single CMakeLists.txt is created

This tool does not use Bazel implementation at all. Instead it takes advantage of the fact that Bazel input files are a subset of Python by using Python to evaluate them.

Have you considered using a real Starlark interpreter? For example, https://github.com/google/starlark-go is easy to embed.

hi, I run the command and got the errors blew.

execfile("WORKSPACE", GetDict(WorkspaceFileFunctions(converter)))

File "WORKSPACE", line 81, in
new_local_repository(
NameError: name 'new_local_repository' is not defined

Hi, whoever is working on this, did you consider using bazel query results to build up the cmake files? Similar to this approach: https://github.com/lizan/bazel-cmakelists/
I think the advantage would be, that you'd have a real representation of how the project is supposed to look like, instead of parsing files directly?