Skip to content
This repository has been archived by the owner on Mar 17, 2021. It is now read-only.

Update docs for make/config target changes #670

Merged
merged 6 commits into from
Nov 27, 2018
Merged

Conversation

hamishwillee
Copy link
Collaborator

Update for changes in PX4/PX4-Autopilot#10875

@@ -13,7 +13,7 @@ This guide is focused only on the host OS and middleware as the applications/fli
In addition to the host operating system specific configuration files described below, there are several groups of configuration files for each board located throughout the code base:
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dagar Can you please let me know correct paths for everything in this section (porting guide)

@hamishwillee
Copy link
Collaborator Author

uorb_graph.md refers to <option value='graph_px4fmu-v4.json'>FMUv4 Modules</option> - will that path for the json change?

kr/debug/profiling.md Outdated Show resolved Hide resolved
@@ -13,7 +13,7 @@ This guide is focused only on the host OS and middleware as the applications/fli
In addition to the host operating system specific configuration files described below, there are several groups of configuration files for each board located throughout the code base:
* Board startup and configuration files are located in: [src/drivers/boards](https://github.com/PX4/Firmware/tree/master/src/drivers/boards).
* This folder contains bus mappings, GPIO mappings, and the initialization code for each board.
* FMUv5 example: [src/drivers/boards/px4fmu-v5](https://github.com/PX4/Firmware/tree/master/src/drivers/boards/px4fmu-v5).
* FMUv5 example: [src/drivers/boards/px4fmu-v5](https://github.com/PX4/Firmware/tree/master/src/drivers/boards/px4fmu-v5).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

en/hardware/porting_guide.md Outdated Show resolved Hide resolved
en/hardware/porting_guide.md Outdated Show resolved Hide resolved
en/hardware/porting_guide.md Outdated Show resolved Hide resolved
en/hardware/porting_guide.md Outdated Show resolved Hide resolved
en/hardware/porting_guide.md Outdated Show resolved Hide resolved
en/hardware/porting_guide.md Outdated Show resolved Hide resolved
@dagar
Copy link
Member

dagar commented Nov 27, 2018

uorb_graph.md refers to <option value='graph_px4fmu-v4.json'>FMUv4 Modules</option> - will that path for the json change?

Yes, although I don't see that being automatically uploaded anywhere. Let's review that separately.

@hamishwillee hamishwillee merged commit 7b524f0 into master Nov 27, 2018
* (All) Board-specific files: [/boards/px4/fmu-v5](https://github.com/PX4/Firmware/tree/master/boards/px4/fmu-v5).
* Build configuration: [/boards/px4/fmu-v5/default.cmake](https://github.com/PX4/Firmware/blob/master/boards/px4/fmu-v5/default.cmake).

In addition there are several groups of configuration files for each board located throughout the code base:
* The boot file system (startup script) is located in: [ROMFS/px4fmu\_common](https://github.com/PX4/Firmware/tree/master/ROMFS/px4fmu_common)
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dagar Is this true?

@hamishwillee
Copy link
Collaborator Author

@dagar As discussed, I have merged the devguide changes and we can iterate.

HOWEVER, as a priority the porting guide needs your further review "as a whole" following this update. ie it was written assuming host OS was the main separator and config was scattered. That is no longer true and we need to a) capture that and b) make sure that other relevant information is available.

@hamishwillee hamishwillee deleted the make_changes branch November 27, 2018 04:41
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants