| Anonymous | Login | Signup for a new account | 11-10-2008 11:14 PST |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | |||||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| 0001324 | [buildroot] Documentation | tweak | always | 04-23-07 19:05 | 04-23-07 19:05 | |||||||
| Reporter | bobwired | View Status | public | |||||||||
| Assigned To | buildroot | |||||||||||
| Priority | normal | Resolution | open | |||||||||
| Status | assigned | Product Version | 0.9.27 | |||||||||
| Summary | 0001324: Adding custom package does not include the editing of buildroot/package/Config.in | |||||||||||
| Description |
The docs (http://buildroot.uclibc.org/buildroot.html) [^] for adding a new package do not mention that you need to add an entry to the buildroot/package/Config.in file. For example, to add the package foo, you might edit Config.in from ... source "package/fakeroot/Config.in" source "package/gettext/Config.in" ... to ... source "package/fakeroot/Config.in" source "package/foo/Config.in" source "package/gettext/Config.in" ... Inserting the new package in the existing Config.in file in alphabetical order. |
|||||||||||
| Additional Information | Until you figure this out, foo will never run. | |||||||||||
| Attached Files | ||||||||||||
|
|
||||||||||||
| There are no notes attached to this issue. |
Issue History |
|||
| Date Modified | Username | Field | Change |
| 04-23-07 19:05 | bobwired | New Issue | |
| 04-23-07 19:05 | bobwired | Status | new => assigned |
| 04-23-07 19:05 | bobwired | Assigned To | => buildroot |
| Copyright © 2000 - 2006 Mantis Group |