OpenWRT Build System for CentOS 7: Difference between revisions

Line 193:

<br />

== Notes from 9.10.2020 ==

==Notes from 9.10.2020==

When using the ./scripts/feeds update -a command, the First Top Tip is: The Directory defined in feeds.conf or feeds.conf.default with the src-link command / directive that contains the path to a feed must have a directory, subdirectory structure, Makefile.

If the Makefile file for a project named helloworld is located in /WhatEverPath/examples/helloworld/Makefile, the the following applies in the feeds.conf or feeds.conf.default file;

* Nope, won't work: src-link examples /WhatEverPath/examples/helloworld

*Nope, won't work: src-link examples /WhatEverPath/examples/helloworld

* This will work: examples /WhatEverPath/examples

*This will work: examples /WhatEverPath/examples

* Oh, and no trailing / (forward slash)

*Oh, and no trailing / (forward slash)

* If it isn't done correctly, this unhelpful error message will occur: ... *** target pattern contains no `%'. Stop.

*If it isn't done correctly, this unhelpful error message will occur: ... *** target pattern contains no `%'. Stop.

** For the above error, some sites note an issue with leading or trailing spaces on any line (does not include spaces after a command / directive) and recommending TABs instead. But after testing with leading and trailing spaces in an attempt to produce the error, it appears that the OpenWRT developers corrected this issue within their script (IE, most errors due to spaces seem to have occurred in an era where only MAKE commands were used prior to the existence of the ./scripts/feeds script.

**For the above error, some sites note an issue with leading or trailing spaces on any line (does not include spaces after a command / directive) and recommending TABs instead. But after testing with leading and trailing spaces in an attempt to produce the error, it appears that the OpenWRT developers corrected this issue within their script (IE, most errors due to spaces seem to have occurred in an era where only MAKE commands were used prior to the existence of the ./scripts/feeds script.

*Also in the feeds.conf or feeds.conf.default file do NOT use a ~ (tilde) in the path (like for a home directory) as it will not allow the ./scripts/feeds update -a command to work properly (plus it won't produce an error message, it just produces a zero byte index file.)

*And be sure to run the ./scripts/feeds update -a and ./scripts/feeds/ install -a command (or instead of -a for ALL, target a specific package

----~~<br~~ />

----How do the variables in scripts from OpenWRT get their default values? (https://openwrt.org/docs/guide-developer/packages as noted here, they can be defined in the Makefile file)

* ~openwrtSDK/feeds/WhatEverDirectory/MakeFile: Modifications here will be reflected in "make ~~Menuconfig~~"

''pwd'' is a Linux command to get the current directory.

* The symbolic links originally used in earlier examples are incomplete. There is NOT a directory to directory equivalent file / directory for symbolic links in ~/openwrtSDK/package/feeds. IE, the subfolders of all of the symbolic links in ~/openwrtSDK/package/feeds seem to be in a flat structure, where as the directories / files they point to are in a hierarchical structure.

* The README files in the various ~/openWRT/feeds directories make reference to the feeds.conf file which seems to now be titled feeds.conf.default. Documentation seems to indicate either one of these file names will work, although the one ending in .default seems to trump feeds.conf if both are present.

* In order for a new item to show up in make ~~Menuconfig~~: Add it to /

<br />

** NO ./scripts/feeds/update needs to be run, if: something is manually added as a symbolic link.

** OR

*~openwrtSDK/feeds/WhatEverDirectory/MakeFile: Modifications here will be reflected in "make menuconfig"

** run the ./scripts/feeds install -a command (obviously this is a better choice)

*The symbolic links originally used in earlier examples are incomplete. There is NOT a directory to directory equivalent file / directory for symbolic links in ~/openwrtSDK/package/feeds. IE, the subfolders of all of the symbolic links in ~/openwrtSDK/package/feeds seem to be in a flat structure, where as the directories / files they point to are in a hierarchical structure.

* Error Logs are located: ~/openwrtSDK/logs/package/feeds/

*The README files in the various ~/openWRT/feeds directories make reference to the feeds.conf file which seems to now be titled feeds.conf.default. Documentation seems to indicate either one of these file names will work, although the one ending in .default seems to trump feeds.conf if both are present.

* If duplicating a directory, start by changing the define Package/WhatEverName that contains: SECTION, TITLE, etc. and every other reference to the same WhatEverName

*In order for a new item to show up in make menuconfig: Add it to /

** It was noticed at minimum, the last line: $(eval $(call BuildPackage,WhatEverName)) had to be changed too.

**NO ./scripts/feeds/update needs to be run, if: something is manually added as a symbolic link.

**OR

**run the ./scripts/feeds install -a command (obviously this is a better choice)

*Error Logs are located: ~/openwrtSDK/logs/package/feeds/

*If duplicating a directory, start by changing the define Package/WhatEverName that contains: SECTION, TITLE, etc. and every other reference to the same WhatEverName

**It was noticed at minimum, the last line: $(eval $(call BuildPackage,WhatEverName)) had to be changed too.

@@ Line 193: / Line 193: @@
 <br />
-== Notes from 9.10.2020 ==
+==Notes from 9.10.2020==
 When using the ./scripts/feeds update -a command, the First Top Tip is: The Directory defined in feeds.conf or feeds.conf.default with the src-link command / directive that contains the path to a feed must have a directory, subdirectory structure, Makefile.
 If the Makefile file for a project named helloworld is located in /WhatEverPath/examples/helloworld/Makefile, the the following applies in the feeds.conf or feeds.conf.default file;
-* Nope, won't work: src-link examples /WhatEverPath/examples/helloworld
+*Nope, won't work: src-link examples /WhatEverPath/examples/helloworld
-* This will work: examples /WhatEverPath/examples
+*This will work: examples /WhatEverPath/examples
-* Oh, and no trailing / (forward slash)
+*Oh, and no trailing / (forward slash)
-* If it isn't done correctly, this unhelpful error message will occur: ... *** target pattern contains no `%'.  Stop.
+*If it isn't done correctly, this unhelpful error message will occur: ... *** target pattern contains no `%'.  Stop.
-** For the above error, some sites note an issue with leading or trailing spaces on any line (does not include spaces after a command / directive) and recommending TABs instead.  But after testing with leading and trailing spaces in an attempt to produce the error, it appears that the OpenWRT developers corrected this issue within their script (IE, most errors due to spaces seem to have occurred in an era where only MAKE commands were used prior to the existence of the ./scripts/feeds script.
+**For the above error, some sites note an issue with leading or trailing spaces on any line (does not include spaces after a command / directive) and recommending TABs instead.  But after testing with leading and trailing spaces in an attempt to produce the error, it appears that the OpenWRT developers corrected this issue within their script (IE, most errors due to spaces seem to have occurred in an era where only MAKE commands were used prior to the existence of the ./scripts/feeds script.
+*Also in the feeds.conf or feeds.conf.default file do NOT use a ~ (tilde) in the path (like for a home directory) as it will not allow the ./scripts/feeds update -a command to work properly (plus it won't produce an error message, it just produces a zero byte index file.)
+*And be sure to run the ./scripts/feeds update -a and ./scripts/feeds/ install -a command (or instead of -a for ALL, target a specific package
-----<br />
+----How do the variables in scripts from OpenWRT get their default values? (https://openwrt.org/docs/guide-developer/packages as noted here, they can be defined in the Makefile file)
-* ~openwrtSDK/feeds/WhatEverDirectory/MakeFile: Modifications here will be reflected in "make Menuconfig"
+''pwd'' is a Linux command to get the current directory.
-* The symbolic links originally used in earlier examples are incomplete.  There is NOT a directory to directory equivalent file / directory for symbolic links in ~/openwrtSDK/package/feeds.  IE, the subfolders of all of the symbolic links in ~/openwrtSDK/package/feeds seem to be in a flat structure, where as the directories / files they point to are in a hierarchical structure.
-* The README files in the various ~/openWRT/feeds directories make reference to the feeds.conf file which seems to now be titled feeds.conf.default.  Documentation seems to indicate either one of these file names will work, although the one ending in .default seems to trump feeds.conf if both are present.
-* In order for a new item to show up in make Menuconfig: Add it to /
+<br />
-** NO ./scripts/feeds/update needs to be run, if: something is manually added as a symbolic link.
-** OR
+*~openwrtSDK/feeds/WhatEverDirectory/MakeFile: Modifications here will be reflected in "make menuconfig"
-** run the ./scripts/feeds install -a command (obviously this is a better choice)
+*The symbolic links originally used in earlier examples are incomplete.  There is NOT a directory to directory equivalent file / directory for symbolic links in ~/openwrtSDK/package/feeds.  IE, the subfolders of all of the symbolic links in ~/openwrtSDK/package/feeds seem to be in a flat structure, where as the directories / files they point to are in a hierarchical structure.
-* Error Logs are located: ~/openwrtSDK/logs/package/feeds/
+*The README files in the various ~/openWRT/feeds directories make reference to the feeds.conf file which seems to now be titled feeds.conf.default.  Documentation seems to indicate either one of these file names will work, although the one ending in .default seems to trump feeds.conf if both are present.
-* If duplicating a directory, start by changing the define Package/WhatEverName that contains: SECTION, TITLE, etc. and every other reference to the same WhatEverName
+*In order for a new item to show up in make menuconfig: Add it to /
-** It was noticed at minimum, the last line: $(eval $(call BuildPackage,WhatEverName)) had to be changed too.
+**NO ./scripts/feeds/update needs to be run, if: something is manually added as a symbolic link.
+**OR
+**run the ./scripts/feeds install -a command (obviously this is a better choice)
+*Error Logs are located: ~/openwrtSDK/logs/package/feeds/
+*If duplicating a directory, start by changing the define Package/WhatEverName that contains: SECTION, TITLE, etc. and every other reference to the same WhatEverName
+**It was noticed at minimum, the last line: $(eval $(call BuildPackage,WhatEverName)) had to be changed too.