AN4379SW - importing CW10.1 project

[leccy]

I am trying to import the TWR-K60N512 project into my workspace.  Unfortunately I get this error:

"C:\Program Files\Freescale\CW MCU v10.1\gnu\bin\make: *** No rule to make target `../Project_Settings/Linker_Files/PK60N512_flash.lcf', needed by `PTA10_twrk60n512.afx'. Stop."

I cannot find the .afx file, or find any reference to it on this site, CW10 help, or google.

Any ideas?

[J2MEJediMaster · Accepted solution]

The .afx file is the binary file that the make process generates. The real issue is what the trouble is with referencing the linker file, PK60N512_flash.lcf.

Does the project you are trying to import work already? If the answer is yes, I wonder if there's something wrong with the pathname of your workspace. Does your workspace directory name have blanks in it?

---Tom

[leccy]

Thanks for your reply Tom

The project was downloaded from this site, and the supporting documentation states that it has been tested on CW10.1 on Windows XP - my setup.

There are spaces in my path (My Dcouments etc) - and i've just noticed that all the folders in the downloaded project use underbars...

Spaces still an issue these days? :smileywink:

[leccy]

Well, I was able to get the project to compile correctly by creating a new workspace folder on c:\ and copying the downloaded AN to that folder, so it does appear to be an issue with spaces in the path.

However, I have been able to create bare metal and MQX projects in folders under My Documents etc, and not get this error.

Is there a setting in the IDE for handling spaces in the path, or is it just that the original AN project was created on a path without them?

Anyway, thanks for pointing me in the right direction Tom.

[J2MEJediMaster]

Glad to hear that you got it working. The thing to watch for is the relative path that CodeWarrior uses for the build. If the build tools work with a pathname starting within the CodeWarrior directory, then it doesn't matter if the parent directories have blanks in their names or not. For example, the CodeWarrior for MCUs v10 installer places a directory named "CW MCU v10.1" in the Program Files directory. Yes, that name has spaces, but notice that every subdirectory within it uses underscores with the directory names. From the build tools perspective, all of the subdirectories have valid names.

The other thing to watch out for is that a pathname can get too long. Both Windows XP and Win 7 have support for really long pathnames, but I've have seen instances where a long directory name caused a directory reference to exceed the filesystem limit and the build tool blows out.

---Tom