Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No rule to make target `flightgear_tf-g2 #43

Open
kaklik opened this issue Jul 10, 2023 · 0 comments
Open

No rule to make target `flightgear_tf-g2 #43

kaklik opened this issue Jul 10, 2023 · 0 comments
Labels

Comments

@kaklik
Copy link
Member

kaklik commented Jul 10, 2023

Running the make px4_sitl_nolockstep flightgear_tf-g2 or similar px4_sitl_nolockstep targets like flightgear_tf-g1 or flightgear_tf-rascal results in the following error in case the fgfs binary is not found by cmake:

PX4-Autopilot> make px4_sitl_nolockstep flightgear_tf-g2
make[1]: * No rule to make target `flightgear_tf-g2'.  Stop.
make: * [px4_sitl_nolockstep] Error 2

Issue is coused by uncath failure of find_program(FGFS_PATH "fgfs") in the file /src/modules/simulation/simulator_mavlink/sitl_targets_flightgear.cmake

Expected behavior

I suggest that cmake use the system variable from PX4-FlightGear-Bridge FG_BINARY (if it exists) and when it doesn't, use the current search function find_program(FGFS_PATH "fgfs"). If that doesn't work either, cmake should end with a clear error, not pretend that it's OK, and at the same time not prepare the target.

Temporary workaround

use the alias to FlightGear starting script (limited use)

alias fgfs=/home/[user]/flightgear/dnc-managed/run_fgfs.sh
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant