"How To" copy one library and its contents from one project to another

[BillMe]

Any "best practices" when wanting to copy a library and its contents from one project to another? I always end up with a ton of conflicts that take me longer to resolve than if I had just recoded the whole library from scratch in the destination project!

[billko]

Maybe the best practice is to have the library exist outside the project so everyone can access it.

[crossrulz]

If you are running into that many confiicts for a single library, you have way too much coupling happening.  Perhaps you did not break down your library enough.

[BillMe]

I'm interested in the most efficient way to copy a library from one project to another without having it live outside either one.

[BillMe]

The library contains a class (Actor Framework), accessors, and private and public methods and messages defined for the class. It can't be broken down any more than that.

[yea_likethecity]

Billme,

The easiest way to do it is to just copy the lvlib to the new location and add it to the project. As long as both projects are not open, there shouldn't be any dependency issues. If both projects are open at the same time, there can be access issues as one project will lock the resources. If you are copying a file structure with the lvlib in it, there can be some issues with relative paths that may be arising. As others have mentioned, it sounds like your file may be too coupled.

[david.fox]

This was posted a long time ago. But, for others to reference, the best way to do what you are asking is to open the current library and "save as" -> "copy" -> rename -> select new location. Hope this helps.

[billko]

I think the best way is to use it as a library should be used.  As a dependency.  The only reason I could see why you want to copy a library is if it is part of a project and not a dependency.  Now to be clear, it's okay for a library to have its own project, but if it isn't directly related to a project, it should be a dependency.