LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

build error: an input parameter is invalid

Encountered this error and saw this post.

 

I tried mass-compile and renaming the build folder directly to c: drive.  These two items did not resolve my issue. The way I resolved my issue is re-adding the dependency folders in the Project explorer.

 

In the image NI-Build-error-resolution.png,  the dependency folders are blue with a yellow icon in the center.  If your folders are grey, remove the folders in the project explorer and re-add the folders.  This resolved my build error.

Download All
0 Kudos
Message 11 of 13
(1,066 Views)

@jchauINVN wrote:

Encountered this error and saw this post.

 

I tried mass-compile and renaming the build folder directly to c: drive.  These two items did not resolve my issue. The way I resolved my issue is re-adding the dependency folders in the Project explorer.

 

In the image NI-Build-error-resolution.png,  the dependency folders are blue with a yellow icon in the center.  If your folders are grey, remove the folders in the project explorer and re-add the folders.  This resolved my build error.


Almost everything you said in your post is incorrect, except that maybe your issue was resolved.  First of all, the folders you are talking about are NOT dependency folders!  Dependency folders are, not surprisingly, in the "Dependencies" section of your project and are NOT added by you - they are automatically added when you add something to your project that includes files not in your project.  The blue and yellow folders are autopopulating folders and the grey folders are virtual folders.

 

Your reckless use of the project folder terminology leads me to believe that the resolution of your issue was almost accidental.  I would not recommend your solution at all.

 

Please read this ultra-slow loading link to better acquaint yourself with the LabVIEW Project Explorer.

 

Edit:

I am sorry this post sounded so harsh, and I don't want to scare you off from offering future potential solutions.  Just be sure your first solution post to a forum is a well-researched one.  🙂

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 12 of 13
(1,071 Views)

Apologies for the mis-use of terminology.  

 

Perhaps the act of re-adding the folders helped resolve the issue because I no longer receive the build error and able to move forward with the build of the executable.  I added the project I wanted to build an executable and as far as I can tell, this did not update any of those folders.  So what would be the correct way to force update those folders?

 

Figured I would post how I resolved it but if this is not the "correct" way than please do share so others can resolve this issue in the future.

0 Kudos
Message 13 of 13
(1,057 Views)