Create a custom project template with Packed Library dependency

[Olivier-JOURDAN]

Hello everyone,

I'm currently strugling creating a new custom template project (https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000x1k8CAA&l=en-US).

 A bit of context :

• Project I want to create from this template allow the user to create a new plugin for an application --> building the project gives a packed library
•  The project rely on a packed library that is used as interface between EXE and plugin

T

The project contained in ProjectTemplate directory as the following hierarchy

 

The lvproj opens correctly here.

First issue

If I try to create a new project from the Create Project window, I get an error 6

CopyUserProject.vi has a password but path inputs type don't have path that exceeds 255 characters

I found a workaround removing the explicit link to the packed Library interface in the project. If this packed library is in the dependencies, project is correctly duplicated, but... see issue 2

Issue 2  

In the new project, the  packed Library interface is linked to the ProjectTemplate directory. I would like to change this link programmatically in order to link to my actual entire project. Do someone know how to automatically change this link ? ( Note that I know that even manually, this not something easy...)

Thank you for any ideas that could help me.

[StefanLemmens]

Hello Olivier,

I also ran into this problem before but I solved it (or worked around it) in a different way.

I have put these dependent (interface) lvlibp's in a package and installed them in the user.lib, this way both the template and the final project can link to that location and I don't need to relink anything afterwards. It also avoid copying this lvlibp too many times and all the created projects get the latest version of the packed library when I install an update of the package.

Not sure if this is any help to you?

Best Regards,

Stefan Lemmens

Intersoft Electronics

[Olivier-JOURDAN]

Hello Stefan,

Thank you for your comment. I've been thinking doing this, but it can lead to other issues related to our work environment. Anyway, it's good to know that you use this solution / workaround.

Thanks again and have a great day.