No rule to make target 'obj/common.o' needed by 'pic30.cof'

A forum useful to discuss the details of the ScicosLab code generator.

Moderator: paolo.gai

Locked
tenzings
Newbie
Posts: 5
Joined: Mon Apr 18, 2011 12:54 am

No rule to make target 'obj/common.o' needed by 'pic30.cof'

Post by tenzings » Mon Apr 18, 2011 1:04 am

I have been attempting to work through the following tutorial on generating code from a Scicos block diagram: http://erika.tuxfamily.org/wiki/index.p ... os_diagram

When I run the code generation step, step 3 fails with the message "make: *** No rule to make target 'obj/common.o', needed by 'pic30.cof'. Stop." Has anyone else encountered this problem? If so, I would greatly appreciate any assistance.

The full output is as follows:

ECLIPSE_HOME directory found.
--------------------------------------------------------
Step 1: Template Generation

RT-Druid is generating the scheleton application which
will be compiled together with the Scicos generated code
--------------------------------------------------------
Buildfile: C:\Evidence\Evidence\eclipse/Evidence/build.xml

an_example:
[rtdruid.Oil.Example]
[rtdruid.Oil.Example] [EXAMPLE WRITER Search Template (ID = board_flex) ... ]
[rtdruid.Oil.Example] [ ... FOUND]
[rtdruid.Oil.Example] [COPY .\conf_scicos.oil]
[rtdruid.Oil.Example] [COPY .\dspic_main.c]
BUILD SUCCESSFUL

BUILD SUCCESSFUL
Total time: 0 seconds
--------------------------------------------------------
Step 2: Parsing OIL File

RT-Druid is parsing the OIL file to generate the
makefiles used for the compilation
--------------------------------------------------------
Buildfile: C:\Evidence\Evidence\eclipse/Evidence/build.xml

compile:
[rtdruid.Oil.Configurator]
[rtdruid.Oil.Configurator] [LOAD conf.oil]
[rtdruid.Oil.Configurator] [WORKING Prepare configuration's files]
[rtdruid.Oil.Configurator] WARNING > Not found any value for MASTER_CPU. Using d
efault value.
[rtdruid.Oil.Configurator] [ Start to save]
[rtdruid.Oil.Configurator] [WRITE Debug\\eecfg.c]
[rtdruid.Oil.Configurator] [WRITE Debug\\eecfg.h]
[rtdruid.Oil.Configurator] [WRITE Debug\\makefile]
BUILD SUCCESSFUL

BUILD SUCCESSFUL
Total time: 1 second
--------------------------------------------------------
Step 3: Compiling the application

The application is now compiled
--------------------------------------------------------
Looking for the MPLAB ASM30 directory...
...Using C:\Program Files (x86)\Microchip\MPLAB ASM30 Suite
Looking for the MPLAB C30 directory...
...Using C:\Program Files (x86)\Microchip\mplabc30♂3.25
MAKE_DIRECTORIES (after a clean)

CP crt0.s
cc -E frommchp/crt0.S > frommchp/crt0.s
ASM crt0.s
CP p33FJ256MC710.h
GEN ee_pic30regs.h
CPP eecfg.c
CPP dspic_main.c
In file included from c:\PROGRA~1\SCICOS~1\SCICOS~1\MY_EXA~1\dspic_main.c:48:
c:/PROGRA~2/MICROC~1/mplabc30/v3.25/include/stdio.h:167: warning: ignoring #prag
ma printf_check
c:/PROGRA~2/MICROC~1/mplabc30/v3.25/include/stdio.h:168: warning: ignoring #prag
ma printf_check
c:/PROGRA~2/MICROC~1/mplabc30/v3.25/include/stdio.h:205: warning: ignoring #prag
ma printf_check
c:/PROGRA~2/MICROC~1/mplabc30/v3.25/include/stdio.h:206: warning: ignoring #prag
ma printf_check
make: *** No rule to make target `obj/common.o', needed by `pic30.cof'. Stop.
--------------------------------------------------------
--------------------------------------------------------
DONE... Application successfully compiled!
--------------------------------------------------------
--------------------------------------------------------

To program your FLEX board with the COF file
Debug/pic30.cof you can:

1- use MPLAB IDE from Microchip

2- run the flash.bat script [ICD3 only]
--------------------------------------------------------

C:\Program Files\scicoslab-44b7\scicos_examples\My_examp_files>

paolo.gai
Administrator
Posts: 864
Joined: Thu Dec 07, 2006 12:11 pm

Re: No rule to make target 'obj/common.o' needed by 'pic30.c

Post by paolo.gai » Mon Apr 18, 2011 7:12 am

(edited, the previous post had errors)

This is quite strange.

A few notes:

- Microchip C30 3.25 is not fully supported yet.Microchip changed a few header files and file positions. Hopefully it will be supported "soon", probably with release 1.6.0 (other posts are discussing this)

- "common.c" is a file that is generated by default by the Scicos-FLEX toolbox. The common.c contains some basic functions needed by the generated code. Is it present in the set of files generated in the directory you specified in the ScicosLab output?

bye

PJ

tenzings
Newbie
Posts: 5
Joined: Mon Apr 18, 2011 12:54 am

Re: No rule to make target 'obj/common.o' needed by 'pic30.c

Post by tenzings » Mon Apr 18, 2011 7:58 am

- Microchip C30 3.25 is not fully supported yet.Microchip changed a few header files and file positions. Hopefully it will be supported "soon", probably with release 1.6.0 (other posts are discussing this)
I realize this, and I did replace cc_pic30_detect.sh as it said in a recent post; my current problem manifested right after this (previously, I wasn't getting that far).
- "common.c" is a file that is generated by default by the Scicos-FLEX toolbox. The common.c contains some basic functions needed by the generated code. Is it present in the set of files generated in the directory you specified in the ScicosLab output?
For some reason, it isn't present in the destination directory. Here is a list of the files that were generated in that directory: analysis, compile.sh, dspic_main.c, scicos_symbols, app.mk, conf.oil, flash.bat, compile.bat, conf_scicos.oil, flash.sh (the Debug directory was also created, and I can list its contents if needed).

paolo.gai
Administrator
Posts: 864
Joined: Thu Dec 07, 2006 12:11 pm

Re: No rule to make target 'obj/common.o' needed by 'pic30.c

Post by paolo.gai » Mon Apr 18, 2011 6:49 pm

that is really strange... common.c should be created at the beginning before calling compile.sh.

Did you try on another PC? it is strange because it is working on our machines...

PJ

tenzings
Newbie
Posts: 5
Joined: Mon Apr 18, 2011 12:54 am

Re: No rule to make target 'obj/common.o' needed by 'pic30.c

Post by tenzings » Mon Apr 18, 2011 8:48 pm

Well, I got it to generate the .cof file and the other C files finally, but the strangest thing is happening: it will only work for one specific folder: the scicos_examples folder included in scicos_pack_9_3. Any folder I myself create will not work as the destination for code generation (i.e. it will not create common.c)! The name of the folder does not matter (a different folder with the same name does not work, whereas that folder with a different name does). Therefore, I thought it might be an issue with permissions, so I made sure the permissions were the same, and it still didn't work. I still think it might be a permissions problem, and maybe there are some settings I don't know about, since I am not that familiar with file permissions on Windows... Do you have any idea what could cause this? I guess it is marginally usable at this point, but I am curious about what might be happening.

Thanks!

tenzings
Newbie
Posts: 5
Joined: Mon Apr 18, 2011 12:54 am

Re: No rule to make target 'obj/common.o' needed by 'pic30.c

Post by tenzings » Mon Apr 18, 2011 9:03 pm

It seems that the problem was the location I was creating the destination folders (within the scicoslab install directory). Could a space in the path name have caused this (there was one in "Program Files")? Also, I did notice that the default permissions were different when I created folders there, so it could be that. When I use a folder on the desktop, it works fine.

paolo.gai
Administrator
Posts: 864
Joined: Thu Dec 07, 2006 12:11 pm

Re: No rule to make target 'obj/common.o' needed by 'pic30.c

Post by paolo.gai » Tue Apr 19, 2011 7:50 am

On Vista and Seven you must create all directory under your user directory!

There was a note in the tutorial
http://erika.tuxfamily.org/wiki/index.p ... pplication
but it was probably not much visible.

I Made it bigger in the wiki :-)

PJ

tenzings
Newbie
Posts: 5
Joined: Mon Apr 18, 2011 12:54 am

Re: No rule to make target 'obj/common.o' needed by 'pic30.c

Post by tenzings » Tue Apr 19, 2011 9:43 am

Ok, thanks for your help! I guess I missed the note because the title refers to Windows XP/Vista whereas I am using Windows 7.

Locked