Rutger Hofman wrote:
> Charles Manning wrote:
>> On Monday 03 November 2008 14:35:08 Rutger Hofman wrote:
>>> Good evening list,
>>>
>>> I am using yaffs/direct for my project (yaffs on eCos). I adapted the
>>> Makefile in direct/, because I want it to generate a library -- right
>>> now, it generates a linked executable.
>>>
>>> The changes are:
>>>
>>> - add a target (not the default) for building a library
>>> - making a difference between the files that should belong in the
>>> library and the files that are used to build the direct/ demo executables
>>> - and some small stuff: I like to generate dependency files; I changed
>>> the symlinking of the files in direct/../ to use the files themselves,
>>> because symlinks defy dependency checking.
>>>
>>> Is yaffs interested in a patch?
>>>
>>> Rutger
>> Hello
>>
>> Please do post this to the list.
>>
>> If it is considered useful then it may be incorporated.

Here is my replacement direct/Makefile.

It depends on GNU make -- but I think the original already did that.

It has the goodies mentioned above. Dependency generation is optional: 
it is done if MAKEDEPEND is defined on the command line, or if the 
compiler name matches "*gcc" (as in my case: bfin-elf-gcc or arm-elf-gcc).

Invocation as just "make" ought to do the same thing as with the 
original. If one wants to build as a library, do "make lib". To change 
compiler name/flags etc, invoke as "make CC=<my compiler> CFLAGS="<all 
compiler flags>", including those that are mandatory for direct 
building, like -DCONFIG_YAFFS_DIRECT -DCONFIG_YAFFS_SHORT_NAMES_IN_RAM 
-DCONFIG_YAFFS_YAFFS2 and friends.

This Makefile already has a target yaffs_test, even though there is no 
file yaffs_test.c in the repository :-) .

Rutger