On 06/04/2013 03:16 PM, Gedare Bloom wrote:
On Tue, Jun 4, 2013 at 4:08 AM, Ralf Kirchner
<[email protected]> wrote:
Hi Cynthia,
Please see my replies below.
Kind Regards
Ralf Kirchner
Am 03.06.2013 16:55, schrieb Rempel, Cynthia:
Could a rule in the Makefile.am be added to generate
testsuites/fstests/fsdosfsname01/image_bin_le_multibyte.h and then not include
the file in the repo?
If the file is needed for comparing a new build vs. the working build (for
testing purposed), then it makes sense to keep image_bin_le_multibyte.h...
The problem is that from within the test (running on a simulator like
SIS) we do not have access to the file system of the PC on which the
test gets executed. This is why the current handling is:
If PRINT_DISK_IMAGE != 0, print the disk images to the console and from
there copy them manually into the header files.
It might be possible to activate this from the Makefile but due to the
missing file system access it would still remain a semi-automatic
process. This is why I did not take the time to investigate further into
activating this from the Makefile.
You can also pack the filesystem into a tarfs / imfs tar file that is
compiled into the application/test and use untar from memory to unpack
it. (For example, [1] has a script generate_fs.sh that creates a tar
image (as a byte array) from the files subdirectory, and then the
Makefile includes the tar image in the compilation.) I played around
with Makefile rules to do this, but I don't recall being happy with
any approach.
No, we need a binary image of a FAT file system for verification.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : [email protected]
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
rtems-devel mailing list
[email protected]
http://www.rtems.org/mailman/listinfo/rtems-devel
