No Rule to Make All
I don`t know if this will help the PO, but I found out what caused *my* problem. It turns out that the problem only occurs when I add „-x c++“ (without the quotation marks, of course) in the build parameters of the C/C++ compiler (which is inserted into the makefile as CFLAGS). At this point, when I look at the makefile and the .prj file, both still have references to the old file (pmcsio4.cpp) and no mention of the new file (serial.cpp). 1. Add -I directives to your C/C++2 settings. Add a VPATH directive to your Makefile macros from the Project Macro3 tab. Rebuild all dependencies, then Build-All — =|=======================================================================================================================================================================================================================================================================================================================================================================================================================================================================|================================================================================================================================================================================================================================================================================================================================================================================================================================================================================= Two, one and one are one. » mke…@gv.net | – The Who, Bargain Same problem: Our Tornado project started crashing with the message „No rule to make the goal“. A closer look at the generated makefile shows the following lines: I`ve been trying to create a correct makefile for some time, but I still get the error „make:*** No rule to make target `all`. Stop it. I tried the makeGen.tcl script and it generated a makefile identical to my project. I suspect this is because the .prjfile file doesn`t have dependencies at all. Pressing the „Update Dependencies“ button in the Tornado IDE does not even generate a new .prj file (i.e.
the time of the file does not change). The „wpj“ is just a list of information that a TCL script reads and uses to generate the make file. The makeGen.tcl in Johan`s FAQ uses these TCL files. There are also other tornado files for command-line builds. I submitted a TSR on top and it`s quite complex to set up, but it works. The comments in the file contain statements that are not entirely correct. For example, your Make rule to create map.o expects an input file named map.c in the current directory. You said that this file is actually in the mtm_map directory, so your creation rule should be: This type of error appears several times in the makefile. Obviously, there is a nasty bug in the Makefile generator. (Tornado 2.0.2 CP4 PPC). Strict adherence to these rules has eliminated the problem in all our projects.
I wonder if anyone has tried all of the above like I did, and is still unable to overcome the „no rule“ error? My project worked well and then I did the unthinkable act of deleting some obsolete files and adding new ones. I didn`t touch the -I or VPATH configurations and my new files all fell within the original settings, so there shouldn`t have been any problems. > „wpj“ is just a list of information that a TCL script reads and> uses to generate the make file. The „makeGen.tcl“ in Johan`s FAQ uses> these TCL files. There are also other Tornado files for > command-line versions. I submitted a TSR on it and it`s quite > complex to set up, but it works. The comments in the file contain > statements that are not entirely correct. Example: „/Tornado/host/resource/tcl/app-config/Project/cmpScriptLib.tcl“> > I don`t know if these are the actual files> > I looked at. I just finished> with a modified version of makeGen.tcl to generate plush rules and> emacs ebrowse files.> > hth,> Bill Pringlemeir.> — > CESID CIDA 2600 Magazine Safe Skipjack Keller halcon PLO Rule Psix> USDOJ UOP Sears Tower RSA Supercomputer INSCOM AES Crack Yes – forget the famous tornado and create your own makefiles from those created by the tcl environment Matt Osminer wrote:> It seems that I have reached a dead end with the infamous problem „no rule to make a goal>. As any tornado victim will tell you, the solution should be pretty simple for me, I ran the make init command outside the target directory where I wanted to create the makefile.
I hope this helps someone. I don`t know if these are the actual files I reviewed. I just used a modified version of makeGen.tcl to generate plush rules and edemacs navigation files. I didn`t have this problem with previous versions of Tornado (2.0, 1.x). I don`t remember why I added the „-x c++“ (used to replace the automatic detection of gcc file types) to the build settings. The removal does not seem to affect compiler output. And I`m not an expert in makefiles, so if you notice any errors, please let me know. map.c exists in a folder called mtm_map in the current folder Personally, I wouldn`t suggest new Ubuntu/Linux users install software from the source code as it is a bit complex compared to other methods. ## dependenciessensor.o: $(PRJ_DIR)/sensor.c ethernet.h 2) I had to fix a problem in the dependencies section. Tornado generated the following in the Makefile. „www.xs4all.nl/~borkhuis/vxworks/vxw_pt1.html#1.6-B“ „www.xs4all.nl/~borkhuis/vxworks/vxw_pt1.html#1.7-C“ If you find a way around this, please let us know.
It appears at some point when we try to add/remove a file in our project or when we try to check for dependencies. (80 files in our project) To restore our project, we must then recover the project file from our backup. Well, I just encountered the problem on Tornado 2.02 while working with aPPC.