XDE11.11.1, XTimeComposer 13.2.3 and xmake "*** no rule to make target for 'all' stop"

New to XMOS and XCore? Get started here.
Post Reply
fubxmos22
Newbie
Posts: 1
Joined: Sun Jul 02, 2017 2:30 pm

XDE11.11.1, XTimeComposer 13.2.3 and xmake "*** no rule to make target for 'all' stop"

Post by fubxmos22 »

Dear Xmos-Nerds,

I run into big difficulties with having 2 different XMOS installations on the same Mac!

At first I took over an XtimeComposer project some weeks ago and everything was working fine!
And then I took over an USB project that was originally build under XDE 11.11.1. with and I was clearly warned that this project will hardly ever being build under XTIMEComoser 13.2.3!

Trying to compile the USB project under XDE11.11.1 I took me about a week trying to get rid of the following XMake message:
" ***xmake no rule to make target for 'all' stop"
... although I was told, that the USB-Project should run after unpacking a zip-file.

Being happy now after hours of experimenting with the Build and C/C++ options and other options I wanted to look whether my XTIMEComposer is still working!
But now I was very surprised to get now the same resulting message from xmake:
" ***xmake no rule to make target for 'all' stop"

Again after hours of experimenting I could reanimate the XTimeComposer project build.
Added another hour to renanimate the Flashing and Run...

The only thing I definitely know now is that the two versions influence each other and have some for me hidden dependicies. I am warned when reopeming th XTIMEComposer:
"This Workspace contains legacy xTimeComposer(pre-12.9) run debug launch
configurations. To convert these to use the latest format (and hence be visible in
the latest xTIMEComposer) select the convert button below:"

Because of the explicit warning above I always select "CLOSE"....


Ok, now I have a state where I could go back to work... But not beeing a native born XMOS-user or a makefile specialist I want to post the following questions to experienced XMOS nerds:


1.) When you read " ***xmake no rule to make target for 'all' stop"
What are you reminded for, where do you look first, what does this tell you?
I only know now that e.g. some of the makefiles within modules or projects are not found.
One thing that I found is that you can/must activate a makefile with the following setting:
"xmake -f.makefile". What does the dot "." stand for?

2.) Could anyone please point to a working solution to deal with the problems of a dual XMOS-versions installation?

3.) Being motivated to understand the details of every check box/option in the project settings dialog boxes - some reachable only via a right click, some over the menus-
and their practical meaning and impact. Is their any detailed/comprehensive documentation out that even a newbie like me could understand.
E.g. searching for any documention about the XDE 11.11.1 I am always beeing redirected to the xTIMEcomposer tutorials and introductions. I seems that these legacy docs are removed from the net.
(or I'm simply too silly for a good internet search..)

Many thanks in advance,
fubxmos22


User avatar
xsamc
Active Member
Posts: 55
Joined: Fri Mar 04, 2011 3:38 pm

Post by xsamc »

Hi fubxmos22,
The only thing I definitely know now is that the two versions influence each other and have some for me hidden dependicies.

There are .project and .cproject files in each module, which allow them to be imported as projects into xTIMEcomposer. There is also a .metadata/ directory at the root of the workspace.
I would guess that some of the issues you are seeing stem from differences in this metadata, so as a starting point it's probably safest to use separate workspaces for each version. You can import the same modules and projects (without copy) in to each workspace.

If temporary build files are being saved you should also perform a clean build when switching between tools version.

You might find it easier to use the command line interface for building the same source files with multiple tool versions, as this will avoid relying on any of the metadata.

Cheers,
Sam
Post Reply