# Can I enable verbosity in PX4 make output? **URL:** \ **Category:** PX4 Autopilot\ **Created:** [December 3, 2021, 3:48pm UTC](https://discuss.px4.io/t/can-i-enable-verbosity-in-px4-make-output/25319 "2021-12-03T15:48:10Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![edsut](https://discuss.px4.io/user_avatar/discuss.px4.io/edsut/32/9665_2.png) [@edsut](https://discuss.px4.io/u/edsut)\ **Post date:** [December 3, 2021, 3:48pm UTC](https://discuss.px4.io/t/can-i-enable-verbosity-in-px4-make-output/25319/1 "2021-12-03T15:48:10Z")
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, ---
**Author:** ![jimdgit](https://discuss.px4.io/user_avatar/discuss.px4.io/jimdgit/32/6860_2.png) [@jimdgit](https://discuss.px4.io/u/jimdgit)\ **Post date:** [December 3, 2021, 4:30pm UTC](https://discuss.px4.io/t/can-i-enable-verbosity-in-px4-make-output/25319/2 "2021-12-03T16:30:27Z")
You might get a better answer sooner on github. There is a specific issue category for questions. ![image](https://discuss.px4.io/uploads/default/original/2X/b/b42e4073ef08428201d29edcb642d77d6e189e1b.png) ---
**Author:** ![edsut](https://discuss.px4.io/user_avatar/discuss.px4.io/edsut/32/9665_2.png) [@edsut](https://discuss.px4.io/u/edsut)\ **Post date:** [December 3, 2021, 4:54pm UTC](https://discuss.px4.io/t/can-i-enable-verbosity-in-px4-make-output/25319/3 "2021-12-03T16:54:01Z")
Thanks, I’ve never used this. Are you talking about here: [Issues · PX4/PX4-Autopilot · GitHub](https://github.com/PX4/PX4-Autopilot/issues) ? Ed ---
**Author:** ![edsut](https://discuss.px4.io/user_avatar/discuss.px4.io/edsut/32/9665_2.png) [@edsut](https://discuss.px4.io/u/edsut)\ **Post date:** [December 3, 2021, 5:15pm UTC](https://discuss.px4.io/t/can-i-enable-verbosity-in-px4-make-output/25319/4 "2021-12-03T17:15:12Z")
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](http://discuss.px4.io/).** I’ll post there and see if I get yelled at. 🙂 ---
**Author:** ![jimdgit](https://discuss.px4.io/user_avatar/discuss.px4.io/jimdgit/32/6860_2.png) [@jimdgit](https://discuss.px4.io/u/jimdgit)\ **Post date:** [December 3, 2021, 5:48pm UTC](https://discuss.px4.io/t/can-i-enable-verbosity-in-px4-make-output/25319/5 "2021-12-03T17:48:23Z")
It’s a build question so I don’t think they will mind. Perhaps is will be a new build feature :-). ---
**Author:** ![Danduril](https://discuss.px4.io/user_avatar/discuss.px4.io/danduril/32/10295_2.png) [@Danduril](https://discuss.px4.io/u/Danduril)\ **Post date:** [December 3, 2021, 8:12pm UTC](https://discuss.px4.io/t/can-i-enable-verbosity-in-px4-make-output/25319/6 "2021-12-03T20:12:44Z")
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](https://github.com/PX4/PX4-Autopilot/blob/4e3d944f58f0d60e072641fc60b426fbcfdad8ab/platforms/nuttx/NuttX/CMakeLists.txt#L75-L90) I hope you get an answer for your general question. ---
**Author:** ![edsut](https://discuss.px4.io/user_avatar/discuss.px4.io/edsut/32/9665_2.png) [@edsut](https://discuss.px4.io/u/edsut)\ **Post date:** [December 3, 2021, 11:36pm UTC](https://discuss.px4.io/t/can-i-enable-verbosity-in-px4-make-output/25319/7 "2021-12-03T23:36:49Z")
> 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](https://github.com/PX4/PX4-Autopilot/blob/4e3d944f58f0d60e072641fc60b426fbcfdad8ab/platforms/nuttx/NuttX/CMakeLists.txt#L75-L90) Thanks, I’ll have to dig into that. Shamefully I’m not much of a cmake expert (or ninja for that matter). ☹ If I learn anything from the github question, I’ll post it here for reference. ---
**Author:** ![Danduril](https://discuss.px4.io/user_avatar/discuss.px4.io/danduril/32/10295_2.png) [@Danduril](https://discuss.px4.io/u/Danduril)\ **Post date:** [December 4, 2021, 2:06am UTC](https://discuss.px4.io/t/can-i-enable-verbosity-in-px4-make-output/25319/8 "2021-12-04T02:06:57Z")
Well, cmake is so so you don’t have to know anything about ninja, except to set your `makeprg` alias to it. Good luck! ---
**Author:** ![edsut](https://discuss.px4.io/user_avatar/discuss.px4.io/edsut/32/9665_2.png) [@edsut](https://discuss.px4.io/u/edsut)\ **Post date:** [December 6, 2021, 11:32pm UTC](https://discuss.px4.io/t/can-i-enable-verbosity-in-px4-make-output/25319/9 "2021-12-06T23:32:18Z")
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). ---
**Author:** ![edsut](https://discuss.px4.io/user_avatar/discuss.px4.io/edsut/32/9665_2.png) [@edsut](https://discuss.px4.io/u/edsut)\ **Post date:** [December 10, 2021, 8:02pm UTC](https://discuss.px4.io/t/can-i-enable-verbosity-in-px4-make-output/25319/10 "2021-12-10T20:02:41Z")
Replying to my own question just in case someone else may benefit… **dagar** posted some good information here: > > > I've posted questions to the forum, figured I'd take a shot here... > I'm new to …PX4, attempting a port to a very crude Teensy4.1 based flight controller hack I am working on. > I'm trying to understand how everything is built (for example builtin\_list.\[ch\] and the rcS file). Is > there any way to enable more trace at "make" time? I've been using the following make command: > \*\*export VERBOSE=1; make V=1 nxp\_teensyhack\_default 2\>&1 | tee make.out\*\* > but that doesn't do much more than show me all the compilation lines. > I also added \*\*@$(eval CMAKE\_ARGS += -DCMAKE\_VERBOSE\_MAKEFILE:BOOL=ON)\*\* and forced \*\*PX4\_MAKE\_ARGS := -v\*\* > in the Makefile but that didn't seem to help. > Any docs or suggestions? on the general issue of build verbosity.