[PATCH 8/9] fsdsosfsname01: Ensure endian correctness

Gedare Bloom gedare at rtems.org
Tue Jun 4 13:16:29 UTC 2013

On Tue, Jun 4, 2013 at 4:08 AM, Ralf Kirchner
<ralf.kirchner at embedded-brains.de> 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.

[1] http://code.google.com/p/rtemssparc64/source/browse/trunk/rtems/rtemscvs/testsuites/mibench/dijkstra/

More information about the devel mailing list