gmake: *** No rule to make target `spacemouse.obj', needed by...
5 Ansichten (letzte 30 Tage)
Ältere Kommentare anzeigen
Hello,
I am trying to build realtime model which includes Space Mouse Input block (which references to s-function 'spacemouse'). Whenever I try to build the model, I get the following error:
L:/matlab/toolbox/rtw/targets/rtwin/openwat/binnt/wcc386 -wcd=201 -wcd=202 -wcd=302 -wcd=400 -q -ei -zp8 -6r -fpi87 -fp6 -zri -zl -wx -oneatxh -DEXT_MODE -DUSE_RTMODEL -DMODEL=untitled -DRT -DNUMST=2 -DTID01EQ=1 -DNCSTATES=0 -DMT=0 -D__OBSCURE_STREAM_INTERNALS -fo="rt_sim.obj" "L:/matlab/rtw/c/src/rt_sim.c"
gmake: *** No rule to make target `spacemouse.obj', needed by `../untitled.rwd'. Stop.
### Build procedure for model: 'untitled' aborted due to an error.
The filename of the model is untitled.
In untitled.mk makefile there is one line including reference to s-function spacemouse.c file which does not exist (only spacemouse.mexw32 is available in toolbox\sl3d\sl3d folder).
I am trying to build using system target file: rtwin.tlc and make_rtw command.
To reproduce the problem: 1. Create new simulink file with Space Mouse Input block from Simulink 3D Animation library 2. Change mode to external and system target file to rtwin.tlc, make command to make_rtw 3. Build model
I am using Matlab R2011a.
Your help will be very much appreciated!
1 Kommentar
Antworten (1)
Pratik
am 17 Jul. 2024
Hi John,
The error "No rule to make target" is typically thrown by the make/gmake build automation tool because it can't find the instructions on how to create a particular file or target. This can happen for several reasons:
- Incorrect Path: Your project path, source file path and/or include folder path contains white spaces that the "make" tool cannot handle.
- Missing File: It could also mean that the indicated file is missing.
- Windows Character Length Limit: A long directory path name could also violate the Windows 256-character length limit and result in this error.
- Simulink Real-Time Character Length Limit: The error could be due to the third-party QNX compiler used by Speedgoat hitting the character length limit
Please refer to the following MATLAB Answer post for more detail:
I hope this helps!
0 Kommentare
Siehe auch
Kategorien
Mehr zu Simulink Coder finden Sie in Help Center und File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!