Using the makefile the following error is encountered
C:\Dev\FreeRTOS\Demo\Cygnal>make
MAKE Version 5.2 Copyright (c) 1987, 2000 Borland
Fatal: ‘…\…\Source\tasks.rel’ does not exist - don’t know how to make it
snapshot SDCC NOV/2004 was used and the project files and directories were installed in C:\Dev\FreeRTOS
That is very odd. If you type "make --v" what do you get. My output is as:
GNU Make 3.80
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
If you are using the same version I cannot see any reason why it would think the makefile was not there.
Some thoughts:
Could it be that it does not like the capital ‘M’ in Makefile. Try making it a lower case ‘m’.
Try specifiying the file to make, as in "make --makefile=Makefile" - maybe even with the path also.
Which host operating system are you using? I am using Win2k.
Results:
1) make -v
C:\Dev\FreeRTOS\Demo\Cygnal>make -v
GNU Make version 3.75, by Richard Stallman and Roland McGrath.
Copyright (C) 1988, 89, 90, 91, 92, 93, 94, 95, 96
Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Report bugs to <bug-gnu-utils@prep.ai.mit.edu>.
C:\Dev\FreeRTOS\Demo\Cygnal>
2)Tried changing Makefile to makefile.
No differrence
Hmm. Still strange. It seems to be taking Sourcetasks.c as a single file, rather than Source\Tasks.c. XP should not care which way round the slashes go.
I will not be able to test on an XP machine until tomorrow unfortunately as I don’t have one available here.
What happens if you run the command line manually rather than through make?
If this builds the single file ok then the finger still points at make. If this has the same problem then make is probably ok now. If this works then maybe you could convert the makefile into a batch file until I have a change to try it under XP.
Each port requires a particular device and a particular compiler. As each compiler uses memory in a different way and generates different code sequences it is unlikely that you would be able to use the IAR compiler without some porting effort.