Can I enable verbosity in PX4 make output?

PX4 Autopilot
1

I am struggling to understand how various parts of the image are created.
Here are a few examples:

  1. How is builtin_list.[ch] created?
  2. How is the /etc/init.d/rcS file created?

Etc…

I know I can set VERBOSE=1 and also make V=1; but is there any other tricks that can be used so that I can log the output of make and then see what’s actually being done?
Right now the best I can do is:
export VERBOSE=1; make V=1 2>&1 | tee make.out
Any suggestions? Is there any documentation that gives some detail on this?
Thanks,

2

You might get a better answer sooner on github.
There is a specific issue category for questions.

image
image1297×472 41.4 KB

3

Thanks, I’ve never used this.
Are you talking about here: Issues · PX4/PX4-Autopilot · GitHub ?
Ed

4

The opening text in that “Issue: Support Questions” message box says:

We use GitHub issues only to discuss PX4 bugs and new features. For
questions about using PX4 or related components, please use PX4 Discuss.

I’ll post there and see if I get yelled at. :slight_smile:

5

It’s a build question so I don’t think they will mind.
Perhaps is will be a new build feature :-).

6

I feel your pain, but never thought to ask this question. Call me cynical, but the only accurate documentation also executes.

ROMFS/px4fmu_common/init.d[-posix] is the origin of /etc/init.d.

For built-in apps, see PX4-Autopilot/CMakeLists.txt at 4e3d944f58f0d60e072641fc60b426fbcfdad8ab · PX4/PX4-Autopilot · GitHub

I hope you get an answer for your general question.

1 Like
7

ROMFS/px4fmu_common/init.d[-posix]is the origin of/etc/init.d

Yea I saw these. I ignored them because none were the same size as what is on my target; however, I just realized that they actually do match… the one on-target just has all empty lines and comments removed. Tx!

For built-in apps, see PX4-Autopilot/CMakeLists.txt at 4e3d944f58f0d60e072641fc60b426fbcfdad8ab · PX4/PX4-Autopilot · GitHub

Thanks, I’ll have to dig into that. Shamefully I’m not much of a cmake expert (or ninja for that matter). :frowning:

If I learn anything from the github question, I’ll post it here for reference.

8

Well, cmake is so so you don’t have to know anything about ninja, except to set your makeprg alias to it.

Good luck!

1 Like
9

The code in v1.12.0’s version (I’m stuck there for now) of that CMakeLists.txt file is substantially different. In both cases though they use the variable module_libraries which isn’t defined or used anywhere else. Where does that come from?
The fundamental problem I have (aside from needing to learn cmake) is that it appears that the builtin_list.h is created from the project-specific default.cmake file; however there are builtins in my running system that are not in that file and I need to understand where they came from (particularly sercom).

10

Replying to my own question just in case someone else may benefit…
dagar posted some good information here:

on the general issue of build verbosity.

1 Like