Hi, John: We suggest here 2 changes to petalinux-copy-autoconfig script (both done by Balajee Premraj): 1 Petalinux-copy-autoconfig - Change 1 1.1 Description The script when executed from a directory other than the EDK Project directory, the script doesn't work. 1.2 Explanation Petalinux-copy-autoconfig refers to the MSS file and XMP project files and extracts certain information's like the CPU version, OS VERSION etc. By default the script expects to be executed only from the current EDK Project path. As a result when we try to execute the script from a different directory it fails to get executed. Yet it can be convenient if one runs this script as part of bigger building script. 1.3 Fix We added the variable called PROJECT_PATH and appended it before reading MSS files, So that the EDK Project files present from different paths can be accessed. Also removed certain conditional error checks which ensures the script being executed from the EDK project directory. In general the Hardware projects are placed under the directory hardware/<PRODUCTNAME> 2 Petalinux-copy-autoconfig -Change 2 2.1 Description The script after executed, the autoconf.h file in kernel has '\r' symbols inside brackets which makes gcc fall. 2.2 Explanation The script copies the EDK Generated auto-config.in file to the software directory /software/petalinux-dist/linux-2.4.x/arch/microblaze/platform/<vendor-pr oduct>/ Since the original source file "auto-config.in" was created by the EDK tool on the windows environment (this is the way we work and may be some other people as well), this file is in the dos format. As a result, the '\r' is appended to the end of the lines. auto-config.in is an input file to generate autoconf.h , while creating the autoconf.h it appends the '\r' as well. 2.3 Fix We remove the '\r' files using the sed command. Thanks, Leonid.
Attachment:
petalinux-copy-autoconfig.patch
Description: petalinux-copy-autoconfig.patch