08-30-2016 09:07 AM
I have a project developed in LabVIEW 2014 which includes .aliases file in the EXE target (and so in the installer which is built including the EXE target).
I don't want to include this file in the installer because it contains information specific to the local computer.
I found this thread but I don't find a way to remove the file from the installer.
How can I do this?
08-31-2016 04:22 AM
Hello,
.aliases files is not auto-added to the installer, when you chose what to include in the installer you simply don't include the .aliases files.
I also suggest you the following link:
On .aliases Files
https://decibel.ni.com/content/thread/23004
I hope this could help.
Enrico
08-31-2016 04:35 AM
@esgro wrote:Hello,
.aliases files is not auto-added to the installer, when you chose what to include in the installer you simply don't include the .aliases files.I also suggest you the following link:
On .aliases Files
https://decibel.ni.com/content/thread/23004
I hope this could help.
Enrico
If you use the exe build spec in the installer build spec (which is much simpler than adding all the files manually) the .aliases file is automatically included.
You can, however, use a custom .aliases file in the exe build spec (Advanced > Use custom aliases file). This can probably even be empty.
08-31-2016 04:41 AM
Can you send some screenshot in order to describe your situation?
Thanks
Enrico
08-31-2016 05:04 AM
Here you are.
For such a simple case you could probably add the files individually (you'd have to add them to the project first). For more complex applications with lots of dependencies in the data folder it is convenient to add an exe build spec to the installer.
08-31-2016 05:28 AM
Hi dan_u,
you perfectly summarized the situation, an d I try to give some additional details:
I don't know if a custom empty .aliases file is a solution, because my project is under a git environment where .aliases files are not tracked. If another developer clones the repository, the custom .aliases file is not present (since it's not tracked) and so the installer cannot be built.
08-31-2016 06:36 AM
But you could have it under version control. We do that with a custom .ini file, which we add to the project and under version control, and which is used for the exe build spec. The same could be done with the .aliases file I assume.