Teo Koon Peng

The windows ci is using a ci build of ros2 which mistakenly exports local directories. ```cmake INTERFACE_INCLUDE_DIRECTORIES "${_IMPORT_PREFIX}/include;C:/ci/ws/install/include" ``` This causes `cpp_nodes` to fail, I tried with a release build...

I went back a few weeks and they all have the same error https://ci.appveyor.com/project/minggangw/rclnodejs/builds/36303858 ``` CMake Error in CMakeLists.txt: Imported target "rclcpp::rclcpp" includes non-existent path "C:/ci/ws/install/include" in its INTERFACE_INCLUDE_DIRECTORIES. Possible...

made an issue https://github.com/ros2/ros2/issues/1068

It looks like the issue still isn't fixed :disappointed:

There is a bug in the current version of electron which causes rclnodejs to not work, the fix is currently scheduled in v11 beta. Also, if you are loading rclnodejs...

I haven't used electron in a while, so some of these information might be outdated. Normally the binding files are built when you install `rclnodejs`, this is done by `node-gyp`...

I am encountering this problem as well, I was able to workaround it by creating an empty `node_modules` directory before running npm install/ci.

This is my experience when working on a `rosidl_generator_nodejs`. A third party rosidl generator would probably need the following: 1. A list of all packages and their messages, services and...

@jacobperron Thanks for the useful insights! > By your description of rosidl_generator_nodejs, I'm guessing that you want to generate nodejs bindings using the output of an specific generator in a...

> AFAIU, we can't distribute binaries via the buildfarm for languages that are not part of the "core" ROS installation. Yeah, this is the main problem I see as well....