build-from-scratch: various cleanups#206
Conversation
|
@lgirdwood unlike in |
| git clone https://github.com/thesofproject/crosstool-ng | ||
| cd crosstool-ng | ||
| cd ../crosstool-ng | ||
| git checkout sof-gcc8.1 |
There was a problem hiding this comment.
we are in gcc9x now
https://github.com/thesofproject/crosstool-ng/tree/sof-gcc9x
@lgirdwood the Docker image is still using gcc8.1 branch like here, do we need to make the update?
There was a problem hiding this comment.
As this PR is already very large, I want to draw the following line: fixes but no "upgrade". These can be tested and done in a later PR.
There was a problem hiding this comment.
Is there any way to "inline" or link (better) original scripts from the sof repo, in case the content is duplicated to reduce further maintenance of the copy?
There was a problem hiding this comment.
@mmaka1 I can add http:// links on the script names mentioned here, that's a good idea thanks. On the other hand I don't understand what duplication you're referring to, example?
There was a problem hiding this comment.
@mmaka1 I tried https://www.sphinx-doc.org/en/master/usage/extensions/extlinks.html and it Just Worked, pretty cool. It doesn't work inside .. code-block:: but the texts before can be rephrased to add the links. I can do this in a later PR.
There was a problem hiding this comment.
@mmaka1 I tried https://www.sphinx-doc.org/en/master/usage/extensions/extlinks.html and it Just Worked, pretty cool. It doesn't work inside .. code-block:: but the texts before can be rephrased to add the links. I can do this in a later PR.
Submitted in PR #213
| make help # lists all available targets | ||
| make baytrail_defconfig | ||
| make bin -j4 | ||
| make bin -j4 VERBOSE=1 |
There was a problem hiding this comment.
can we make the verbose to be optional?
There was a problem hiding this comment.
This just an example, so anyone can leave it out.
On the other hand, someone not familiar with cmake would not be able to guess it.
See commit message.
| git clone https://github.com/thesofproject/crosstool-ng | ||
| cd crosstool-ng | ||
| cd ../crosstool-ng | ||
| git checkout sof-gcc8.1 |
There was a problem hiding this comment.
As this PR is already very large, I want to draw the following line: fixes but no "upgrade". These can be tested and done in a later PR.
| make help # lists all available targets | ||
| make baytrail_defconfig | ||
| make bin -j4 | ||
| make bin -j4 VERBOSE=1 |
There was a problem hiding this comment.
This just an example, so anyone can leave it out.
On the other hand, someone not familiar with cmake would not be able to guess it.
See commit message.
Nope, no one ever got around to it, you could add a code owners here to make this easier ? |
I can if someone tells me what its content should be (which may take longer than just doing it?)
I've never been a github admin but I didn't expect a CODEOWNERS file to help with that, seemed like a permissions issue rather. |
|
@marc-hb permissions updated. |
ffe8fd2 to
4dc28d0
Compare
While I thoroughly tested every change I still need people to review the style :-) |
| cmake .. | ||
| make -j4 | ||
| mkdir build_tools | ||
| cmake -B build_tools |
There was a problem hiding this comment.
We shouldn't use -B of cmake's cli, because it's not in our minimum supported version (3.10).
There was a problem hiding this comment.
Instead of replacing, I added -B as an example with a 3.13 version caveat. 3.13 is 1+ year old now and -B is very convenient so worth knowing.
4dc28d0 to
8ded658
Compare
8ded658 to
4db92cf
Compare
4db92cf to
72be34d
Compare
|
@deb-intel I think we are good to merge. @marc-hb can you fix the conflicts thanks. |
- Fix some typos, rephrase a number of sentences. - Explain how to fix an out of date config-* file. - Move LD_LIBRARY_PATH=alsa-lib into the ALSA section as opposed to interrupting some unrelated flow. - Rename some section headers, add some in the toolchains section. - Add numerous ``monospace`` backticks. - Add missing space '#comments' - Use VERBOSE=1 and make help in some examples - much easier to ignore or remove than to guess. - PATH is already exported (otherwise it would not work). - Replace deprecated backticks `pwd` with $(pwd). http://mywiki.wooledge.org/BashFAQ/082 - Replace `pwd`/../../etc with $XTENSA_ROOT which is shorter to type and compatible with make -C or ninja -C - Convert one example to cmake -B && make -C to show the possibility. Not done to keep this large patch somewhat reviewable in a reasonable time: address the creeping platforms duplication. Signed-off-by: Marc Herbert <marc.herbert@intel.com>
72be34d to
f062bef
Compare
Done, thanks! Rebasing and fixing conflicts is not fun and exactly why I've been resisting very good suggestions to make this PR bigger than it already is (too much). By the way there seems to be a recent increase in the number of warnings. I just found and submitted #211 to fix the missing ... was just introduced by PR #203 There seems to be a couple other warnings new since I started this PR. Apparently none because of this PR. |
|
Lets merge this now and fix the minor parts incrementally. |
I just submitted thesofproject/sof#2741 to report doxygen warnings where they happen: in |
Fix some typos, rephrase a number of sentences.
Explain how to fix an out of date config-* file.
Move LD_LIBRARY_PATH=alsa-lib into the ALSA section as opposed to
interrupting some unrelated flow.
Rename some section headers, add some in the toolchains section.
Add numerous ``monospace`` backticks.
Add missing space '#comments'
Use VERBOSE=1 and make help in some examples - much easier to ignore
or remove than to guess.
PATH is already exported (otherwise it would not work).
Replace deprecated backticks `pwd` with $(pwd).
http://mywiki.wooledge.org/BashFAQ/082
Replace `pwd`/../../etc with $XTENSA_ROOT which is shorter to type and
compatible with make -C or ninja -C
Convert one example to cmake -B && make -C to show the possibility.
Not done to keep this large patch somewhat reviewable in a
reasonable time: address the creeping platforms duplication.
Signed-off-by: Marc Herbert marc.herbert@intel.com