Proper procedure to duplicate a project?

[scottm]

This seems like it should be a simple task, but I struggle with it every time.  What's the proper way to replicate a project within the same workspace in MCUXpresso?

The way I think it ought to work is that you'd select the original project (with the project open - for some reason it'll let you copy but not paste if the source isn't open) from the project explorer and select copy, then paste.  Usually this works in Eclipse.  This is what I get in MCUX:

The only thing in the log is this:

!ENTRY org.eclipse.cdt.core 1 0 2019-02-03 10:49:19.947
!MESSAGE Indexed 'HyperionBasic' (11 sources, 59 headers) in 1.08 sec: 6,016 declarations; 9,264 references; 9 unresolved inclusions; 66 syntax errors; 270 unresolved names (1.7%)

Now, some of my source folders are linked to other locations.  I can't see why it wouldn't be able to keep the same references, but I mention that because it's something I don't see in the example projects so I figure maybe it's not something that gets tested routinely.

Is there an alternate way to do this?  I've been told to never copy or move projects manually in Eclipse or you'll foul things up and get weird problems.  I'm trying to do this as much by the book as possible, but it doesn't seem to be covered in the MCUX docs.

Thanks,

Scott

[BlackNight]

Hi Scott,

I copy projects in MCUXpresso IDE (10.3.0 for the reference) with a simple copy & paste in the project explorer (select project, CTRL-C and then paste it with CTRL-V and give it a new name.

After that I do a Project > Clean as this is recommended after every move or copy to get rid of old files.

Linked folders get copied too as is, so this is expected.

So this is *much* easier and works straight forward in MCUXpresso IDE compared to KDS where I have to adjust project settings or launch configs. In MCUXpresso the launch configs still have the original names (expected), so I simply delete them to have them re-created when I do a debug again.

So to me the copy of projects really is nothing special.

About your error dialog I could imagine that this might come from a special plugin which tries to scan the files in the background and get confused. I do have extra plugins installed too, but seen any issues.

But what I have seen on a student machine is that these 'free virus scanners and firewalls' can cause all kind of issues as they interfere somehow with the file operations. I have on my machine the Windows standard firewalls/scanners installed and running, and they do not cause such issues.

I hope this helps,

Erich

[scottm]

Hi Erich,

Guess I'll have to start uninstalling plug-ins, or start with a fresh install on another machine and see if I can figure out where it's going wrong.  I didn't want to waste more time on it without knowing if it actually does copy links properly.  Are your linked folders project-relative or absolute, and do you find that it makes any difference?

Do you use linked folders for shared components?  I've got a few folders that contain modules used across multiple projects.  I really wish MCUX had CW's ability to exclude source files using checkboxes rather than individually going in to each file's properties, but then CW wasn't perfect either, and would reset the explorer view every time you changed a checkbox.

I've been thinking of making those git submodules for better control.  For now, the shared folder setup is manageable when the components are only shared between a few projects and I can do immediate testing on all of them if I need to make a change.

Thanks,

Scott

[BlackNight]

Yes,  a clean install is something worth to try (you don't have to uninstall anything, simply install it into a different folder).

I'm using linked folders for shared sources. I always set them up in a realtive way, e.g. ../../common.

Erich