topic Re: v4.2 Project links with old libraries in LPCXpresso IDE

v4.2 Project links with old libraries

lpcware — Thu, 16 Jun 2016 01:01:22 GMT

Content originally posted in LPCWare by caprock on Wed Apr 18 10:16:42 MST 2012
Code Red Xpresso V4.2.0 - Project LPC11xx (13xx & 17xx as well)

I am developing some static libraries and executables, and have changed names of files and/or copied files to new names. The Application is an executable that links with these libraries. While the Application seem to function as expected, I am stumped with the Project Settings Include paths.

The old libraries keep come back! (or at lease their names)

Looking at the Application/Project/Settings the list of Include paths (-I) Debug/Release, the list is populated with all of my previous libraries. I edit the list making sure to Apply, Clean/Build and the entries are cleared as expected.

Next I use Export to Zip w/o references to an external disk. Then I Delete all files in the Workspace and tick delete from disk as well. I then import the archive project and the old libraries are there! Not only at the Settings/Include, but they are in MCU/General and MCU/Linker/Libraries/Library search path as well!

I must be doing something wrong but can't seem to understand just what.

Can anyone provide information as to what is happening? :confused:

Re: v4.2 Project links with old libraries

lpcware — Thu, 16 Jun 2016 01:01:23 GMT

Content originally posted in LPCWare by frame on Wed Apr 18 11:17:34 MST 2012
I had a similar issue a few weeks ago. I tried to pull an existing library project, based on CMSIS V1.3 over to CMSIS V2.0. The effect was almost identical - references to the old (V1.3) libraries popped up everywhere in the build process, even after manually replacing all of them.
I finally recognized that this was unmanageable for me - I scrapped the project, setting it up from start with the new library, only importing the source files.

I guess it gets lost in the opaque project management of Eclipse - I had issues with other Eclipse-based IDEs too. But for a developer / end user, it is usually the overall impression that counts ...

Re: v4.2 Project links with old libraries

lpcware — Thu, 16 Jun 2016 01:01:24 GMT

Content originally posted in LPCWare by CodeRedSupport on Wed Apr 18 11:52:58 MST 2012
Is this what you are seeing...

Quote:
Invalid project path: Include path not found ....

If so, then see:

http://support.code-red-tech.com/CodeRedWiki/InvalidProjPath

And if you need to change the names of library projects that your application project link with, then you should be able to use a modified version of the script we provide for updating from linking with CMSIS 1.3 to 2.0 projects....

http://support.code-red-tech.com/CodeRedWiki/cmsis130to200

Regards,
CodeRedSupport

Re: v4.2 Project links with old libraries

lpcware — Thu, 16 Jun 2016 01:01:24 GMT

Content originally posted in LPCWare by caprock on Wed Apr 18 12:05:35 MST 2012
No errors or warnings.
I am using CMSISv2p00.

I just deleted my library including delete from disk.
I created a new project w/same name. There was a warning that this would apply new settings - Ok.

When this project was created, my includes were already there! And of course, the resulting App has the old libraries as posted earlier.

So now I am going to try creating a fresh & empty workspace and try this all over again.

Re: v4.2 Project links with old libraries

lpcware — Thu, 16 Jun 2016 01:01:26 GMT

Content originally posted in LPCWare by caprock on Wed Apr 18 13:50:23 MST 2012
frame,
Took your advise & from Code Red:

Created totally NEW static libraries & NEW C applications in a new Workspace.

Now all seems ok.

The question remains possibly for Code Red:
How can we delete these old histories? Are we forced to re-create projects when a major update is needed?
:)

Re: v4.2 Project links with old libraries

lpcware — Thu, 16 Jun 2016 01:01:26 GMT

Content originally posted in LPCWare by frame on Thu Apr 19 04:11:19 MST 2012
I do not blame Code-Red / LPCXpresso IDE, because I had other troubles with Eclipse based IDEs, too. I don't have the time and the nerves to dig that deep into Eclipse. It might be free / open source, but it hides a lot of the build settings from me by default. You hardly know what actually happens internally - thats what I meant with the slightly euphemistic "opaque".
All this made me loving [FONT=Courier New]make[/FONT] files...

Re: v4.2 Project links with old libraries

lpcware — Thu, 16 Jun 2016 01:01:27 GMT

Content originally posted in LPCWare by CodeRedSupport on Thu Apr 19 04:33:16 MST 2012

Quote: caprock

The question remains possibly for Code Red:
How can we delete these old histories? Are we forced to re-create projects when a major update is needed?
:)

Sorry, we are not sure we actually follow what the problem you are seeing is. It certainly doesn't ring any bells here either with project updates we have done ourselves or with interactions we have had with customers over updates they have done.

If you can explain in more details exactly what you are doing and exactly what you see (preferably a step by step set of instructions for replicating the problem), then we can investigate. Otherwise I'm not sure what else we can do here.

Regards,
CodeRedSupport

Re: v4.2 Project links with old libraries

lpcware — Thu, 16 Jun 2016 01:01:28 GMT

Content originally posted in LPCWare by caprock on Thu Apr 19 08:24:58 MST 2012
Thanks CodeRed & frame - I certainly did not mean to be critical of this product, only to raise an issue. I have been working with Red Suite NXP Version for about 2 years and this is the first big issue. This is a [B]great[/B] product, well integrated, and yes, complex to understand some aspects, especially the project construct (metadata)?.

This problem report may have something to do with how the workspace was created, as this had been my first exposure to Red Suite V4.0.4 and I probably mixed some content from V3.6.3.

In short, this is a 13xx project that includes several (5) bogus libraries, including mix of 13xx/17xx) libraries referenced for Include and Release libraries. These bogus libraries are not random; they seem to represent derivative and/or solutions used to create the current names. But they do include a mix of processor types 13/17xx.

Unfortunately, all attempts to take a snapshot showing this problem exceeds the attachment size.

[B][I]But this problem seems to be isolated to this one particular workspace.[/I][/B]

I can recreate all of this and can send any info perhaps offline on Monday.

Re: v4.2 Project links with old libraries

lpcware — Thu, 16 Jun 2016 01:01:28 GMT

Content originally posted in LPCWare by researchinnovation on Thu Apr 19 22:26:17 MST 2012
Hi...!!!

Are you still facing the same problem. Why do not you create new workspace and try.

Thanks...:)